The first experience of scrum

First, preface

The two-month entry, as a newcomer, did not attend a morning scrum meeting.

The biggest feeling is that one day at noon, take my development brother suddenly said the product this afternoon to test, I suddenly was ignorant.

This is the biggest team I've experienced without taking part in scrum, which leads to a difference in information.

As the team grew, the company began to split. All of us now have to take part in scrum, but the original team was split and the number of people controlling scrum was within a certain range.

Ii. Scrum Training

The training Scurm is explained by the experienced old staff.

Summary Highlights: (Reference: HTTP://WWW.SCRUMCN.COM/AGILE/SCRUM-KNOWLEDGE-LIBRARY/SCRUM.HTML#TAB-ID-1)

Scrum is a framework for developing and sustaining complex products and is an incremental, iterative development process. In this framework, the entire development process consists of several short iteration cycles, a short iteration cycle called a sprint, and the recommended length for each sprint is 2-4 weeks (Internet product development can use a sprint of 1 weeks). In scrum, the product backlog is used to manage product requirements, and the product backlog is a list of requirements sorted by business value, and the form of the list entry is typically a user story. The scrum team is always first to develop requirements that are of high value to the customer. In Sprint, the scrum team picks the highest-priority requirements from the product backlog for development. The selected requirements are discussed, analyzed and estimated at the Sprint planning meeting to get a list of tasks that we call the sprint backlog. At the end of each iteration, the scrum team submits a potentially deliverable product increment. Scrum originates from software development projects, but it is suitable for any complex or innovative project.

3 roles in a scrum framework:

1. Products Owner (product owner)
2. Scrum Master
3. Scrum Team

3 artifacts in a scrum framework:

1. Product Backlog
2. Sprintbacklog
3. Burndown Chart (burn-down chart)

5 meetings in the scrum framework:

1. Sprint Planning Conference (Sprint planning meeting)
2. Daily Station (Daily Scrum meeting)
3. Sprint Review Conference (Sprint Review meeting)
4. Sprint Review Conference (Sprint retrospective meeting)
5. Product Backlog Grooming meeting (products backlog Refinement)

There are other concepts, such as agile estimating size, user stories, cross-functional teams, and so on.

Iii. Discussion

A: The team has also worked on the paper Burndown chart, very time-consuming, and the paper flies.

B: Agile Estimating time, if you really want everyone involved, the day is almost out of time, so, the results of each estimate is not allowed.

C: Open scrum time every day, we used to be before work, many are morning, late or early will be punished.

D: In fact, so much training, scrum is a team, what activity meetings are forms, the ultimate goal is to make everyone more united, better to complete each stage of the goal. If there is a certain incentive policy, so that everyone has the protagonist consciousness, and if because of their late early or did not complete the task and affect everyone, there will be guilt, it is the feeling of the team to everyone tightly together, so as to achieve these effects. Otherwise it is a mere formality, but also waste everyone's time.

。。。

Iv. Experience

The next iteration, which will be involved in scrum, has not yet been witnessed.

For my most intuitive impact, is to know what the team everyone is doing, if their own development process encountered in the business of docking, but also know about who docking.

The first experience of scrum