Scrum Conference for the basic series of scrum entry

Scrum session 3 reply to the Scrum Basics series

Scrum meetings include sprint scheduling, daily meetings, sprint review sessions, and Sprint retrospectives. These sessions are described in the following sections, which are described in a simple template:

Why, "what" when, "who", "how", that is, why this meeting, the input and output of this meeting, what time to open this meeting, who will attend, how to open this conference.

What is the sprint plan?

The sprint plan will be a scheduled meeting for the current sprint.

What

The Sprint program input is the product backlog, the latest product increments, the team's ability and development rate, and the output for the sprint and sprint targets.

When

The Sprint planning meeting takes place at the beginning of the sprint. For a 4-week sprint, the schedule should be less than 8 hours, a 2-week sprint, and the schedule will be less than 4 hours, and so on.

W.H.O.

The Scrum team (product owner, development team, ScrumMaster) should participate in the sprint program.

How

There are two ways to schedule a sprint meeting.

Way one: traditional two-segment meetings – The first part consists of the product owner and the development team deciding what to accomplish (what), and the second part of the development team to decide how to do it.

Mode two: The circulating –1 product owner and development team Select the top user story of the product backlog, 2 the development team decides whether the user story can be completed according to team capability and previous rate, 3 if it can be done, then split the user story as a task, otherwise choose to end the sprint planning meeting. 4 Repeat the above-mentioned, until the team cannot commit more user stories.

Daily Meeting Why

The team synchronizes information every day

What

The team will be based on the daily meeting, 1. Adjust the Burndown chart (if any) 2. Adjust the tasks in the Sprint backlog or sprint backlog.

When

It is highly recommended to start at a fixed time and place every day

W.H.O.

Development team, ScrumMaster, product owner (optional), other stakeholders (optional)

How

The team circle, facing each other, answer the following 3 questions: 1. What have I done since the last meeting? 2. What will I accomplish from now to the next meeting? 3. What are the obstacles or problems? Throughout the daily session, only pigs (metaphor for the role of scrum) can speak.

Sprint Review

Before the sprint ends, the product owner receives or rejects the development team's sprint goals. The team examines and adjusts the product increments for development.

What

Enter the release plan for the sprint goals and Sprint Backlog, output for potentially deliverable product increments and adjustments.

When

Before Sprint ends

W.H.O.

Development team, ScrumMaster, product owner, other stakeholders (recommended invitations, especially for associated work)

How

The sprint review will be an informal meeting where there is no need to prepare slides for the perfect performance, and the team needs to show the results of their work. In addition, the product owner should not be the first to see the results of the sprint, that is likely in peacetime, the development team each completed a user story, the product owner has reviewed one. Finally, it's just a ritual that gives the team a sense of accomplishment.

Sprint Review Why

The team worked together to make improvements to the development process before the sprint ended.

What

Input is a variety of subjective and objective data, the output is an action plan, it may be placed in a special improvement backlog, may also be placed in the next sprint backlog.

When

Before the sprint is over, it is usually after the sprint review.

W.H.O.

Development team, ScrumMaster, product owner. (generally not recommended for managers to attend)

How

1. Setting up the environment
2. Collecting data
3. Generate Insights
4. Identification of actions
5. Closing the meeting
For details, please refer to the "Agile Review" book (retrospectives)

Basic Scrum Basics Series:

• Scrum origins in the basic series of scrum entry
• Scrum framework for the basic series of scrum entry
• Scrum roles for the basic series of scrum entry
• Scrum Conference for the basic series of scrum entry
• Scrum artifacts for the basic series of scrum entry
• Scrum requirements grooming for the basic series of scrum entry
• Scrum estimates for the basic series of Scrum basics (please expect)

Scrum Conference for the basic series of scrum entry