Course Overview
Requirements are approached differently in agile way of working. We use the behavior of the user as a starting point for requirements gathering and refine the requirements along the conversation we maintain with the user. This is all done parallel to developing small part of the product with a prioritized selection of stories for each sprint period. This not only requires engineers and developers having conversation with users, it also requires a different technique of writing these stories down. Next a different approach to planning is used which allows for estimation for sized work packages and a normalized approach to estimating these stories, story points and empirical planning.
Who should attend
- Scrum Team member
- Developers
- Engineers
- Product Owners
- Scrum Master
Prerequisites
- General Agile knowledge
- General Development and usiness knowledge
Course Objectives
•
- What is a user story.
- How to work with user stories the correct way
- What is refinement.
- What is the Cone of Uncertainty.
- How do we plan
- What is a Story point
- How To allow for agile, empirical planning.
- It may sound strange but by allowing the individual estimates to be wrong, as a group the estimates come together and tend to be more accurate.
Engels
Nederland