Development Management checklists (18)-agile development scrum Sprint plan meeting I

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 Sprint plan meeting,

Through this article, you can check
1. process and steps of your scrum Sprint plan MEETING
2. output results of the Meeting

Sprint program meetings are critical and should be considered the most important activities in scrum (this is of course my subjective opinion ). If it fails, the entire sprint may even be destroyed.
A sprint program meeting is held to give the team sufficient information to work in a few weeks without interference, and to give the product owner sufficient confidence in the meeting.

I. Purpose of the meeting 
 
1. Set the sprint target and product backlog
2. The work of the Meeting is mainly focused on analysis. The goal is to understand in detail what the end user really wants. The product development team can learn more about the real needs of end users from this meeting. At the end of the meeting, the Team will decide what they can deliver.
Basic requirements:
Only a team member can determine how many backlog entries the team can receive in the current sprint.

Ii. Meeting Time 

In a sprint, this meeting takes 60 minutes each week. Hold the meeting in the morning,
In this way, the second part of the sprint planning meeting may be held on the same day.


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. Problems in backlog have been evaluated
4. Publish the product backlog to everyone in the meeting to ensure that the product can be obtained.
5. who are expected to be absent (for example, on vacation)
6. Ensure that the room environment is suitable for group discussion
7. Everyone can obtain the results of the last sprint review meeting and sprint review meeting.
8. The Sprint schedule has been arranged.
9. Schedule of sprint scheduled meeting 1
10. Schedule of sprint Planning Meeting 2
11. The first day of the sprint is determined.
12. The last day of the sprint is determined.
13. Schedule of daily scrum meetings
14. Schedule of sprint review meetings
15. Sprint review meeting schedule

Iv. Meeting process 

1. Publish the sprint schedule to everyone
2. publish the results of the sprint review meeting to all
3. Publish the sprint review meeting results to everyone
4. The product owner will explain the product vision to the team
5. Product owners and teams work together to determine sprint Objectives
6. Start with the first product backlog entry (story.
7. Discuss the product backlog entry for further understanding.
8. Analyze and clarify the User Acceptance Test.
9. Find non-functional requirements (performance, stability ......).
10. Locate the acceptance criteria.
11. Find out the level to which the task needs to be completed.
12. Get a clear understanding of all aspects of the backlog entries.
13. Draw relevant charts for deliverables, including flowchart, UML diagram, hand-drawn sketch, and UI design.
14. Go Back To Step 1 and select the next backlog entry
Process check:
Ask the team if they can answer the following questions quickly: "Can we finish the first backlog entry in this sprint ?" If you can get a positive answer, continue to ask for the next backlog entry until the last backlog entry that has been analyzed.
Next, take a rest.
After rest:
Expand the preceding process for the next backlog entry.

End Process:
1. Set aside 20 minutes before the end of Part 1 of the sprint planning meeting.
2. Ask again-more seriously and formally: "Can you complete the first backlog entry ,...... Second ,......?"
3. If the team thinks they cannot accept more backlog entries, stop.
4. Now it is a very important step: Send the product owner away. She must leave! All people, except the team and scrum Master, have to leave. Customers and end users, all others have to leave!
5. When everyone else leaves, ask the team: "really -- do you believe you can complete this list ?"
6. I hope the team can have a brief discussion to see how much work they think they can accomplish.
7. communicate the results with the product owner and end users. No more discussion!

V. meeting results 
1. Prepare the established product backlog for sprint Planning Meeting 2
2. Select the product backlog entries.
3. Requirements for each backlog entry.

4. User Acceptance Test for each backlog entry

<Development Management checklists> by dylove98 @ Development Management checklists