The contents of Scrum are organized as follows: (continuous update and supplement)
table of Contents
Agile values (more emphasis on the left)
definition
Scrum is an iterative incremental software development process, usually used for agile software development.
Roles
Scrum Master (Scrum promoter):
- Scrum coaches and team leaders ensure that the team operates Scrum reasonably and help the team remove obstacles encountered in the implementation process.
Owner (Product Manager):
- Determine the direction and vision of the product, define the content, priority and delivery time of the product release, and be responsible for the return on product investment.
Developer (Developers):
- It is composed of developers, with a number of 5-9 people, and the team has all the skills needed to deliver usable software.
Four meetings
Sprint Planing
- Explain the requirements.
- Select PBI (product backlog item), that is, the customer selects important PBI.
- Disassemble PBI to SBI (sprint backlog item).
- Discuss the working hours of each SBI.
- The team selects this Sprint task.
Daily Scrum ( Ask yourself three questions )
- From yesterday's Daily Scrum to this moment, what have I done?
- From this moment to the Daily Scrum tomorrow, what do I plan to accomplish?
- Is there any difficulty hindering my progress?
Sprint Review
- After the Sprint is over, everyone will review the output of this Sprint together. Everyone is free to express their opinions and assist the product owner to make the final decision on the future work. And according to the actual situation, appropriately adjust the product to-do list.
Sprint Retrospective
- After a Sprint is over, review the effectiveness of the team in terms of process and communication. Let's discuss together, which ones are well done and which ones need improvement?
Implementation process
- Step1. Draft Vision
- Step2. Maintain Backlog
- Step3. Split Sprint
- Step4. Run Sprint Plan
- Step5. Maintain Daily Scrum
- Step6. Sprint Review
- Step7. Retrospective
tool
1. Stand-up
2. Kanban
3. Demo
4. User story
- Role: Who wants to use this feature.
- Activity: What kind of function needs to be completed.
- Commercial value: Why is this function needed, and what value does this function bring?
5. Continuous Integration
General practice
- The customer becomes part of the development team.
- Like all other forms of agile software processes, Scrum has frequent intermediate deliverables that contain functions that can work. This allows customers to get working software earlier, and allows the project to change project requirements to adapt to changing needs.
- The development team frequently assesses risks and develops mitigation plans. Risk mitigation, monitoring and management are carried out in accordance with commitments at each stage.
- The plan and module development should be transparent so that everyone knows who is responsible for what and when it will be completed.
- Participants should meet frequently to track the progress of the project-balanced (release, customer, employee, process) dashboard updates-stakeholder updates. You must have an early warning mechanism, such as warning when delivery may be delayed.
- Don't hide the problem. Recognizing or speaking out any unforeseen problems will not be punished.
- You must be fully committed in the workplace and during working hours. – Doing more work does not mean that you need to work longer.
Agile values (more emphasis on the left)
- Individuals and interactions - processes and tools
- Working software - detailed documentation
- Customer cooperation-contract negotiation
- Respond to changes - follow the plan
Agile principles
- Customer satisfaction
- concise
- Face-to-face communication
- Continuous improvement
- Self-organizing
- Cooperation
- Delivery value
- Adapt to change
- Reflective review
- Short cycle
- Incentive trust
- Steady pace
Related views
- Agile is an idea, an attitude, advocating simple design, fast delivery, value orientation, and response to changes. A way of thinking: defined by values, guided by principles, and embodied through many different practices. It is more an attitude than a process, an atmosphere rather than a method.
- For us, the most important thing is to meet customer needs through early and continuous delivery of valuable software.
- We welcome changes in requirements, even in the later stages of development. Agile processes can manage change and maintain the customer's competitive advantage.
- Always deliver working software, from a few weeks to a few months, the shorter the time scale, the better.
- Business people and developers should always work together day and night throughout the project.
- Revolve around high-spirited people for software development, provide developers with a suitable environment, meet their needs, and trust them to complete their tasks.
- The most efficient and effective way of communicating information in a development team is face-to-face conversation.
- Working software is the main measure of progress.
- Agile processes promote sustainable development. Investors, developers, and users should always maintain a constant rhythm.
- The constant pursuit of technical excellence and good design will help increase agility.
- Simplicity-the art of minimizing the workload is essential.
- The best architecture, requirements, and design are derived from self-organized teams.
- At regular intervals, the team should summarize how to be more efficient, and then adjust its behavior accordingly.
- Agile is to always only do things that are useful for products and projects.
- Agile development is not a set of immutable standardized processes, but more of an adaptive and self-optimizing process concept. Different teams have different processes, so before implementation, they must be adjusted according to the current state of their team.