Excerpt: https://www.cnblogs.com/yixinjishu/p/12161359.html
Scrum agile development processes of: 3 roles, 5 meetings, 12 principles
In this paper, several aspects of the definition and purpose of Scrum, Agile Manifesto, staff roles in Scrum, Scrum development process, agile 12 principles to help you understand the whole process of Scrum agile development.
A, Scrum definition and object
Scrum is a framework for the development and maintenance of complex products, is an incremental, iterative development process, the purpose is to allow developers like to play football as fast and passionate, through teamwork, improve work efficiency. Through effective interaction between team to create value for the enterprise.
Second, the Agile Manifesto
In fact, prior to publication, "Agile Manifesto", many agile practices already exist and are used, for example: Scrum, XP, KanBan and so on. The reason why the issue "Agile Manifesto" because these practices are in place to promote agile development alone, rather than in the form of a consortium, and there is no uniform guidelines. So 17 agility, co-founder decided to publish "Agile Manifesto", to jointly promote the agile development movement in the world. Here is the Agile Manifesto four words:
Three, Scrum roles of staff
3 Role
Scrum of staff divided into three roles: Product Owner (Product Owner), Scrum Master, the development team (Team).
- Product Owner: Define all the product features, product releases and decide what date, input-output responsible for the product, according to market changes prioritized the need to develop functional, reasonably adjust product features and iteration order, agree or refuse iteration delivery.
- ScrumMaster: ScrumMaster is not the project manager, his power is not assigned tasks, no power assessment, the authority is not under command, members of his guidance of the project team to do things in accordance with the principles of Scrum method, leading the team to complete the practice of Scrum and reflect its value , exclude the difficulties encountered by the team to ensure the team qualified for their work, and to maintain efficient productivity, making the team work closely together so that individuals have the ability to work a team many functions to protect the team is not subject to external influence for no reason.
- Development Team: Classic team has a 5-9 person team includes programmers, testers, user experience design, etc., in a team relationship iteration should be fixed, individual adjustment of functions can occur when a new iteration start, team self-organization and management (self-organizing, self-driven), team members are full-time job.
Four, Scrum development process
(Picture from the network)
The waterfall model is different from the development process is divided into requirements, design, coding, testing phase, Scrum the entire development process is divided into several iterations (called Sprint, Sprint), generally for a period of 2 to 4 weeks, the most common is two weeks . Scrum is not a time to focus on the completion of a process, but all in every part of the process must be focused completed within this period of time. Requirements, design, coding, testing, on-line must be completed in one iteration, each iteration must produce software that can work.
4.1 five meetings
Scrum entire development process is divided into five conferences:
1) todo organize meetings (Backlog Grooming Meeting)
Before you start the iteration planning meeting was held three days, Product Owner and Scrum Master must participate in, the key developer or architect need to participate; time control in 30 minutes to 1 hour.
By the Product Owner to a group of user stories team hope to achieve in the next iteration, in accordance with the order described to realize the presence of team members, Scrum Master with the presence of members of the analysis of user stories, made clear that the team believes local demand is not clear, Product Owner field notes , after the completion, Scrum Master and architects, as well as the presence of members of the analysis of user stories which need technical tasks include establishing Scrum Master first sub-tasks, easy iteration planning meeting when the team can more accurately estimate the task story points.
At the end of the meeting, Product Owner to ensure that before the start of the iteration planning meeting team issues raised can be resolved, the meeting focused on the need to strengthen or if the team found the perfect place, Product Owner there are two to three days may be reinforced, and not a waste of time to do the iteration planning meeting this thing.
2) Iteration Planning Meeting (Sprint Planning Meeting)
Product Owner to establish a list of product features (Product Backlog). Product features list is a set entry requirements, it must describe the value from the customer point of view, and prioritizes.
Scrum Master convene stakeholders will convene iteration planning, iteration planning meeting was held in the first day of each iteration, the objective is to select Backlog of this iteration and the current iteration of the estimated workload.
Product Owner one by one to explain the most important product features, the development team to estimate the amount of work needed Backlog, until this iteration workload saturated. Product Owner and participate in the discussion and answer questions related needs, but does not interfere with the estimation results. Players claim the task (or negotiated by the head of distribution), to complete the task independently or together with others; meeting time control in 1-2 hours.
3) Daily station will (Standup Meeting)
Internal team use daily legislature to communicate progress, the end of the 15 minutes, the development team used burndown chart to show overall progress; if there is no special reason, iterative period no change in daily stop at team members need to answer the following three questions :
- What did you do yesterday?
- What are you going to do today?
- You need to have a place to help you?
These are committed to each other team members.
4) will be assessed (Retrospective Meeting)
Group show iteration results of the work to the person in charge of the product, the product owner to give comments and feedback. Whether a user story to be able to assess the successful delivery of task completion. The whole team needs to participate, ScrumMaster, product owner, group, and possibly customers, time control in 1-2 hours.
5) will reflect on (Retrospective Meeting)
Held after each iteration brief reflection will summarize what things well, what things do not. Well done retention, poor abandoned. Meeting concluded that: What started doing, keep doing what, what do stop, the general control of 15-30 minutes.
Scrum is a set of development process, is an agile, mainly the implementation of Man, emphasizing self-organizing, self-driven, carefully understand the only constant in the practical application, in order to understand the true meaning of Scrum, the Scrum good use.
12 4.2 Principles
Here are 12 principles of agile development, these 12 principles of agile development for guidance Program software development process, but also on the Agile Manifesto explained with a practical sense, I hope you carefully understand in practical applications.
We follow these guidelines:
- Our highest goal is that through early and continuous delivery of valuable software to meet customers.
- Welcome to the demand made changes - even late in the project development. To make good use of the demand for change, to help customers gain a competitive advantage.
- To continue to deliver software available, period ranging from several weeks to several months, and the shorter the better.
- Course of the project, business people and developers must work together.
- To be good at motivating project personnel, giving them the required environment and support, and believe that they can complete the task.
- Whether it is within a team or between teams, the most effective way to communicate face to face conversation.
- Available software is the primary measure of progress.
- Agile processes promote sustainable development. Side project, developers, and users should be able to maintain long-lasting stability in the rate of progress.
- The improvement of technology and to constantly improve the design will enhance agility.
- To do simple, namely the maximum extent possible to reduce unnecessary work. This is an art.
- Best architectures, requirements, and designs emerge from self-organizing teams.
- Team to regularly reflect on how we can do it more efficiently, and adjust the behavior of the team accordingly.
Author: Sven handsome
Source: CreditEase Institute of Technology
In this paper, several aspects of the definition and purpose of Scrum, Agile Manifesto, staff roles in Scrum, Scrum development process, agile 12 principles to help you understand the whole process of Scrum agile development.
A, Scrum definition and object
Scrum is a framework for the development and maintenance of complex products, is an incremental, iterative development process, the purpose is to allow developers like to play football as fast and passionate, through teamwork, improve work efficiency. Through effective interaction between team to create value for the enterprise.
Second, the Agile Manifesto
In fact, prior to publication, "Agile Manifesto", many agile practices already exist and are used, for example: Scrum, XP, KanBan and so on. The reason why the issue "Agile Manifesto" because these practices are in place to promote agile development alone, rather than in the form of a consortium, and there is no uniform guidelines. So 17 agility, co-founder decided to publish "Agile Manifesto", to jointly promote the agile development movement in the world. Here is the Agile Manifesto four words:
Three, Scrum roles of staff
3 Role
Scrum of staff divided into three roles: Product Owner (Product Owner), Scrum Master, the development team (Team).
- Product Owner: Define all the product features, product releases and decide what date, input-output responsible for the product, according to market changes prioritized the need to develop functional, reasonably adjust product features and iteration order, agree or refuse iteration delivery.
- ScrumMaster: ScrumMaster is not the project manager, his power is not assigned tasks, no power assessment, the authority is not under command, members of his guidance of the project team to do things in accordance with the principles of Scrum method, leading the team to complete the practice of Scrum and reflect its value , exclude the difficulties encountered by the team to ensure the team qualified for their work, and to maintain efficient productivity, making the team work closely together so that individuals have the ability to work a team many functions to protect the team is not subject to external influence for no reason.
- Development Team: Classic team has a 5-9 person team includes programmers, testers, user experience design, etc., in a team relationship iteration should be fixed, individual adjustment of functions can occur when a new iteration start, team self-organization and management (self-organizing, self-driven), team members are full-time job.
Four, Scrum development process
(Picture from the network)
The waterfall model is different from the development process is divided into requirements, design, coding, testing phase, Scrum the entire development process is divided into several iterations (called Sprint, Sprint), generally for a period of 2 to 4 weeks, the most common is two weeks . Scrum is not a time to focus on the completion of a process, but all in every part of the process must be focused completed within this period of time. Requirements, design, coding, testing, on-line must be completed in one iteration, each iteration must produce software that can work.
4.1 five meetings
Scrum entire development process is divided into five conferences:
1) todo organize meetings (Backlog Grooming Meeting)
Before you start the iteration planning meeting was held three days, Product Owner and Scrum Master must participate in, the key developer or architect need to participate; time control in 30 minutes to 1 hour.
By the Product Owner to a group of user stories team hope to achieve in the next iteration, in accordance with the order described to realize the presence of team members, Scrum Master with the presence of members of the analysis of user stories, made clear that the team believes local demand is not clear, Product Owner field notes , after the completion, Scrum Master and architects, as well as the presence of members of the analysis of user stories which need technical tasks include establishing Scrum Master first sub-tasks, easy iteration planning meeting when the team can more accurately estimate the task story points.
At the end of the meeting, Product Owner to ensure that before the start of the iteration planning meeting team issues raised can be resolved, the meeting focused on the need to strengthen or if the team found the perfect place, Product Owner there are two to three days may be reinforced, and not a waste of time to do the iteration planning meeting this thing.
2) Iteration Planning Meeting (Sprint Planning Meeting)
Product Owner to establish a list of product features (Product Backlog). Product features list is a set entry requirements, it must describe the value from the customer point of view, and prioritizes.
Scrum Master convene stakeholders will convene iteration planning, iteration planning meeting was held in the first day of each iteration, the objective is to select Backlog of this iteration and the current iteration of the estimated workload.
Product Owner one by one to explain the most important product features, the development team to estimate the amount of work needed Backlog, until this iteration workload saturated. Product Owner and participate in the discussion and answer questions related needs, but does not interfere with the estimation results. Players claim the task (or negotiated by the head of distribution), to complete the task independently or together with others; meeting time control in 1-2 hours.
3) Daily station will (Standup Meeting)
Internal team use daily legislature to communicate progress, the end of the 15 minutes, the development team used burndown chart to show overall progress; if there is no special reason, iterative period no change in daily stop at team members need to answer the following three questions :
- What did you do yesterday?
- What are you going to do today?
- You need to have a place to help you?
These are committed to each other team members.
4) will be assessed (Retrospective Meeting)
Group show iteration results of the work to the person in charge of the product, the product owner to give comments and feedback. Whether a user story to be able to assess the successful delivery of task completion. The whole team needs to participate, ScrumMaster, product owner, group, and possibly customers, time control in 1-2 hours.
5) will reflect on (Retrospective Meeting)
Held after each iteration brief reflection will summarize what things well, what things do not. Well done retention, poor abandoned. Meeting concluded that: What started doing, keep doing what, what do stop, the general control of 15-30 minutes.
Scrum is a set of development process, is an agile, mainly the implementation of Man, emphasizing self-organizing, self-driven, carefully understand the only constant in the practical application, in order to understand the true meaning of Scrum, the Scrum good use.
12 4.2 Principles
Here are 12 principles of agile development, these 12 principles of agile development for guidance Program software development process, but also on the Agile Manifesto explained with a practical sense, I hope you carefully understand in practical applications.
We follow these guidelines:
- Our highest goal is that through early and continuous delivery of valuable software to meet customers.
- Welcome to the demand made changes - even late in the project development. To make good use of the demand for change, to help customers gain a competitive advantage.
- To continue to deliver software available, period ranging from several weeks to several months, and the shorter the better.
- Course of the project, business people and developers must work together.
- To be good at motivating project personnel, giving them the required environment and support, and believe that they can complete the task.
- Whether it is within a team or between teams, the most effective way to communicate face to face conversation.
- Available software is the primary measure of progress.
- Agile processes promote sustainable development. Side project, developers, and users should be able to maintain long-lasting stability in the rate of progress.
- The improvement of technology and to constantly improve the design will enhance agility.
- To do simple, namely the maximum extent possible to reduce unnecessary work. This is an art.
- Best architectures, requirements, and designs emerge from self-organizing teams.
- Team to regularly reflect on how we can do it more efficiently, and adjust the behavior of the team accordingly.
Author: Sven handsome
Source: CreditEase Institute of Technology