Step by Step Agile development: 5. 4 Types of Scrum conferences

Included in the scrum meeting: scheduled meetings, daily stops, review meetings, and retrospective meetings.

1. Sprint Program (Sprint planning)

In scrum, the Sprint planning meeting has two parts:
1. Decide what work needs to be done?
2. Decide how the work is done?

Part I: What do I need to do?
Attendees: Team, Scrum Master, Product Owner
The first part of the meeting, the product owner introduces the development team to the ordered product backlog, which is understood collectively by the entire Scrum team.
The number of product backlog items that need to be completed in a sprint is fully determined by the development team. How much work can only be decided by the development team, the product owner or any other person cannot impose more effort on the development team.

Part II: How to get the job done?
Attendees: Team, Scrum Master
The second part of the meeting, the development team needs to decide how to implement the next product increment, based on the current "completed definition". They have enough design and planning to be confident that they can do all the work in the sprint.
Deciding how to get the job done is the responsibility of the development team, and deciding what to do is the responsibility of the product owner.

The Sprint planning meeting ultimately requires the scrum team to agree on the amount and complexity of the work that the sprint needs to complete, resulting in a to-do list that is the sprint backlog.
The sprint to-do list is a product backlog that needs to be completed in the current sprint, and includes a plan for the team to do so.

2. Daily station meeting (Daily Scrum)

The development team is self-organizing and confirms that they can still achieve sprint goals through the daily station.
Each development team member needs to provide the following three-point information:

• From yesterday's standing meeting to now, I finished what;
• From now to tomorrow's standing meeting, what I plan to accomplish;
• What has hindered my progress.

Daily scrum typically does not exceed 15 minutes.
There may be brief clarification and answers to the questions in daily scrum, but there should be no discussion of any topic.
Daily scrum is neither reported to the management nor reported to the product owner or ScrumMaster. It is a communication meeting within the development team to ensure that they have a consistent understanding of the status quo.
Only members of the scrum team, including ScrumMaster and product owners, can speak at the meeting. Other interested people can come to the audit.

3. Sprint Review Meeting (Sprint Review)

At the end of the sprint, the scrum team and the people involved reviewed the Sprint's output. All scrum meetings are time-limited, and the recommended duration for a sprint review meeting is one hours per week in the sprint (for example, a sprint has a 2-week duration, and the sprint review meeting is 2 hours).
Everyone can comment at the Sprint review meeting. The product owner will make the final decision on the future and adjust the product backlog appropriately.
The Sprint Review Conference presents an overview of the current product increments for everyone. The product to-do list is usually adjusted in the Sprint review meeting.

4. Sprint back to Xu Conference (Sprint retrospective)

At the end of each sprint, the scrum team gathers together to open a sprint review meeting to review how the team is doing in terms of processes, relationships, and tools. The team identifies which ones are doing well, what is not, and identify potential improvements to make plans for future improvements. All scrum meetings are time-limited, and the recommended duration for a sprint retrospective is one hours per week in the sprint (the Translator notes: For example, a sprint contains 2 weeks, the Sprint review session is 2 hours long).
Scrum teams are always improving their own processes within the framework of scrum.

Summary: Each sprint repeats the scrum cycle continuously

Scrum team members (including product owners, development teams, and ScrumMaster) work together to complete a series of product increments that take a short period of time called sprints. Each product increment meets the acceptance criteria for the product owner and meets the team's "done definition". All work comes from the product backlog.
The sprint always starts with the sprint planning meeting, and the team develops a sprint to-do List (Sprintbacklog) in the meeting. The team is self-organizing to develop, leveraging daily scrum meetings to coordinate and ensure that the team produces the best product increments. The team prepares for the next sprint planning meeting by combing the product backlog list. At the end of the sprint there will be a sprint review meeting and a sprint review meeting to review the product and team processes.

Agile Journey 2014 Beijing Station-a journey with agile thinking

Date: December 20 09:00-18:00
Location: No. 6th, Shang-Xi Road, Haidian District, Beijing, China Association Research Institute

Focus on Agile Journey Beijing station , sweep

More Agile Tours 2014 cities Please pay attention: Agile Travel China

Step by Step Agile development: 5. 4 Types of Scrum conferences