Agile Development (eight)-Scrum sprint Planning Meeting 1

This article is intended to test your understanding and use of Scrum Sprint planning meetings.

Through this article you can test
1. The process and steps of your scrum Sprint planning meeting
2, the output of the conference
The Sprint planning meeting is critical and should be considered the most important activity in scrum (which is, of course, my subjective opinion). If it does not perform well, the entire sprint will even be destroyed.
Sprint planning meetings are held to allow the team to get enough information to work undisturbed for a few weeks and to give the product owner full confidence
I. Purpose of the meeting
1. Set Sprint target and scheduled product Backlog
2, the work of the Conference is based on analysis, the goal is to understand in detail what the end user wants. The product development team can learn more about the real needs of the end user from this meeting. At the end of the meeting, the team will decide what they can deliver.
Basic requirements:
Only team members can determine how many backlog entries the team can claim in the current Sprint.
Ii. Time of the meeting
In a sprint, the meeting takes up to 60 minutes per week. The meeting was convened in the morning,
It is also possible to convene the second part of the Sprint planning meeting on the same day.
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. The issues in the Backlog have been assessed
4. Release the product Backlog to everyone in the meeting to ensure that it is accessible
5. Who is expected to be absent from the team (e.g. vacation)
6. Ensure room environment is suitable for panel discussion
7. Everyone can get the results of the last Sprint review and Sprint review meeting
8. Sprint schedule has been scheduled
9. Schedule for Sprint Schedule Meeting 1
2 Schedule of the Sprint planning session
One. The first day of the Sprint has been determined
The last day of the Sprint has been determined
Schedule of Scrum daily meetings
Schedule of Sprint Review meetings
Schedule of the Sprint review meeting
Iv. process of the Conference
1. Open the Sprint schedule to everyone
2. Publish the results of the Sprint review meeting to everyone
3. Publish the results of the Sprint review meeting to everyone
4. Product owner to the team product Description Product Vision
5. Product owner and team work together to determine Sprint goals
6. Start with the first Product backlog entry (story).
7. Discuss the Product backlog entry for an in-depth understanding.
8. Analyze and clear the user acceptance test.
9. Find non-functional requirements (performance, stability ...). ）。
10. Find acceptance criteria.
11. Figure out what level you need to "finish".
12. Get a clear understanding of all aspects of the Backlog entry.
13. Draw a diagram of the required deliverables, including flowcharts, UML diagrams, Freehand sketches, screen UI design, and more.
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, simply by answering the question: "Can we complete the first Backlog entry in this sprint?" "If you can get a positive answer, go ahead and ask for the next backlog entry until you have finished analyzing the last backlog item."
Next, take a break.
After the break:
Expand the process above for the next backlog entry.
End Process:
1. Set aside 20 minutes before the end of the first part of the Sprint planning session.
2. Ask again-this time to be more serious and formal: "Can you complete the first Backlog entry ... The second one, ...? ”
3. If the team thinks they can no longer accept more backlog entries, stop.
4. Now is a very important step: Send product Owner. She has to leave! All people, except the team and Scrum Master, have to leave. Customers, end-users, all others have to leave!
5. When everyone else leaves, ask the team: "Seriously-do you believe you can complete this list?" ”
6. Hopefully the team can now discuss it briefly to see how much work they think they can accomplish.
7. Communicate the results to Product owner and end user. No more talking about it!
v. Outcome of the meeting
1. Prepare the scheduled product Backlog for Sprint planning Session 2
2. Select a good Product backlog entry.
3. Requirements for each backlog entry.

4. User acceptance test for each backlog entry

Agile Development (eight)-Scrum sprint plan meeting 1