Agile Development Method - KanBan
2025-02-10 15:36:00 0 Report
Log in to view full content
This mind map delves into the Agile Development Method with a focus on Kanban, an approach rooted in Toyota's TPS. Kanban emphasizes visualizing work processes, utilizing tools like physical whiteboards or electronic platforms such as Trello and JIRA Agile. Its core objectives include mapping workflows, triggering discussions, and fostering continuous improvement. Key principles involve visualizing tasks, limiting work in progress, and managing workflow liquidity. It is important to note that Kanban is not a silver bullet; it highlights bottlenecks but doesn't provide solutions. The method assumes teams must consistently deliver valuable products, with completed parts prioritized.
Other works by the author
Outline/Content
Source
Toyota's TPS
Origin
Starting from the current situation
Don't rush to start improving the process.
Core Assumption
The team must deliver a valuable product.
Every release must be valuable.
Completed parts of the product are better than those that are not completed.
Kanban
Physical Kanban
Whiteboard
Large blank wall
Electronic Kanban
Trello
LeanKit Kanban
JIRA Agile
Core Objective
Visualization work
Map the workflow onto the Kanban wall.
Trigger discussion
Continuous improvement
No need for 100% discussion.
The principles of KanBan
Visualization
Visualize everything as much as possible.
Limit work in progress
The less work in progress.
Manage liquidity
The rapid flow of work items
Access Admission and Exit Standards
Kanban is not a silver bullet.
The Kanban can only indicate where the current bottleneck is, it cannot provide a solution.
The dashboard can only provide operational data, not the analytical process.
Will involve a bit more management work
0 Comments
Next Page
Recommended for you
See more
