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 includes 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. Sprint
The selected requirements are analyzed, discussed, and estimated at the sprint planning meeting to obtain a sprint task list, which we call 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 deliver valuable software to our customers as soon as possible and continuously.
• You are welcome to propose changes to your needs, even after the project is developed. Be good at making use of demand changes to help customers gain competitive advantages.
• Continuously deliver available software, ranging from weeks to months, and the shorter the period, the better.
• Business personnel and developers must work together during the project process.
• Be good at motivating project personnel, give them the necessary environment and support, and believe they can complete the task.
• Face-to-face communication is the most effective way for both within and between teams.
• Available Software is the main indicator for measuring progress.
• The agile process advocates sustainable development. The project team, developers, and users should be able to maintain a stable and stable pace of development.
• 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 they can be more effective and adjust their behaviors accordingly.

Features of scrum
• Scrum defines a very simple 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 way to detect and remove 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 more than 1 thousand developers and executors.
• Scrum makes every participant 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 with a fixed cycle.
• Product design, development, and testing are all completed during the sprint.
• Deliver software that can work at the end of the sprint.
• Changes are not allowed 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 review 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 release date and content.
• Responsible for the product's profitability of the product (ROI.
• Determine the function priority based on market value.
• Adjust functions and priorities for each sprint as needed (adjusted before each sprint starts ).
• Accept or reject the work of the development team.

The product owner participates in 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.
• Ensures good collaboration between roles and responsibilities.
• Solves the obstacles in team development.
• Serves as an interface between the Team and the external team to prevent external interference to the team members.
• Ensure that the development process is as planned and daily scrum, sprint review and sprint planning meetings are organized.

Scrum role team
• Generally, the number is 5-9
• Cross-functional teams (including developers, testers, and user interface designers)
• Team members must be full-time. (In some cases, such as the database administrator)
• Within the scope of the project wizard, you have the right to do anything and ensure that you have reached the sprint goal.
• High self-organizational skills.
• Demonstrate product functions to the product owner.
• The composition of team members cannot be changed within the sprint.

Sprint plan meeting of scrum ceremony
> Sort priorities:
• Analyze and evaluate product backlog
• Determine the 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 the 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 organizes meetings at this stage and invites relevant stakeholders.
• The team displays the functions completed in the sprint
• Functions and architecture are generally presented through on-site demonstration
• Not too formal
• No PPT required
• Generally within 2 hours
• All team members are required
• Everyone can be invited

Sprint Review Meeting of scrum ceremony
• The Team regularly inspects itself and finds out what is good and what is bad.
• Generally, the duration is 15-30 minutes.
• Each sprint is required
• All participants: scrum master, product owner, team, potential customers or other stakeholders

At the sprint review 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.
• Generally, user stories are used to represent backlog entries.
• Ideally, each requirement item is of value to the customers or users of the Product
• Backlog entries are prioritized by Business Value
• Priorities are arranged by product owners.
• The priority sorting should be updated at the end of each Sprint

Sprint backlog of scrum objects
The Sprint backlog defines the sprint goal and defines the specific tasks 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
• Each team member can modify the sprint backlog to add, delete, or modify tasks.

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-consuming workload gradually decreases, the estimated error or missing workload may increase at the beginning.

Extended scrum
• Generally, the number of people in a team is limited to 5-9. Large projects can adopt multiple teams and expand Scrum through team of teams.
• Factors Affecting Scaling: team size, project type, project cycle, and team distribution.
• Scrum was used for projects with more than 1000 teams.