Case 6 of using scrum for project management

Document directory

• 1. Purpose of the meeting
• 2. Meeting process
• 3. How to improve estimation efficiency in meetings

Introduction:

I will track and record a series of articles that I am currently working on using a complete scrum management project. There will be some lessons to learn and encourage readers to learn from each other. Hai Han is still recommended for some incorrect or poorly written information. Of course, I hope you can provide more valuable comments. The support of readers is my greatest motivation. (One, two, three, four, five, six)

========================================================== ========================================================== ================

This is the last article in this series. I will share some conclusions of the project summary meeting with you:

Meeting topics

1. How to enable Iteration Planning Meeting iteration plan MEETING

1. What is the purpose of the meeting?

2. What is the meeting process?

3. How to improve estimation efficiency in meetings

Ii. agile practices in this project

1. Establish a communication mechanism

2. Development Process Definition

3. agile preaching Training

4. All team members are active (RD is directly involved in the design)

5. Early participation in testing

I. Iteration Planning meeting1. PURPOSE OF THE MEETING

Ü all members understand story, and Po explains all story of this iteration.

Ü estimate the size of this iteration

Ü define the scope. What will we accomplish next iteration?

Ü formulate this iteration plan and generate the corrected sprint backlog

Ü generate a task dashboard or something similar to it (we use an Excel dashboard)

2. Meeting process

2.1 preparations before the meeting:

2.1.1 select the sprint backlog list that may be completed in this iteration meeting based on the product backlog (This list may include the customer feedback after the previous iteration demonstration and technical improvement reconstruction. The list must be sorted by priority ).

2.1.2 send the sprint backlog list to all the team members in advance. You can preview the list and raise questions about story in the list as much as possible.

2.1.3 prior to the meeting, we should also explain each story and evaluate the planned time based on the number and difficulty of story to be discussed in this planned meeting. In this way, the host can control the time during the meeting. If the time-out period expires, you can skip this step.

2.2 calculate the resource time available for this iteration, and calculate the SP (story point) that this iteration may complete based on the previous iteration experience ).

2.3 ask the po or SA to explain the requirements in the initial sprint backlog order. After the explanation, all the team members and the po or SA will perform Q &. Then, the team evaluated the story and estimated the SP.

2.3.1 Q & A tips. We have summarized a Q & A checklist as follows (we agree that the last three points are the most important ):

Ü what functions do I need? What are the special requirements? Such as performance

Ü is there a UI? Are there any special operation requirements?

Ü what is the relationship with other functions in the system?

Ü what is the checkpoint? The most important test cases

Ü acceptance criteria or demo

2.3.2 estimation techniques (listed separately later in this article)

2.4 After estimating one item, proceed with the next one until the team's iteration time is saturated.

2.5 Let's finally confirm the final sprint backlog and maintain the task dashboard or something similar to it (we use an Excel dashboard ).

2.6 when maintaining the dashboard, if there is sufficient time, it is best that every story should be decomposed into tasks. The Team has no objection to reading the tasks once.

2.7 exit the meeting after confirmation.

3. How to improve estimation efficiency in meetings

The PO explains the requirements until they can be evaluated, refine the content, and communicate with each other separately;

Only sp evaluation of story, not Task Evaluation;

After the Po clarifies the requirement and implements Q & A, the evaluation card method is used for SP evaluation;

Three six, six-minute Po to explain the demand, six-minute Q & A, 30 seconds to play the card. If there is an objection to 6-minute PK (there is no absolute, in short, we need to control the time );

Ii. agile practices

The reason for the release is summarized. The four steps are as follows:

1. Lock code;

2. determine the scope;

3. to do list verification;

4. Deliverable scope.

Action:

1. One day before release:

2. Clearly define the scope of release;

3. Pass the test and lock the code;

4. full preparation, list check items, one-to-one check, including installation manual, database script, package, clean environment (Virtual Machine) installation;

5. Release Date:

6. sanity test execution is in place;

7. verification and confirmation of release scope;

Bytes ---------------------------------------------------------------------------------------------------

Finally, I would like to thank you again, the company, the team, and my wife for their support !!! Your support is my greatest motivation.