Agile Development (VII)-Scrum assessment meeting

This article is primarily intended to test your understanding and use of the scrum assessment sessions,

Through this article you can test
1. The process and steps of your Scrum assessment meeting
2. The results of the SCRUM evaluation
I. Purpose of the meeting
1. Determine the size of the items in the Backlog.
2. Determine how much work the team can do in a sprint.
3. Team members can see what happens in the next phase of the project from the meeting.
4. Content of the backlog: break down the backlog of items in a reasonable way for a deeper understanding
Basic requirements:
Only teams can make estimates. Product owner needs to be present to help determine whether certain user stories can be split into smaller stories.
Ii. Time of the meeting
1. The meeting time limit is not more than 90 minutes.
2. If the sprint lasts longer than one week, it is more appropriate to have two estimated meetings per sprint
III. Preparation of the meeting
1. Invite participants to:
Product Owner
Scrum Master
All members of the team
2. Prioritized issues in the product Backlog
3. Make the product Backlog publicly available to all and ensure that it is accessible
4. Label 1,2,3,5,8,13,21,34,89 on a set of cards used as a planning card, and go to the hands of each team member
Iv. process of the Conference
Describe the objectives of the meeting
1. Product owner shows the product backlog entries that she wants to get estimated.
2. The team uses planning poker to estimate the backlog entries.
3. If you have not yet started to evaluate the issues in the Backlog:
(1), select the problem that you think is the smallest use case in the backlog, and assign a workload of 2 story points for each issue in the product backlog:
(2), by the product owner to explain the Backlog of the detailed use cases behind the problem.
(3) The members of the team elect a plan card on their hands to vote to determine the amount of work he considers the problem to be.
(4) All team members flash their cards at the same time. If the assessment results are divided, let the members with the most divergent opinions debate and then vote again until everyone agrees
(5), evaluation results are added to the Backlog item
4. If a backlog entry is too large to be placed in the next or subsequent sprint, the team divides the backlog entry into smaller backlog entries and estimates the new backlog entry using planning poker.
5. Re-estimate the entries that are not currently completed in the backlog, but that may be completed in the next three sprints.
6. Concluding the evaluation session with a concise summary
(1), if necessary, and then schedule another assessment meeting
7. Identify the backlog entries that need clarification for the next estimate meeting.
v. Outcome of the meeting
1. The estimated product Backlog.
2. Smaller backlog entries.
3. Issues requiring clarification.

4. All personnel in the company are asked to obtain this assessed backlog

Agile Development (VII)-Scrum assessment meeting