Development Management checklists (17)-agile development scrum evaluation meeting

Note: The Development Management Checklists-series of articles are transplanted from my iteye blog. The Development Management checklists column will be updated directly in the future.

This article mainly aims to check your understanding and usage of the scrum evaluation meeting,

Through this article, you can check
1. process and steps of your scrum evaluation meeting
2. Scrum evaluation output results

I. Purpose of the meeting

1. determine the size of each item in the backlog.
2. determine how much work the team can do in a sprint.
3. The team members can know what will happen in the next stage of the project from the meeting.
4. trim the backlog content: deploy each backlog project in a reasonable way to gain a deeper understanding.

Basic requirements:
Only teams can make estimates. The product owner must be present to help determine whether a user story can be split into smaller ones.

Ii. Meeting Time 

1. The meeting time limit is no more than 90 minutes.
2. If the sprint lasts longer than a week, it is appropriate to hold two estimation meetings for each sprint.

Iii. Preparations for the meeting 

1. Invite Attendees:
Product owner
Scrum master
All team members
2. Problems in product backlog have been sorted by priority
3. Publish the product backlog to everyone to ensure that the product can be obtained.
4. Add tags 1, 2, 3, 5, 8, 13, 89 to a group of cards used as planning cards and send them to each team member.

Iv. Meeting process 

Objectives of the meeting
1. The product owner shows the product backlog entries that she wants to estimate.
2. The team uses planning poker to estimate backlog entries.
3. If you have not started evaluating problems in the backlog:
(1) Select the problem that you think is the smallest use case in the backlog, and assign two story points for the workload:
(2) The product owner is responsible for explaining the detailed use cases behind the problem in the backlog.
(3) Each member of the team selects a plan card from his hand to vote for the workload of the problem he considers.
(4) All team members should display their cards at the same time. If there are differences in the evaluation results, let the members with the greatest differences of opinion debate and then vote again until everyone agrees.
(5) the evaluation result is added to the backlog entry.
 
4. if a backlog entry is too large and needs to be placed in the next or subsequent sprint, the team will divide the large backlog entry into several smaller backlog entries, estimate the use of planning poker for new backlog entries.
5. Re-estimate the entries in the backlog that are not completed yet, but may be completed in the next three sprints.
6. End the evaluation meeting with a concise summary
(1) If necessary, schedule another evaluation meeting
7. Separate the backlog entries to be clarified in the next estimation meeting.


V. meeting results 

1. Estimated product backlog.
2. Smaller backlog entries.
3. Issues to be clarified.

4. All employees of the company should obtain the evaluated backlog.

<Development Management checklists> by dylove98 @ Development Management checklists