A picture to show you how Agile development scrum

Recently, our company is fully committed to the agile development of scrum, the sense of efficiency is greatly improved, so simply share under agile development scrum.

00. Agile Scrum Manifesto:

One, the focus of a picture

The figure shows the scrum framework, which includes 3 characters, 3 artifacts, 5 activities, 5 values, and one by one below.

Two, 3 roles

corresponding to the upper right corner of the focus graph:

Product Owner: The person who is responsible for the maintenance of the product order and represents the interests of the stakeholders.

Scrum Master: SM, which can be understood as the scrum director, who is responsible for the scrum process, ensures the correct use of scrum and maximizes the benefits of scrum. Generally not translated.

Scrum team: Team of development teams, a cross-functional team of people responsible for self-management development of products.

Three, 3 pieces

corresponding to the lower right corner of the focus map:

Product Backlog: High-level requirements sorted by priority.

Sprint Backlog: A checklist of tasks to complete in a sprint.

Burndown Chart: Burndown chart, showing the length of the sprint all remaining working time of the daily decline of the graph, because the overall is always diminishing the name.

Share our list of tasks Whiteboard:

Iv. 5 Activities

Corresponding to the left bottom of the focus graph:

Sprint: Sprint, a time period (typically between 2 weeks to 1 months), during which the development team completes the development of a promised set of order items.

Sprint Planning Meeting: Plan meetings, at the beginning of each sprint, by the product owner to explain the requirements, and to be estimated by the development team.

Daily Scrum Meeting: The daily station, the team daily communication of the internal short, because generally only 15 minutes and standing to get the name.

The Sprint review:sprint review meeting, which is presented to the product owner and evaluated before the sprint ends.

Retrospective:sprint Review Conference, a meeting on self-Sustainability improvement, held after the end of the sprint.

Share the mood curve of our sprint review meeting:

Share the cards on our sprint planning meeting:

Five, 5 values

Focus: Focus on only a few things over a period of time. Stop starting, Start finishing. The team's ability (energy) is limited, and within limited capacity and limited time, focus on the most valuable things to achieve better results.

Courage: We need the courage to meet all the challenges.

Public: Public progress in the team (Progress), i.e. visualization and transparency, can easily expose risk problems and obstacles. and transparency is the basis of respect and trust.

Commitment: Make a commitment at the beginning of your organization's team and do your best to fulfill your commitments during the iteration.

Respect: The team is sitting together, long-term stability, which helps deepen mutual respect and understanding.

Vi. Scrum development process

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 a number of short iterations, a short iteration cycle called a sprint, and the recommended length for each sprint is 2-4 weeks (internet
Product development can be used for a 1-week sprint). 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. Scrum teams are always first to develop high-value requirements for their customers
。 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 will submit
Potentially deliverable product increments. Scrum originates from software development projects, but it is suitable for any complex or innovative project.

Vii. Summary

Developers have been through a lot of projects, whether agile or not, often can successfully complete project development. In many of these projects, we have experienced many software development models, each with its own ornate academic name, waterfalls, prototypes, iterations, spirals, agility, and sheep-herding. In fact, the biggest difference between these models is not in the results, but in the process of achieving the ease of the goal.

For example, everyone from home to the company to work, can choose a variety of ways, such as driving, electric cars or bicycles. Either way, we will eventually arrive at the company at the prescribed time of work. The difference is that driving is probably the quickest, but it has to endure rush hour traffic. Electric cars are smart and convenient, but pay attention to safety. Bicycles are the slowest, but keep fit. And which way to go to work depends on the road and my mood of the day.

The so-called project management or software development model, I think the biggest goal is not to complete the software development, but how to let the team in a healthier and easier way to achieve the goal. The only criterion for evaluating what is healthy and easy is the number of overtime.
So, please remove the agile gorgeous coat:

1. The station must be brief, the time must be fixed.

2. Before the iteration plan, the core personnel participate in the analysis and the plan, prepares adequately, the other person listens and questions.

3. Remove any information system and use the whiteboard.

4. Please extend the review cycle, not too frequent, really miserable.

5. If you do not have a flat, bureaucratic tendency, then don't be agile, in other ways.

6. There are many types of meetings in agile, and meetings are not for programmers to do. appropriate deletions, and no need to participate every time, the time back to the programmer.

7. Don't be agile for agility, it's just a methodology, not a universal.

Here are the highlights:

The so-called project management or software development model, I think the biggest goal is not to complete the software development, but how to let the team in a healthier and easier way to achieve the goal. The only criterion for evaluating what is healthy and easy is the number of overtime.

A picture to show you how Agile development scrum