Example of Leangoo Agile Project Management Scenario

 Leangoo is a professional agile development management tool that provides end-to-end agile R&D management solutions, covering agile requirements management, task collaboration, progress tracking, statistical measurement, etc.

Leangoo is quick to learn and low in implementation cost, which can help enterprises quickly implement agile, improve quality and efficiency, shorten cycle time, and accelerate innovation.

• Leangoo is different from traditional project management software. Leangoo realizes the visual kanban collaboration of what you see is what you get based on the latest web real-time communication technology.

•Project requirements, tasks, problems, and defects are all placed on the Kanban board as cards, through which the visual and transparent management can be realized, and real-time collaboration can be realized through the real-time synchronization of the cards on the Kanban board.

•Project progress and status are updated in real time from multiple perspectives, and visualized.

• Leangoo is built by China's top agile R&D and project management consulting team, with 20 years of practical experience in agile R&D and project management, helping enterprises to build digital R&D and project management systems and platforms at low cost and efficiently, and improve enterprise R&D efficiency , Accelerate the delivery of business value.

•Leangoo can support agile R&D management process, project management, lightweight collaboration and other scenarios.

​​​​​​About Scrum agile R&D management scenarios:

Here is an example of Scrum agile single-team agile development:

1. Create a product roadmap

First we need to create a product roadmap for this project. The product roadmap is a high-level strategic plan that describes how the product may develop and grow in the future. The product roadmap ensures that the entire product team continues to focus on the goals of the product , to help the product owner grasp the strategic direction of the product, adjust product priority and product planning.

There are multiple milestones in the product roadmap, and milestones are the phased goals on the product roadmap to achieve the product vision. Agile milestones are usually planned on a cadence, such as a milestone every two months, or a milestone every quarter.

"We use Leangoo's agile development tools to manage agile projects. If you want to be agile, you can use Leangoo to lead songs."

The following figure is an example of an agile kanban board for a product roadmap:


After the product roadmap is created, the epic stories on the product roadmap are usually relatively large stories, so we need to plan the epic stories into the product Backlog so that the team can split the epic stories in the product Backlog and divide them Disassemble into smaller user stories, so that the team can gradually complete them in subsequent Sprint iterations.

2. Product roadmap planning

 In Leangoo, you can directly use the "Milestone Planning" button to open the milestone planning pop-up box, and drag and drop the epic stories in the "Milestone" list to the corresponding "Milestone-Product Backlog", so that these epic stories will be Refer to the product Backlog Kanban to complete the milestone planning. 

3. Split user stories in the product Backlog

In the Product Backlog Kanban, the team splits the planned epic stories into smaller user stories, and then prepares for subsequent Sprint planning.

An epic story has a swimlane, and the swimlane horizontally corresponds to the tasks split by the user story.

4. User story combing

 After the user story disassembly is completed, the team can sort out the user stories with higher priority. The task items needed to complete the user story can be added to the check items in the card, so that after the subsequent user story is planned in the Sprint, it can be easily disassembled into smaller task cards.
Through the list flow, let the team intuitively understand the priority and planning of requirements

5. Iterative Planning

 After the user stories are sorted out, before the iteration starts, we need to plan the user stories that have been sorted out and have high priority in the iteration Kanban. Before the iteration starts, the team needs to estimate and add workload to the user stories to be done. .

Click the "Sprint Planning" button in the Kanban, and drag the sorted user stories to the iteration Kanban.

6. Defect management 

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 contains defects left after release, defects reported by customers, etc.

In the iterative process, we not only need to do relevant user stories, but also solve the defects that arise. Therefore, when planning iterations, we also need to plan defects into Sprints.

7. Iterative execution

After the iteration planning is completed, enter the iteration Kanban, and you can see that the planned user stories are placed in independent swim lanes, and the swim lanes can horizontally correspond to user stories and split tasks.
After the Sprint starts, the team disassembles it into smaller tasks based on the relevant information of these user stories (such as check items and information in the description), and then everyone receives development separately.
Through the flow of the list, the progress and completion of the task are reflected.

8. 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 Sprint iterations. 

View iteration progress

There is an important Sprint progress statistic in each iteration type Kanban - burndown chart.

The burndown chart is a simple and practical tool for tracking team progress in Scrum. It can visually display the remaining workload and the change trend of the remaining working time in the current iteration. Generally, the team will use the burndown chart during the daily stand-up meeting. Understand the current Sprint sprint speed situation.

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 of each iteration Kanban, and automatically generate visual statistical charts, so that the management can see the completion progress of each iteration at a glance.

 

View team speed

Team Velocity is the amount of work that the Scrum Team actually gets done in one Sprint (usually using Story Points as the unit of Team Velocity).

After the end of each Sprint, Leangoo will automatically record the workload completed in the current Sprint, and automatically generate a visual statistical chart of the team rate, so that the team can understand the trend of team efficiency changes and analyze it. 

View task distribution

The Scrum team is a self-organizing team, and the team's daily goals and work arrangements are determined by team discussions.

Through task distribution statistics, the team can quickly and intuitively understand the workload and work progress status of each team member, and help the team collaborate more efficiently.

 

View defect distribution

Defect distribution statistics can show the distribution of tasks under each list in the defect kanban in the project through different dimensions (workload, number of cards) 

View test case distribution

The distribution of test cases can show the distribution of tasks in the test plan Kanban in the project through different dimensions (workload, number of tasks).

 

Product Backlog progress statistics

According to the kanban cycle and burndown chart configuration information, count the product Backlog kanban progress under the project

Statistics of the number of member tasks

The statistics of the number of member tasks is to count the task distribution of project members in all kanbans in the project 

Proportion of member project work

The member's project work proportion is used to count the proportion of each member in the project in the project. (Proportion of items can be adjusted manually)

 

Project member and authority management

Members in the project can be managed in a unified manner. Members can be directly imported into the project from within the enterprise, project roles can be set for the project, project proportions can be set, and the number of projects that members participate in and the projects that members belong to can be checked.

 

 Project file management

Leangoo provides file storage, which is convenient for the team to accumulate experience and share resources.

• Multiple people share project files

• Real-time synchronous upload

•Support documents, pictures, videos and other materials to upload

• Work tasks can be deeply associated, and the task card can be opened in the kanban to associate documents.

Card ID

In order to better assign tasks, find tasks, and quickly locate a task card, Leangoo provides a card ID, which can be opened directly on the project page.

Project Sharing Mind Map

In addition to creating multiple task kanbans in a project, you can also create multiple shared brain maps, which can be used for multi-level demand decomposition, etc.

 

Mind map node

Each node of the Leangoo mind map can be opened, just like the cards on the Kanban board, you can add members, attachments, labels, start and deadlines, etc. to the node, for efficient sharing and collaboration.

Leangoo official website: www.leangoo.com

Guess you like

Origin blog.csdn.net/leangoo/article/details/131214133