7 Tips for backlog grooming/refinement meeting





Backlog Grooming meeting should be timeboxed and ready stories should be identified prior to meeting.

  1. Ensure that the Acceptance criteria has specific details which can be tested and verified.
  2. Acceptance Criteria should be agreed with team so that they could point out any ambiguity/unknown points.
  3. Tester should have seen the acceptance criteria (prior to Backlog grooming meeting)to suggest any possible test cases which could be covered for example common UI validations.
  4. Try to identify the negative scenarios which could be critical for team to handle during implementation.
  5. Use Whiteboard to explain user stories and business flow
  6. Any assumptions/queries/risks should be noted to be handled later. 
  7. Enough details should be there so that additional found in sprint should not change the scope of work

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