Killer Requirements Generation Using Design Sprints
Requirements are a key driver for any project and there is a direct relationship between the accuracy of requirements and the outcome of a project.
In many cases there is a direct link between scope and requirements, hence requirement definition impacts project scope. Every project benefits by having a well-defined project scope that helps define boundaries for the project, the primary outcome/goal/deliverable to be achieved and success metrics (what does "done" look like")
We'll discuss how Design Sprint methods can be used to help project managers and teams at-large ensure alignment between current problem/challenge, scope of work and requirements for the project overall.
- Understand the design sprint process and major outcomes resulting from completing a successful sprint.
- Understand risks associated with requirements definition and risk mitigation actions
- Understand how to identify stakeholders to engage in design sprint process
- Understand how design sprints can be used to generate and validate project requirements
- Understand how to manage team dynamics during the design sprint process
NOTE: You must watch videos in their entirety and all the way through to the end for our system to record your viewing activity accurately. Learn more about PDUs on ProjectManagement.com.
Acknowledgements: Kimberly Whitby, Derrick May and James McCrory