Scrum Study Notes

Scrum Study Notes

Agility has been on fire for a long time, but I have never had the opportunity to practice it. Now I have started to team up and practice it. Haha, first study the rules ~~

What is scrum?
Scrum is an agile development framework and an incremental and iterative development process. In this framework, the entire development cycle contains several small down generation cycles. Each small down generation cycle is called a sprint. The recommended length of each sprint is 2 to 4 weeks. In scrum, product backlog is used to manage product or project requirements. product backlog is a list of requirements sorted by business value. The list entries are usually in the form of user stories. The SCRUM development team always develops high value requirements for customers first. In each sprint, the scrum Development Team selects the most valuable requirements from the product backlog for development. The selected requirements in the sprint are analyzed, discussed, and estimated at the sprint planning meeting to obtain a sprint task list, which we call a sprint backlog. At the end of each iteration, the scrum team will deliver potentially deliverable product increments.

Agile value-agile 4 Declaration
? Individuals and interactions over processes and tools
? Available Software over complete documentation
? Customer collaboration over contract negotiation
? Response to changes over compliance plans


12 principles of agile Value
? Our highest goal is to satisfy our customers by delivering valuable software as soon as possible and continuously.
? You are welcome to change your requirements, even after the project is developed. Be good at making use of demand changes to help customers gain competitive advantages.
? We need to continuously deliver available software, ranging from weeks to months, and the shorter the period, the better.
? In the project process, business personnel and developers must work together.
? Be good at motivating project personnel, give them the necessary environment and support, and believe they can complete the task.
? The most effective communication method is face-to-face communication between teams.
? Available software is the main indicator to measure the progress.
? The agile process advocates sustainable development. The project owner, developers, and users should be able to maintain a stable and stable process.
? Improving technology and improving design will improve agility.
? To be concise, minimize unnecessary work. This is an art.
? The best architecture, requirements, and design come from self-organizing teams.
? The team should regularly reflect on how it can be more effective and adjust the behavior of the Team accordingly.

Features of scrum
? Scrum defines a very easy development process.
? Scrum is a summary of the existing design process.
? Based on teams, scrum is a way to develop systems and products iteratively and incrementally when demand changes rapidly.
? Scrum is a process that controls chaos caused by conflicts of interests and needs.
? Scrum is a way to improve communication and optimize cooperation.
? Scrum is a method of checking and removing barriers in product development and production.
? Scrum is a way to maximize productivity.
? Scrum applies to a single project to the entire enterprise. Scrum can control and organize multiple associated product development and project implementation processes with over developers and practitioners.
? Scrum makes everyone and everyone proud of what they do and their contributions, and brings them to the optimal level.

Sprints
? The SCRUM project process consists of a series of sprints.
? The Sprint length is generally limited to 2-4 weeks.
? Maintain a good pace through a fixed cycle.
? Product design, development, and trial are all completed during the sprint.
? Deliver software that can work at the end of the sprint.
? You do not agree to the change during the sprint.

Scrum framework
Three roles: product owner, scrum master, and team
Four Ceremonies: Sprint plan meeting, daily site meeting, sprint Review Meeting, sprint recall meeting
Three items: product backlog, sprint backlog, and burned-out diagram

Product owner of scrum role
The product owner has the following responsibilities:
? Determine the features of the product.
? Determine the publication date and content.
? Responsible for the product's profitability of the product (ROI.
? Determine the function priority based on market value.
? For each sprint, adjust the function and priority as needed (before each sprint starts ).
? Accept or reject the work of the development team.

Product owner development and scrum planning.

Scrum master role
As a team leader and product owner, they work closely together to help team members in a timely manner. He must:
? Ensure that team resources are fully available and all are highly productive.
? Ensure good collaboration between roles and responsibilities.
? Solve the obstacles in team development.
? As an interface between the Team and the external team, the external team members are shielded from interference.
? Ensure that the development process is as planned and daily scrum, sprint review and sprint planning meetings are organized.

Scrum role team
? In normal cases, the number of people is about 5-9.
? Cross-functional teams (including developers, trial testers, and user interface designers)
? Team members must be full-time. (In some cases, for example, the database administrator)
? Within the scope of the project wizard, you have the right to do whatever you want to achieve the sprint goal.
? High self-organizational skills.
? Demonstrate product functions to the product owner.
? The composition of team members does not agree with the change within the sprint.

Sprint plan meeting of scrum ceremony
> Sort priorities:
? Analyze and evaluate product backlog
? Determine sprint target

> Sprint plan:
? Determine how to achieve the sprint goal (design ).
? Create a sprint backlog (task) based on the product's backlog entries (user stories, functions ).
? Estimate tasks in sprint backlog by hour

Sprint Review Meeting of scrum ceremony
The Sprint review will be used to demonstrate the product features developed in this sprint to the product owner. The produc owner will organize meetings at this stage and invite relevant stakeholders to participate.
? The team displays the functions completed in the sprint.
? The function and architecture are usually presented through on-site demonstration.
? Not too formal
? No PPT required
? Generally within 2 hours
? All team members must join
? Can invite all persons to shujia

Sprint recall meeting of scrum ceremony
? The Team regularly checks itself and finds out what is good and what is bad.
? Generally, the time range is 15-30 minutes.
? Every Sprint has to do
? All shujia: scrum master, product owner, team, potential customers or other stakeholders

At the sprint recall meeting, all the members discussed which good practices can be started, which bad ones cannot be continued, and which good practices should be carried forward.

Product backlog of scrum objects
? A list of requirements.
? In general, user stories are used to represent backlog entries.
? Ideally, each requirement item is of value to the customer or user of the product.
? Backlog entries are prioritized based on business value
? Priorities are arranged by product owners.
? Update the priority at the end of each sprint.

Sprint backlog of scrum objects
The Sprint backlog defines the sprint goal and understands the detailed tasks that need to be completed during the sprint process.
Manage the sprint backlog:
? The team members select their own tasks instead of assigning tasks.
? Update the remaining workload estimates for each task every day.
? Every team member can modify the sprint backlog and add? Delete or modify a task

Burn down chart)
The burnout diagram intuitively reflects the remaining workload during the sprint. the Y axis indicates the remaining work, and the X axis indicates the sprint time. As the time consumption gradually decreases, the workload may increase at the beginning because of estimation errors or omissions.

Extended scrum
? In general, the number of people in a team is limited to 5-9. Large projects can be scaled with multiple teams and scaled through team of teams.
? Factors that affect Scaling: team size, project type, project cycle, and team distribution.
? Scrum was used for projects with more than 1000 people.