A Sprint plan meeting is held on the first day of the sprint. This meeting is divided into two parts. Plan meeting 1 is attended by Po, Sm, and team, it is mainly to select the established product backlog that needs to be placed under the current sprint from the product backlog, and then the SM and team participate in the planning meeting 2, split the story of the established product backlog into tasks for estimation, PO can also participate in this section to learn the specific development details. Below I will list the main contents of the meeting. (The following meeting content is from scrum checklists)
Meeting content Sprint plan meeting 1
Together with the team, the product owner develops the sprint goal and the established product backlog based on the previous evaluation results.
Target
Set sprint goals and established product backlog
Meeting preparation
-
- Participants: product owner, scrum master, and all team members
-
- Problems in product backlog are sorted by priority
-
- Problems in backlog evaluated
-
- Publish the product backlog to everyone in the meeting to ensure that it can be obtained.
- Who are expected to be absent (for example, on vacation)
-
- Make sure the room environment is suitable for group discussion
-
- Everyone can obtain the results of the last sprint review meeting and sprint review meeting.
-
- The Sprint schedule has been scheduled.
- Schedule of sprint scheduled meeting 1
- Schedule of sprint scheduled meeting 2
- The first day of the sprint is determined.
- The last day of the sprint is determined.
- Schedule of daily scrum meetings
- Schedule of sprint review meetings
- Schedule of sprint review meeting
-
- (Optional) Prepare a dingtalk board for the established backlog: A dingtalk board of at least 2x2 meters, card and sticker, highlighter
-
- (Optional) cards used as scheduled cards
Meeting process(4 hours)
- Publish the sprint schedule to everyone
- Publish the results of the sprint review meeting to all
- Publish the sprint review meeting results to everyone
- Product owner describes product prospects to the team
- Product owners and teams work together to determine sprint goals
- If there is a problem missing in the backlog: The product owner has the permission to add the problem to the backlog.
- If the product backlog is not evaluated at all: select the problem that you think is the smallest use case in the backlog, and assign two story points for the workload. Allocate the story point of other problems in the backlog according to the workload standard of this minimum case.
- If some problems in the backlog are not evaluated: the number of story points for these problems is evaluated based on the workload of other problems.
- If the items in the product backlog have not been properly sorted by priority: the product owner sorts the items in the product backlog by priority.
- Product owners and team members acknowledge the sprint goals and established product backlog.
Meeting results
Prepare the established product backlog for sprint Planning Meeting 2
Sprint Planning Meeting 2
In sprint Planning Meeting 2, the team refined each item in the backlog of the established product into multiple tasks. Each task can be completed within one day.
Target
Determine all tasks, generate the sprint backlog, and confirm the sprint target
Meeting preparation
- Participants: scrum master, all members of the team,Product owner (can be informed of all problems)
- For Task Planning, refer to the backlog of the product.
- (Optional) Prepare a dingtalk board for the established backlog: A dingtalk board of at least 2x2 meters, card and sticker, highlighter
Meeting process(4 hours)
- Team members can separate tasks from various problems in the backlog.
- Make sure all the details are taken into account: coding, testing,CodeReview, meeting, learning new technologies, compiling documents
- If the task takes more than one day: Try to split the task into several small tasks
- If the team thinks that there are too many items in the sprint backlog: the problem in the backlog is deleted with the product owner
- If the team considers that there are too few items in the sprint backlog: work with the product owner to select the most important issue from the product backlog and add it to the sprint backlog.
- The team confirms the sprint Objectives
Meeting results
- The Sprint target and sprint backlog are open to everyone in the company.
- All team members can obtain the tasks in the sprint backlog.
Recommended:Online e-books you may need
Agile individual Sina apron:Http://q.t.sina.com.cn/135484
You are welcome to reprint it. Please note: Reprinted fromAgile personal website
