Practical demonstration: How to use ONES to develop a Scrum iteration plan?

The core of agile development is iteration. Each iteration includes steps such as planning, design, development, and testing. Through frequent releases and tracking feedback from the previous iteration, the product is gradually improved.

With the deepening of research and development practice, agile has derived a lot of development methods, including: Scrum, lean method, extreme programming (XP), Kanban, etc. Among them, Scrum is undoubtedly the most successful agile method at present, because it provides A set of fixed roles and work processes are more easily accepted by most teams.

Today, we will take you to understand what Scrum is, and how to use ONES for iterative planning and implement Scrum efficiently. Let's take a look~

Scrum is an iterative and incremental software development process that covers the production, delivery, and management of products, typically used in agile development.

• Step 1: The product owner is responsible for sorting out the feedback and needs from stakeholders, and sorting them according to their priorities to form a Product Backlog, that is, product to-do items;
• Step 2: After iteration planning, meeting analysis, and estimating the Product Backlog, the Sprint Backlog is formed, that is, the iteration to-do items;
• Step 3: Delivery of potentially releasable product increments by the team within a fixed development cycle;
• Step 4: After the iteration review and iteration review, end the current iteration and start the next iteration.

(1) Three roles

Role 1: Product Owner

The product owner's core job is to be accountable for the value delivered by the team. His role is to define requirements, requirements prioritization, requirements acceptance criteria, and product release content and dates.

Role 2: Agile Coach (Scrum Master)

The core job of an agile coach is to help the team become familiar with and master the Scrum framework, continuously improve, and work well and quickly.

Role 3: Scrum Team

The R&D team includes developers, testers, business analysts and other roles required for development. The size is usually 5-9 people. It has the characteristics of self-organization and self-management, and is responsible for the deliverables.

(2) Three major workpieces

Artifact 1: Product Backlog

The product backlog is a list of requirements from a product perspective. It is maintained, added, removed, and prioritized by the product owner. Each requirement needs to describe its external value. User stories are one of the best practices.

Artifact 2: Sprint Backlog

The Sprint backlog is derived from the product backlog. In the Sprint planning meeting, the team needs to discuss, analyze and estimate the selected requirements, get the corresponding task list, that is, the Sprint BackIog, and define the "done" standard together.

Artifact 3: Potentially deliverable product increment (Increment)

After the sprint, the release-ready product feature increment needs to be presented at the iteration review meeting.

(3) Five major events

Event 1: Sprint

Think of a Sprint or Iteration as a special event, and its cycle is usually 2-4 weeks.

Event 2: Sprint Planning Meeting

The core topic of the Sprint planning meeting is to estimate the requirements in the product Backlog according to the product backlog, determine the goals and scope to be achieved in the next sprint, and form the iterative backlog.

Event 3: Sprint Daily Standup

Daily stand-up meetings are held at fixed times, 15 minutes a day, with the goal of promoting information sharing and transparency within the team.

Team members briefly answer 3 questions: What did I do yesterday? What am I planning to do today? Am I currently running into obstacles, are obstacles preventing me from accomplishing my goals? No in-depth discussion of the issues.

Event 4: Sprint Review

The Sprint Review is held at the end of the sprint, and the user reviews the results of the current period. It requires the participation of the whole team and invites relevant stakeholders, and the product owner can refuse to accept the results.

Event 5: Sprint Retrospective

The meeting is held after the iteration review meeting. It also requires the participation of the entire team to review the sprint together, summarize experiences and lessons, and form a list of feasible improvements.

(4) 5 Values

Open: Scrum makes everything in the project open to everyone, and transparency of information is of great help in improving collaboration efficiency.
Respect: Everyone has a unique background and experience, and respect for each team member is the foundation of project trust.
Courage: Members have the courage to make commitments, fulfill commitments, and accept respect from others completed on schedule

In general, Scrum is a framework for solving complex problems, allowing us to deliver the most valuable products in the shortest time in an iterative and incremental manner. The specific process should be flexibly adjusted according to the actual situation of the team, and should not be rigidly applied.

(1) Determine the iterative goal

It is important to establish a goal, this goal can be "make more money", "impress the CEO", "complete the top three stories" or "make the system good enough to be released as a beta version to real users" use" and so on.

(2) Determine the iteration cycle

It is recommended to maintain a stable iteration cycle throughout the duration of the project, which will allow the team to follow a stable development rhythm and also help to accurately estimate the time required for project completion.

In ONES, we can create new iterations and set the iteration cycle and attributes. The recommended cycle is 1 to 4 weeks, which can be adjusted flexibly based on the team's situation.

(3) Determine the iteration scale

After the iteration is created, we need to determine how many requirements can be completed in each iteration. Based on the data in ONES Performance performance management, we can understand how many story points, how many requirements, and how many man-hours the team has completed in historical iterations, so as to accurately plan the current iteration.

(4) Assess product demand

Estimate the story points and working hours in the product Backlog, and clarify the boundary, scope, acceptance and completion standards of the requirements. If the requirements are unclear, the product owner will explain them. Once they do not meet the requirements, the team has the right to reject the requirements and not join. This iteration.

In this process, we can use ONES to filter out all the work items in the list that are not planned for iteration, and sort them by priority to form a product to-do list, and use and pass the "planning to iteration" function to select the good ones. Requirements are planned into already created iterations.

(1) Divide the requirements into tasks

With the help of agile Kanban under ONES Project iteration, we can split requirements into tasks and assign them to different owners.

(2) Estimate working hours for tasks

In addition, we can also estimate the working hours of their respective tasks, and intuitively control the progress of the tasks through the statistics of the remaining working hours of the iteration and the burndown chart.

After this work is done, our iteration planning meeting is over. In this link, the agile coach is responsible for grasping the meeting process and time. If the iteration cycle is 2 weeks, it is recommended that the duration of the iteration planning meeting should not exceed 2 hours.

With professional solutions and service capabilities, ONES has successfully helped more than 200,000 medium and large teams in various industries such as Inspur Software, China Merchants Fund, Kweichow Moutai, and China Telecom to improve their R&D efficiency.