Requirement gathering in Scrum

Scrum framework is deliberately light in defining this as there are many existing practices is requirement gathering that work well. Scrum does not want to impose any one style and allow the organisation to choose what is best for them. 

Product Owner should 
- Establish a vision for the project to constrain the scope 
- Talk to his/her users and get high level business requirements. 
- Order them so they give value to the organisation and meet the scope of the project (or change the scope if not originally correct) 
- Work with the team to define what is a "Ready" requirement. 
- With team refine them into functional requirements that can actually be built 
- Constantly adapt as more knowledge is learnt or gained 

This is a continual process

Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros
Read more