Learn about the technique of using experiments to elicit requirements, and when to recognize that experiments are needed.
- Sometimes, people don't know what they don't know.…They have blind spots due to complexity, ambiguity,…or just plain uncertainty about the future.…This is increasingly common in today's…business and technology landscape.…If your team is struggling with blind spots,…try experimenting.…It's the best technique to pull out when your team…needs clarity and needs to learn something to move forward.…Experimenting is about learning the unknown,…testing ideas, assumptions, and key theories…that drive requirements for products and systems.…
We identify what we want to learn more about…and design an experiment to bring…the team the needed information.…Experimenting helps teams get through the times…when requirements are hard to get at…or, on the other side of the equation,…requirements keep changing.…When you see one of these patterns happening,…it may be time to recommend and plan an experiment.…To plan an experiment, first we need…to know what we want to learn.…What information could we gather…that would help the team make decisions?…
LinkedIn Learning (Lynda.com) is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- What's elicitation and analysis?
- The relationship of elicitation to analysis
- Elicitation techniques
- Using interviews, brainstorming, and experiments to elicit requirements
- Analysis techniques
- Working with process models, context diagrams, and decision tables
- Adding to a process, product, or system