Agile Development Framework - Scrum
At present, there are many agile development frameworks to choose from in the industry, and these development frameworks provide very detailed agile guidance,
such as:
- XP, extreme programming
- Crystal Methods, crystal method
- FDD, Feature Driven Development
- ASD, Adaptive Software Development
- …
Currently the most popular agile development framework in the industry is Scrum.
What is Scrum?
It is an iterative incremental software development process
The more important thing in Scrum is Sprint.
In Scrum, Sprint can be considered as an iteration of a project.
The length of a Sprint is generally 2-4 weeks, fixed and not allowed to be extended or shortened.
In Scrum it includes:
- three roles
- four activities
- three artifacts
three roles
product owner
Responsible for building and maintaining product features
- Constantly communicate and collaborate with customers to determine what the product should do, define user needs, and prioritize needs
- must have decision-making power
- Have an understanding of the workflow and technical level within the team
scrum coach
Ensuring the team can deliver faster
- Be able to stimulate team morale, promote teamwork, and ensure team efficiency
- Be able to help the team eliminate distractions and ensure the smooth progress of the sprint goals.
- The coach is not a micromanager, but more like a servant to the team
Scrum team
5-9 people team - self-organization, equality
- In a Sprint, members should try to remain stable
four activities
Sprint Planning Meeting
Marks the start of the sprint (generally no more than 4 hours in length)
- The Scrum team selects and understands the work to be done
- Agenda 1: Introduce the product by the product owner; determine what tasks will be completed in the Sprint; clarify the highest priority tasks in the product backlog; clarify the sprint goals; determine the number of tasks to be completed in this round of sprints
- Agenda 2: The Scrum team studies how to complete the tasks to be delivered in this round of sprint; the team reaches a consensus on the number and complexity of tasks to be completed in the sprint; fully understands and estimates the requirements; converts the contents of the product backlog into software development specific tasks in the process.
Daily stand-up meeting The
daily stand-up meeting is also called the daily stand-up meeting. Since it usually starts in the morning, it is also called the morning meeting.
Team members take turns speaking at the meeting, answering: - what did i do yesterday
- what am i going to do today
- What difficulties did I encounter in my work and whether it hindered the progress of my work.
- Not recommended for more than 15 minutes
Sprint review meeting
- It is used to demonstrate the product functions developed in this round of sprint, and is accepted by the product owner.
If you want to change a certain function during the demonstration process, you can add it to the new requirements. If you find defects, you can add it to the in the defect list. - It is recommended to control it within 2 hours.
Sprint retrospective meeting
- It is used to give the team regular self-examination, also called project review.
- It is recommended to keep it within 30 minutes.
three artifacts
Product Backlog
An organized to-do list
- Covers every known requirement in product development and should be the only source of product requirement changes
- The Product Owner is the only Product Backlog Owner
- Others can provide input, but only the product owner has the authority to make decisions
In a Product Backlog there may be the following:
- functional requirements or non-functional requirements
- defect
- technical debt
A better product backlog should follow the "DEEP principle":
DEEP principle
The DEEP principle is a general term for the following four principles:
- Detailed appropriately: The product backlog should be thicker and thinner at the far end, and the farther away the requirements should be thicker, and the closer the requirements to be developed should be more detailed.
- Estimated: There is a workload estimate and technical risk estimate for each item
- Emergent: The Product Backlog is not static, but emergent
- Prioritized
Sprint Backlog
- Also called an iteration backlog, it is a selection of work items from the product backlog for the current iteration.
- Essentially a target plan for the current iteration
- Very detailed and prioritized
- The development team estimates effort, identifies sprint backlog priorities, and more
- The Sprint Backlog can be modified during the iterative development process as circumstances change.
- The completion of the sprint backlog can reflect the progress of the current iteration of the development team in real time
Product increment
- After the current iteration is completed, a product increment is formed. A Product Increment is the sum of all Product Backlogs completed for an Iteration, and the sum of the value of Product Increments for all previous Iterations.
- Fully tested, potentially releasable; new increments must be finalized
- The Scrum team needs to have a common standard for "done" and ensure that the quality is good enough and can be released together with the previous increment