1. Agile development model:
Agile thinking, effective communication, small steps, embracing change, continuous improvement.
Agile project roles:
Product Owner : Mainly responsible for determining the functions of the product and meeting the required standards, specifying the release date of the software and the content of delivery, and having the power to accept or reject the work results of the development team.
Process Manager (Scrum Master) : Mainly responsible for the smooth implementation and progress of the entire Scrum process in the project, as well as clearing the communication barriers between customers and development work, so that customers can directly drive development.
Development Team (Scrum Team) : It is mainly responsible for the development of software products under the Scrum prescribed process. The number of people is controlled at about 5 to 10 people. Each member may be responsible for different technical aspects, but each member must have a strong self. Management ability, and at the same time have a certain ability to express; members can use any way of working, as long as they can achieve the goals of the Sprint.
2. Agile development process:
1. First we need to confirm a PB (Product Backlog, that is, a list of product requirements in priority order), which is the responsibility of the PO (Product Owner)
2. ST (Scrum Team) will estimate and arrange the workload according to the PB list
3. With the PB list, we need to select a Story as the target for this iteration through the Sprint Planning Meeting. The time period for this target is 1 to 4 weeks, and then the Story is detailed. to form a Sprint Backlog
4. The Sprint Backlog is completed by ST, and each member is further refined into smaller tasks according to the Sprint Backlog (the workload of each task can be completed within 2 days)
5. In the process of completing the Sprint Backlog selected in the planning meeting of the Scrum Team, a Daily Scrum Meeting (daily standing meeting) is required, each meeting is controlled for about 15 minutes, everyone must speak, and all members must be presented in person Report what you accomplished yesterday, and promise to all the members what you will accomplish today, and you can also ask questions that cannot be solved. After everyone answers, they should go to the blackboard to update their Sprint burn down (Sprint burn down) picture)
6. To achieve daily integration, that is, to have a version that can be successfully compiled and demonstrated every day; many people may not have used automated daily integration, in fact, TFS has this function, it can support every time When a member performs a check-in operation, the latest version is automatically obtained on the server, and then compiled in the server. If it passes, the unit test code will be executed immediately. If all pass, the version will be released. At this time, a formal check-in is performed. The input operation is saved to TFS. If there is any failure in the middle, the project manager will be notified by email.
7. When a Story is completed, that is, the Sprint Backlog is completed, which means that a Sprint is completed. At this time, we have to conduct a Spint Review Meeting (demo meeting), also known as a review meeting. Both the product owner and the customer must attend ( It is best that the boss of the company also participates), and each member of the Scrum Team must demonstrate to them the software product they have completed (this meeting is very important and must not be cancelled)
8. The last is the Sprint Retrospective Meeting (retrospective meeting), also known as the summary meeting, which takes turns to speak. Everyone has to speak, summarize and discuss the improvements, and put them into the product requirements for the next Sprint.
3. Agile process summary:
- On the first day of the sprint, the goals need to be clearly defined and known to everyone on the team to "make sure to establish consistent goals and make them clear";
- If there is a change in requirements, it will be prioritized to the next iteration, and special cases need to be dealt with to "ensure that this iteration can be completed on time";
- The Scrum Master decomposes the requirements in the iteration into tasks, each task can only have one task leader, and no more than one person-day "ensures that the daily tasks can be evaluated";
- Let the Product Owner directly determine the requirements with the relevant developers, and the Scrum Master needs to participate in "ensure that there is no deviation between the requirements and the implementation";
- Regular daily standing meetings, no more than 15 minutes in length, and not too large in scale "to ensure that the completion of tasks is consistent with the plan";
- Conduct a code review once a day, under the responsibility of the Scrum Master, and notify the relevant developers of the review results the next day to "ensure that the quality of the code does not decline";
- The Scrum Master of each team maintains communication once a day for no more than 15 minutes to "ensure that there is no risk in project management";
- At the end of each iteration, let everyone relax a little, and provide some team activities, such as dinner parties "to ensure that the team can be more cohesive";
- The Scrum Master needs to give the team some commitments, such as project bonuses or special benefits to "ensure that the team is more passionate";
- For employees with abnormal emotions, the Scrum Master needs to communicate with them in time to "make sure not to let one person's emotions affect the entire team";
In addition, as a project manager, you need to continuously strengthen the following 5 points of culture in your team:
- Direction match
- face-to-face communication
- Whole-heartedly
- full trust
- do as promised