Development Management checklists (19)-agile development scrum Sprint plan meeting 2

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

Through this article, you can check
1. process and steps of your scrum Sprint plan meeting 2
2. Results of scrum Sprint plan Meeting II

This meeting is based on sprint planning meeting 1.

I. Purpose of the meeting 

The work of the Meeting is mainly designed. The product development team can complete the design work for the solution they want to implement. At the end of the meeting, the Team knows how to build the features they want to develop in the current Sprint
1. Determine the sprint Length
It takes a short time. As a result, the company will become "agile", which is conducive to the random response. Short sprint = short feedback cycle = more frequent delivery = more frequent customer feedback = less time spent on the wrong direction = faster learning and improvement, and numerous benefits come one after another.
2. Determine the sprint target
For some reason, it is indeed difficult to set sprint goals. But I found it worthwhile to squeeze it out like a toothpaste. Half-dead targets are no better than none.
3. Determine the story to be included in the sprint
Deciding which stories need to be completed in this sprint is a major activity of the sprint planning meeting.
4. Set the time and place of the daily meeting
5. determine the size of each item in the backlog.
6. The team members can know what will happen in the next stage of the project from the meeting.
7. trim the backlog content: break down each backlog project in a reasonable way to gain a deeper understanding.
Ii. Meeting Time 

In a sprint, this meeting takes 60 minutes each week. This meeting will be held after the first part of the sprint planning meeting is completed. Lunch can be used as a longer break for two meetings. However, the first part of the sprint planning meeting must be completed on the same day.

Iii. Preparations for the meeting 

1. Invite Attendees:
Product owner
Scrum master
All team members
2. For Task Planning, refer to the backlog of the product.
Iv. Meeting process 

1. Start with the first backlog entry.
Make sure that you understand the customer's requirements correctly.
This backlog entry is designed based on the following similar issues:
(1) What interfaces do we need to compile?
(2) What architecture should we create?
(3) What tables do we need to update?
(4) What components do we need to update or compile?
(5) ensure that all details of the work are taken into account
Encoding
Test
Code Review
Meeting
Learning new technologies
Document Writing
(6) If the task takes more than one day, try to split the task into several small tasks.


2. When the Team knows exactly how to develop this function, they can switch to the next backlog entry. 
In the last 10 minutes of the meeting, the team members used instant posts to write preliminary tasks. This helps team members know where to start the next job. Place these tasks on the task board. Do not estimate these tasks
V. meeting results 

1. Sprint objectives.
2. List of team members (and their input level, if not 100% ).
3. The estimated product backlog is the list of stories included in the sprint ).
4. Confirm the sprint demo date.
5. determine the time and place for daily scrum meetings.
6. Issues to be clarified.

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

<Development Management checklists> by dylove98 @ Development Management checklists