Scrum and XP in smoke (1)

Scrum standards of Nokia:

1. Iterations must have a fixed time box, which cannot exceed six weeks.
2. The end of each iteration,CodeMust be tested by QA.
3. The SCRUM team must have a product manager who knows who the team is.
4. The product owner must have the product's backlog, including the team's estimation.
5. The team must have a burn-out chart and understand their own production efficiency.
6. In a sprint, outsiders cannot interfere with the team's work.

Backlog is the core of scrum. Basically, it is a list of requirements, stories, or features that are sorted by importance. It must be what the customer wants, it is described by the customer's voice. None of the entries is a story. We recommend that each story contain these fields:

1. ID (Uniform identifier)
2. Name)
3. IMP (importance)
4. Est (initial estimation)
5. How to demo (how to make a demo)
6. Notes (Others)

Each story has 3 + 1 variable (range, importance, estimation) + quality, and in any case cannot compromise quality.

Quality is divided into internal quality and external quality:

1. External quality is perceptible to users, such as slow running and confusing interfaces.
2. Internal Quality is generally an element invisible to users. It has a profound impact on the maintainability of the system, such as system design consistency, test coverage rate, and code readability.

Remember, building beautiful pavilions on a loose beach will never be able. Experience has proved that sacrificing internal quality is a bad idea, saving a little time for the next day, you will always pay for it.

Everything in scrum has a time box and must be delivered at that time.

"This sprint is not very good for everyone, but we should see its positive impact. The entire team has benefited a lot and the next iteration meeting will be more efficient ."

Learn to arrange work according to the time box, learn to develop various reasonable time boxes, which is equally effective for the sprint meeting length.

A typical sprint schedule, with a 10-minute rest every hour:

1. The 30-minute general introduction summarizes the product's backlog.
2. Estimated time of 20 minutes.
3. 1 hour story selection, computing productivity.
4. One-hour standing meeting schedule and split the story into tasks.

An ideal sprint can be 3 weeks in length. (currently, the company's daily build version is released to the testing department for testing. It should be an automated testing process, the manual test should be the normal version released every month)

Half-dead targets are better than nothing.

The number of stories contained in a sprint is determined by the Team, rather than the product owner or others, but the product owner has an impact on what story should be placed in the sprint.

Script that automatically generates the story card: http://blog.crisp.se/henrikkniberg/2007/12/18/1197973740000.html

Planned number of points: 0, 1/2, 1, 2, 3, 5, 8, 13, 20, 40, 100 ,? And coffee.