Grooming meeting and the role of testers

Grooming meeting's Chinese translation is "grooming meetings", which is not a standard meeting in the scrum framework (standard meetings for planning meeting, Daily Scrum meet, Review Meeting and retrospective meeting), which is added to clarify requirements and thus increase the efficiency of planning meeting, can be called pre-planning meeting.

Objective

• Add a new user story (also available from within the team)
• Clarify requirements and let the team understand the user story at the same level
• Break down the user story and prioritize the corresponding
• Assess the ease of user stories (planning poker)
• Add Acceptance Criteria
• Identify the ambiguous aspects of the user story and clarify the confirmation in time

Time

Grooming meeting time is typically 2-3 days before the end of the current sprint, which allows clarifying times for some of the less-than-clear requirements encountered in the meeting. Grooming meeting duration is typically 2 hours (for a sprint of two weeks)

Conference Staff

Grooming meeting encourages all agile team members to participate, of course, if it is better for customers to participate, so that people from different roles can view the user stories to be sorted from different perspectives

Process

Grooming meetings are hosted by Scrum Master, and the PO as the presenter is sorted according to the priority of the user story, as long as the user story is sufficient or slightly more than the number of commits that the next sprint can commit.

The grooming steps for a story are generally:

• Before
  • Team members View (review) the user story to be combed, have a preliminary understanding
• In the meeting
  • Select the highest priority to do user story from the User stories list
  • PO to explain the user story
  • Team members ask questions from different perspectives for user stories
  • Po explains and eventually agrees on the content of the user story, records, adds action item, and develops the appropriate owner for the unclear requirements, then confirms
  • Team Definition Acceptance criteria
  • Team uses planning poker to assess the ease of user stories
• After the meeting
  • PO and team members gather and confirm information about requirements that are unclear in the meeting

Test personnel

For testers, you need to look at the user stories you want to comb from the following perspectives:

• Product Manager Perspective: is the user story reasonable? Is it valuable to customers? Is it a core feature? Is the priority reasonable? Is it possible to split?
• User perspective: Is it easy to use?
• Test angle of view: Acceptance criteria is comprehensive and reasonable? Are there blocking (environment, external dependencies, etc.)?

Summarize

By combing the meeting, the team members have a clear understanding of the user stories to be done by the next sprint and have a good grasp of the task creation and evaluation of the scheduled meeting.

Grooming meeting and the role of testers