Leangoo 's agile tools cover the entire process of agile project development, including small-scale team agile development and Scrum of Scrums large-scale agile.
With the increasing popularity of SAFe, Leangoo provides a complete SAFe framework function this time, including: Program Backlog, PI planning, iteration planning, iteration execution, iteration statistics, etc.
What is SAFe?
SAFe (Scaled Agile Framework) is the most widely used large-scale agile framework in the world. Blending Lean, Agile, and DevOps, SAFe is a knowledge base of proven Lean-Agile practices and capabilities.
SAFe was born in 2011. In just 12 years, there have been more than 1.2 million SAFe certified professionals around the world, and it has continued to grow rapidly, and has been recognized by more and more professionals around the world. More than 20,000 well-known corporate giants around the world are using SAFe, from technology, software, finance, medical care to aviation and manufacturing. 70% of Forbes Fortune 100 companies are using SAFe. SAFe is the world's most popular and accepted large-scale agile framework.
Then let's take a look at how to use Leangoo to do SAFe large-scale agile~
SAFe project template
In Leangoo, after creating a project with the SAFe project template, the system will automatically create three Kanban boards, namely: Program Backlog, Scrum of Scrums, and Defect Kanban. The team can directly use these Kanban boards to quickly start project collaboration.
Program Backlog Signboard
The Program Backlog Kanban is a staging area for future feature stories (Feature), which can be used to meet user needs and deliver business benefits for an Agile Release Train (ART).
In the Program Backlog Kanban, we can add multiple PIs, (each list represents a PI) and feature stories that need to be completed in the PI.
Feature stories with high priority are placed in the earlier PI, and those that need to be prioritized in the PI are placed in the upper position, or the priority of each feature story is marked with a label.
New PI column
On the Program Backlog board, the system creates 2 PI columns by default. We can click the "New PI" button to create a new PI, fill in the PI cycle and the number of iterations, and the number of iterations is the number of iteration lists in the subsequently created Team Backlog Kanban.
Modify PI information
After the PI column is created, we can modify the PI information at any time. For example, start PI, modify PI, end PI, delete PI, etc.
Note: PI information modification is not supported for the completed PI.
View PI information
There will be a "PI" icon to the left of the list header. The different colors of the icon indicate the different states of the PI, and a PI in progress will have a green horizontal line at the top of its list to highlight its status.
When the mouse hovers over the "PI" icon, the basic information of the PI will be displayed, such as: PI status, start date, end date, number of completed cards, number of unfinished cards, completed work, and unfinished work.
Start PI
After filling in the feature story in the Program Backlog Kanban, PI planning can be carried out.
Before PI planning, we need to start a PI first. When starting PI, you need to fill in and reconfirm the PI cycle and the number of iterations in the Team Backlog board to be created.
Note: A PI cannot be started until another PI is finished.
Starting the PI system will create a Team Backlog Kanban corresponding to the PI for each Scrum team.
PI planning
After starting a PI in the Program Backlog Kanban, the feature stories in the PI column can be planned to the Team Backlog Kanban corresponding to the PI.
Click the "PI Planning" button, and all the Team Backlogs corresponding to the PI will appear on the right side of the board. Drag the feature stories in the PI column to the Team Backlog. After the operation is completed, the feature stories will be referenced to the Team Backlog board.
After the PI planning is completed, enter the Team Backlog Kanban of a certain team. We have introduced and placed feature stories in independent swim lanes through planning, and use the swim lanes to horizontally correspond to user stories split by feature stories.
The team splits these feature stories into smaller user stories, and then prepares for subsequent iteration planning.
Before iteration planning, the team needs to estimate the user stories to be done and add workload, and then everyone decides how much workload stories need to be completed according to the past team speed.
start iteration
After the feature stories are disassembled, the team can sort out the user stories with higher priority. After sorting out, before iteration planning, we need to start an iteration. Note: An iteration cannot be started until another iteration has finished.
After the iteration is started, the system will create an iteration Kanban corresponding to the Team Backlog Kanban iteration column by default, and the task cards in the Team Backlog iteration column will be referenced to the iteration Kanban by default.
iteration planning
After adding a user story card in the iteration column of the Team Backlog kanban, you can click the "Iteration Planning" button, drag the task card to the corresponding iteration, and the card will be referenced to the iteration kanban.
iterative execution
After the iteration starts, enter the iteration Kanban, and you can see that the referenced user stories have been placed in independent swim lanes, and the swim lanes can horizontally correspond to user stories and split tasks.
Based on the relevant information of these user stories (such as check items and information in the description), the team disassembles them into smaller tasks, and then everyone receives development.
Through the flow of the list, the progress and completion of the task are reflected.
Scrum of Scrums sign
Scrum of Scrums Kanban is a Scrum team for cross-team collaboration. Scrum of Scrums regularly holds Scrum of Scrums standing meetings according to the rhythm, usually 2-3 times a week, and the frequency can also be increased as needed.
Usually the Scrum Master participates. The meeting identifies impediments or cross-team dependencies that prevent the team from completing its sprint goal.
defect management
In the iterative process, we not only need to make relevant user stories, but also need to solve the defects in the process. Therefore, we can use a defect-type kanban to manage daily defects, and then plan the defects on the iterative kanban during iteration planning.
The defects of the current iteration are recommended to be placed on the iteration kanban of the current iteration, and repaired before the end of the iteration.
"Defect Kanban" usually stores defects left after release, defects reported by customers, etc.
For defect planning in large-scale scenarios, first select the target team that needs to be planned, then plan the defects into the iterative Kanban of this team, then switch to the next team, and complete the defect planning of multiple teams in turn
Sprint review
In agile development, each of our iteration teams will hold a retrospective meeting. At this time, the team can put the reviewed items into the Sprint review board, and then gradually solve the problems that need to be improved while maintaining efficient collaboration in subsequent iterations.
View the overview of the Program Backlog Kanban
On the project statistics page, you can see the workload completion of each feature story in each PI in the Program Backlog Kanban.
View defect distribution
The defect distribution can also be seen on the project statistics page, and the defect statistics chart can show the distribution of tasks under each list in the defect kanban in the project.
In Leangoo, tags are often used as categories for tasks. Can also be used as a priority for marking tasks, etc.
The defect kanban also supports statistics of defects through labels.
Iteration progress under each PI
Leangoo provides iteration progress statistics, we can see the iteration completion status of each Team Backlog under each PI in the project.
team speed
Team Velocity is the amount of work a Scrum Team actually gets done in an Sprint (often using story points as the unit of Team Velocity).
In each iteration, Leangoo will automatically record the workload completed in the current iteration, and automatically generate a visual statistical chart of the team rate, so that the team can understand and analyze the trend of team efficiency changes
Iteration completion rate
The completion rate of iteration is to count the completion of each iteration Kanban in the project.
Configure Kanban cycle and burndown chart, Leangoo will automatically count the completion rate of each iteration of Kanban, and automatically generate a visual statistical chart, so that the management can see the completion rate of each iteration at a glance
job distribution
Work distribution statistics show the task distribution of project members in all kanban/mind maps of the project.
Through work distribution statistics, managers can quickly and intuitively understand the workload and work progress status of each project member, helping the team to collaborate more efficiently.
View and set Kanban status
Kanban status and status switching functions are newly added in Kanban. There are four statuses of Kanban: "not started", "in progress", "finished"', and "not set".
At present, only the initial state of the Kanban in the SAFe project is "Not Started". For other types of projects, the system defaults to "Not Set", and you can enter the Kanban to set it yourself.
In addition to supporting SAFe large-scale agile, Leangoo also provides SAFe large-scale agile training.