Scrum vernacular Summary

Scrum is a well-known process framework in Agile processes and is adopted by many teams.

Scrum uses iterative development. Each iteration goes through a "plan-> Implementation-> Verification-> reflection" process. This is a development process and a process of understanding the project. Such a design actually follows the philosophical cognitive theory.

 

Glossary:

Sprint: each iteration is called a Sprint.

Backlog: a list of requirements.

SM: Scrum Master, the manager of the Scrum process.

PO: The Product Owner.

TEAM: architects, developers, testers, etc.

Chicken: other people, such as CEOS and customers. Pai_^

Story: a relatively independent feature.

Measurement: Some metric values in the process. For example, the number of bugs in the current system.

Events: all events that occur during the process. For example, Mr. Wang put a fart on the bus this morning when everyone was fully engaged in the station ......

 

Role

There are only three roles in Scrum: SM, PO, and Team.

 

Planned MEETING

Scheduled meetings are the most important meetings in Scrum. The duration is generally set to 2-4 weeks.PurposeIt is to determine the task objectives and plans for this Sprint, so that all Members can perform their work more smoothly in the following days. At the same time, this will make the PO more confident.

Main activities: PO makes the product Backlog and explains it at the meeting. At the meeting, the Team evaluated the story points based on their understanding. Finally, it is split into task points. Both the story points and tasks are placed on the small blackboard.

Products (sorted by priority ):

Business objectives, Demo meeting date,

Sprint Backlog (story point list, estimated priority and estimated time, HowToDemo ),

Speed and resource calculation, member list,

The time and place of the Daily website meeting,

Split the story point into tasks.

Note: 

PO is required to attend this meeting! This is because face-to-face communication with the Team is required to plan to determine variable factors such as estimated time, scope, and importance.

The PO and the team should ensure that there is no problem in understanding the story. This ensures that all columns of the backlog are written. The most important thing is the How to demo column.

For technical stories, do not set the priority of the PO. This will lead to a very low priority, which is often very important.

 

Sprint Backlog

Each Sprint requires a Backlog. Backlog is the description of the current requirement. Currently, our project team uses Excel for Backlog:

Figure 1 Backlog Excel table

 

At the same time, use the blackboard for daily adjustments:

Figure 2 small blackboard

 

Daily website

Every day, members of the Scrum Team attend this meeting. The meeting time is less than 15 minutes, and everyone is standing ".

At the conference, everyone mainly describes what they did yesterday, what they will do today, and the support they need. At the same time, each person updates related content on the small blackboard, such:

Figure 3 Update Time

 

Sprint Demo MEETING

The Demo meeting is also a very important meeting.

This is mainly to show PIG the results of the current phase of the project. The meeting should ensure that the business objectives of this Sprint are clearly presented.

This is importantCommunication and feedback.

 

Sprint review meeting

This is also a very important meeting. This meeting will help the teamProgress.

The meeting will classify all the stories, measurements, and events of this Sprint in the following three aspects: Well done, wrong done, and improvement suggestions.

(If the same thing happens in the next Sprint, you should treat it differently .)

 

Others

To systematically learn Scrum, see: Introduction to Scrum-An Agile Process

Also: Scrum and XP from the Trenches

 

I personally understand the above points. If you have any mistakes, please kindly advise. Thank you.