Agile development takes the evolution of users’ needs as the core, and adopts an iterative and step-by-step method for software development.
1. Product owner
It is mainly responsible for determining the function of the product and meeting the required standards, specifying the release date and delivery content of the software, and has the right to accept or reject the work results of the development team.
2. Process Manager (scrum Master)
It is mainly responsible for the smooth implementation and progress of the whole scrum process in the project, as well as removing the communication barriers between customers and development work, so that customers can directly drive development.
3. Scrum team
It is mainly responsible for the development of software products under the process specified by scrum, and the number of people is controlled at about 5 ~ 10. Each member may be responsible for different technical aspects, but each member must have strong self-management ability and certain expression ability; Members can work in any way, as long as they can achieve sprint’s goals.
Four kinds of meetings
1. Sprint planning meeting
Select some user stories from the product backlog as the goal of this iteration. The time cycle of this goal is 1 ~ 4 weeks, and then refine this user story to form a sprint backlog;
- Split the user story into development tasks
User story is a description of the user’s perspective; Development task is a specific executable development work, which is described from the development perspective. The two will be different.
- Evaluation hours
It emphasizes self-organization, so it adopts the way of solitaire. Generally, half a day is used as a story point (twice the number of days), and further refinement is not necessary. So take the number on the card as the number of days, which is the most convenient.
- Rank priority
It emphasizes self-organization, communication and coordination, which are solved by developers themselves, and there is no special project coordination.
- The planned meeting shall be controlled within 4 hours, that is, half a day (1 story point);
2. Daily scrum meeting
Each meeting shall be controlled at about 15 minutes. Everyone must speak and report to all members what you accomplished yesterday, and promise all members what you want to accomplish today. At the same time, you can also put forward any unsolvable problems. After everyone answers, they should go to the blackboard and update their sprint burn down chart
Now there are all kinds of tools to make task Kanban, and there is no need for pieces of paper to fly all over the sky.
3. Srpint review meeting, also known as review meeting
Product leaders and customers should participate (preferably the boss of the company), and each member of Scrum team should demonstrate their completed software products to them.
Similarly, the meeting is controlled within 4 hours, that is, half a day (1 story point);
4. Sprint retrospective meeting, also known as summary meeting
Take turns to speak. Everyone should speak, summarize and discuss improvements, and put them into the product requirements of the next round of sprint;
Some personal thoughts
Although scrum opposes the culture, it does not mean that scrum does not need communication and documentation. Instead, Scrum places more emphasis on communication and documentation. For example, interface documents for front and back-end debugging are necessary, and are likely to go further. For example, let the test directly input the data required by the smoking case through the background, and complete the smoking test when developing;
Four hours are needed for planning, demonstration and summary meetings; If no consensus can be reached within 4 hours, it is better to move out first and postpone the implementation. But landing is more important than anything.
The daily station meeting looks very simple, and it is the most difficult to implement in practice. There will be various alternative ways to be proposed, but in the end, it will make the station a mere formality. In fact, this is the most useful aspect of scrum.
The spring cycle is recommended to be 3 weeks, with another week for product trial, technical pre research, requirements and design review. A late, rhythmic, can last. Although it is called agile development, it is definitely not simple and fast.
Scrum emphasizes the strength of the team, similar to the special team, and does not highlight individual heroism. Therefore, most of the company’s performance appraisal, such as KPI, is not help but resistance to the implementation of scrum.
A feasible way is team investigation. For example, after the planning meeting, you should give a reward for sprint’s completion (even if only 1000 yuan is incentive). When it is completed on time, the Po accepts the product and can cash it. As for how to distribute the 1000 yuan reward within the team, just like the usual problems and task communication, the team members solve it by themselves.
This seemingly flawed incentive measure with only reward and no punishment is the most effective. The core of Scrum is to deliver products, but what attracts developers most is this self-organizing management method. (take care of yourself. Of course, it’s human nature to reward without punishment)