Titlebook: Experiment-Driven Product Development; How to Use a Data-In Paul Rissen Book 2019 Paul Rissen 2019 Product development.Agile.UX.hypothesis-

無禮回復(fù)

夸張

妨礙

牽索

Governance and Limited StatehoodSo here we are. You’ve run an experiment and collected the evidence. Now comes the important part—learning from what you’ve discovered. If you don’t take the time to learn—to interpret the results of an experiment and understand its implications—then everything you’ve read previous to this has been for nothing.

Anticoagulant

Helen Peterson,Minna Salminen-KarlssonYour experiment is complete. You’ve taken the time to analyze the evidence and determine whether your hypothesis has passed the test, or otherwise. You’ve noted what you’ve learned, what you haven’t been able to determine, and any intriguing questions that have arisen. Most importantly, you’ve reached a conclusion, and made a decision.

inchoate

What Is Experiment-Driven Product Development?Experiment-driven product development (XDPD) is a way of approaching the product design and development process so that research, discovery, and learning—asking questions and getting useful, reliable answers—are prioritized over designing, and then validating, solutions.

Measured

Overthrow

Hypotheses, Measures, and ConditionsIn the previous chapter, we looked at what is known as the “Planning Phase” of experiment-driven product development. In that phase, we collected together all kinds of raw material that form the basis of product development work, turned them into experiment-ready questions, and prioritized among them.

文藝

Scale and MethodBy now, you should be almost ready to get started running an experiment. In the previous chapter, we covered the first part of the Design Phase—formulating a hypothesis where applicable, identifying the measures of evidence by which we’ll answer the question, and determining conditions for being part of the experiment.

貞潔