Applying Agile MoSCoW Prioritization
59mBeginner2018-11-19
Authors

Claudine Peet
Founder of IT Explained, LTD
Course details
Appropriate prioritization of requirements helps ensure timely and efficient project delivery. The MoSCoW method sorts requirements into four categories: must have, should have, could have, and won't have. The framework helps the project team reach a common understanding with stakeholders and ensures you deliver high-quality results that are on time and on budget. In this course, Claudine Peet shows how to implement MoSCoW prioritization in agile project management. Learn how to define requirements, prioritize and test those requirements, and deal with changes that arise during the project life cycle. Claudine provides tips and tricks that will ensure you end up building the product with exactly the features you needed—without the features you thought you wanted.
Learning objectives
Describe what a project’s variables are.
Identify the best time to define broad project requirements.
Summarize the process of testing the requirements of a project.
Recall tips for prioritizing requirements.
Explain the process of making a requirement change.
Learning objectives
Describe what a project’s variables are.
Identify the best time to define broad project requirements.
Summarize the process of testing the requirements of a project.
Recall tips for prioritizing requirements.
Explain the process of making a requirement change.
Skills covered
Agile Project ManagementProject ManagementFoundations
Concepts
Introduction
- Agile MoSCoW prioritization
Overview
- What are requirements
- What is MoSCoW
- Challenges applying MoSCoW
- Importance in projects
- Project variables
- Requirements levels
Defining Requirements
- Roles and responsibilities
- Techniques
- How to document requirements
- Tips for writing user stories
- Functional and nonfunctional requirements
Prioritizing Requirements
- How to apply MoSCoW to requirements
- What will be delivered
- Testing requirements
- Requirements cycle
- Tips for prioritizing
- Tracking projects
Dealing with Changes in Requirements
- Reasons for change
- Impact on levels
- Effect on prioritization
- Baselining requirements
Conclusion
- Next steps