In the previous issue, we introduced some tips for catching fish. Today, let's take a look at how the "iterative planning meeting" held in each iteration in the agile development process should be held, and how to use the pigtooth fish to carry out the iterative planning meeting efficiently and conveniently. Let's take a look!
After reading this article you will learn:
• What is an iteration planning meeting ?
• What are the inputs to the iteration planning meeting?
• What is the process of the iteration planning meeting?
• What are the outputs of the iteration planning meeting?
• How to hold a good iterative planning meeting with Hogtoothfish ?
01
What is an iteration planning meeting?
The so-called iteration refers to carrying out a series of continuous and regular activities in a specific way and producing specific results. Meeting is the most common work scene in daily work. It involves information transmission, decision-making negotiation and execution within the enterprise, and its importance is self-evident. The iteration planning meeting actually does two things:
1. Decide what needs to be done in the iteration phase?
2. Determine how the development team will work together to complete the Increment to be delivered.
02
What are the inputs to the iteration planning meeting?
Enter the Product Backlog
The product owner (Product Owner) breaks down the needs of customers or users, or the needs of the product itself or the technical needs of the development team, into several product to-do items to generate a product to-do list. Among them, the priority of the product to-do items can only be arranged by the person in charge of the product, and the person in charge of the product arranges according to the value of the product, according to the user's preference and frequency, so that it will not affect the key functions used by the user, nor will it affect the user's experience.
03
What is the process of the iteration planning meeting ?
Agile development is incremental delivery, which may consist of several iteration cycles. The previous iteration cycle ends and a new iteration cycle begins. Iteration planning will serve as a new start, and the following four processes need to be completed.
1. PO defines priority
The product owner prioritizes the product backlog items according to the value of the product . The principle of sorting is to sort them according to the priority of the requirements and the correlation between the requirements and the technical requirements, and then select from the candidate solutions according to certain criteria Choose the best solution.
2. The development team chooses what to do
Based on the product backlog priorities defined by the PO, members of the development team start to claim the requirements to be done from the high-value requirements , and define the acceptance conditions at the same time. Put these requirements into the "to be done" items, and sort the technical requirements, and judge which technical requirements can realize these requirements according to the determined needs and priorities. After determining the requirements, the development team members need to design a variety of action plans to ensure the implementation of the optimal plan.
3. Determine the iteration goal (Sprint Goal)
The agile team determines the iteration goals of this iteration, which makes the development team more focused and focused . Under the guidance of clear goals, the self-management ability of team members is stimulated, prompting the team to work together towards the set goals and realize the highest vision of the team.
4. The development team drives the requirements independently
After determining the iteration goals, the development team members will claim the requirements by themselves and start to work. Put what they are doing in the "Doing" area, and put the completed ones in the "Done" area. In this way, the daily stand-up meeting All team members can see it. Each requirement goes through "To Do"->"Doing"->"Done " until the product backlog requirements are completed in this iteration cycle.
04
What are the outputs of the iteration planning meeting?
Output Sprint Goal
The sprint goal is the goal of this iteration, and the goal is very important for agile management, which will help the development team focus. Because the work in the iteration cycle is carried out around the sprint goal, in the next iteration cycle, the development team will strive around this iteration goal, and other things that are not related to this iteration goal are at least ignored in this iteration cycle.
Output iteration backlog (Sprint Backlog)
After the agile team defines the sprint goal, according to the iteration speed of the development team and the iteration cycle of this iteration (for example, 2 weeks to 4 weeks), the requirements that can be completed are selected from the product backlog according to the priority. The collection of these requirements is called Iterate over todos. Once the sprint goal is determined and the iteration backlog is selected, the rest is the time for the agile team to show its talents.
——The above pictures are from Pixbay, Unsplash, etc.
05
How to hold an iterative planning meeting with Hogfish?
Based on the Scrum-based agile project management function, Hogtooth uses to-do items to plan sprints, visually manages team iterations through task boards, tracks and manages work items, promotes communication among team members, reduces project management costs, and improves communication and collaboration efficiency .
1. Enter the Product Backlog
In the Agile management process of FISH, the product owner first enters the Product Backlog in the roadmap, formulates features (features are services that meet the needs of stakeholders), and through the PI planning meeting, all The organized features are planned, and new features can be created, placed on the backlog and maintained prior to when the agile release train has not yet started.
2. Determine the iteration goal (Sprint Goal)
Then the iteration goals are formulated in the iteration planning meeting, and the goals are realized during the iteration cycle.
3. Focus on things to do
In the iteration planning meeting, the development team uses the to-do bulletin board to associate the subtasks, tasks, and stories of the current iteration, and estimate the man-hours required for each work item of the current iteration. Team members can view the work required for each iteration through the work list. Things done.
4. Drive demand autonomously
The development team independently promotes requirements through the story map. The story map uses epics and versions as the basic context, divides swimming lanes based on epics horizontally, and organizes them vertically by version. Team members can see demand tasks more clearly on the story map, helping the team conveniently and efficiently. Efficiently drive matters to be dealt with in a timely manner.
5. Output iteration backlog
The agile team outputs the iteration to-do items (Sprint Backlog) through the task kanban. The task kanban visualizes the plan execution of the entire iteration, changes the status of the problem by dragging the story card, and clearly shows the shortcomings or bottlenecks in the development and execution process. In Kanban, cards represent stories, tasks, or defects; columns represent development processes, and cards flow from the first step to the last step, which facilitates progress management of the work.
With professional solutions and service capabilities, Totooth has successfully helped several corporate teams improve their R&D efficiency.
Want to experience the flexible and powerful solution of Hogtoothfish right away? You are welcome to contact us, apply for a free trial, and immediately start the journey of easy and efficient digital intelligent development and management.
Zhenzhi Technology (ZKNOW) was hatched by the well-known enterprise digital service provider "Hand Information" in the industry. Inheriting Hande Information's more than 20 years of digital consulting and implementation experience, familiar with the business model, management process, and IT construction of various industries, and depositing Know-How into two products - Yanqianyun and Zhutooth Fish, to help enterprises build "questionable solutions" An intelligent IT operation and maintenance management system, an employee consultation and question-and-answer center, a customer service and complaint platform, and an efficient management tool of "visible progress and smooth collaboration" for digital R&D and projects of enterprises.
Recommended reading / Apply for a trial
Zhenzhi Technology grows together with many excellent companies
