User story checklist...

Try the INVEST acronym. If you just google this, you should find a few links. 

One should try to have Stories be: 
Independent 
Negotiable 
Valuable 
Estimatable 
Small 
Testable 

Also, a popular format used is: 
As a <Persona> I need <some functionality> so that <benefit>. 




Acceptance criteria is critical to get before sprint planning as this removes any ambiguity of what has to be delivered and how it will be accepted. That is if you can prove the acceptance criteria (and your other DoD) then the product owner has to accept it. If suddenly a "Yes, but it doesn't do", the answer is simply "Not in the acceptance criteria, add this to the backlog and prioritise when it should be done" 

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