Muftasoft TM

User Tools

Site Tools

Trace:
training:project_management:kanban

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
training:project_management:kanban [2023/10/11 18:26] – created wikiadmintraining:project_management:kanban [Unknown date] (current) – external edit (Unknown date) 127.0.0.1
Line 4: Line 4:
  
 1. **Introduction to Kanban** 1. **Introduction to Kanban**
 +
 2. **The History of Kanban** 2. **The History of Kanban**
 +
 3. **Kanban Principles** 3. **Kanban Principles**
 +
 4. **Key Concepts in Kanban** 4. **Key Concepts in Kanban**
 +
 5. **Kanban Practices** 5. **Kanban Practices**
 +
 6. **Implementing Kanban** 6. **Implementing Kanban**
 +
 7. **Kanban in Different Contexts** 7. **Kanban in Different Contexts**
 +
 8. **Kanban vs. Scrum** 8. **Kanban vs. Scrum**
 +
 9. **Benefits of Kanban** 9. **Benefits of Kanban**
 +
 10. **Challenges and Considerations** 10. **Challenges and Considerations**
 +
 11. **Kanban Tools and Software** 11. **Kanban Tools and Software**
 +
 12. **Conclusion** 12. **Conclusion**
 +
  
 **1. Introduction to Kanban** **1. Introduction to Kanban**
Line 209: Line 221:
  
 - **Scrum:** Scrum defines specific roles, including the Scrum Master, Product Owner, and Development Team. - **Scrum:** Scrum defines specific roles, including the Scrum Master, Product Owner, and Development Team.
 +
 - **Kanban:** Kanban doesn't prescribe specific roles; it allows for more flexibility in team structure. - **Kanban:** Kanban doesn't prescribe specific roles; it allows for more flexibility in team structure.
  
Line 214: Line 227:
  
 - **Scrum:** Scrum operates in fixed-length iterations known as sprints, typically lasting 2-4 weeks. - **Scrum:** Scrum operates in fixed-length iterations known as sprints, typically lasting 2-4 weeks.
 +
 - **Kanban:** Kanban does not use fixed timeframes like sprints; it allows for continuous flow. - **Kanban:** Kanban does not use fixed timeframes like sprints; it allows for continuous flow.
  
Line 219: Line 233:
  
 - **Scrum:** Scrum teams commit to delivering a specific set of work during a sprint planning meeting. - **Scrum:** Scrum teams commit to delivering a specific set of work during a sprint planning meeting.
 +
 - **Kanban:** Kanban teams do not make specific commitments for future work but focus on managing current tasks and flow. - **Kanban:** Kanban teams do not make specific commitments for future work but focus on managing current tasks and flow.
  
Line 224: Line 239:
  
 - **Scrum:** Scrum does not have explicit WIP limits; it relies on capacity planning within sprints. - **Scrum:** Scrum does not have explicit WIP limits; it relies on capacity planning within sprints.
 +
 - **Kanban:** Kanban uses explicit WIP limits for each stage in the workflow. - **Kanban:** Kanban uses explicit WIP limits for each stage in the workflow.
  
Line 229: Line 245:
  
 - **Scrum:** Scrum discourages changes to the sprint scope once it begins. Changes are deferred to the next sprint. - **Scrum:** Scrum discourages changes to the sprint scope once it begins. Changes are deferred to the next sprint.
 +
 - **Kanban:** Kanban accommodates changes at any time since there are no fixed-length sprints. - **Kanban:** Kanban accommodates changes at any time since there are no fixed-length sprints.
  
Line 234: Line 251:
  
 - **Scrum:** Scrum employs time-boxed iterations to ensure a predictable release schedule. - **Scrum:** Scrum employs time-boxed iterations to ensure a predictable release schedule.
 +
 - **Kanban:** Kanban focuses on continuous flow and optimizing the delivery of work as it becomes ready. - **Kanban:** Kanban focuses on continuous flow and optimizing the delivery of work as it becomes ready.
  
Line 239: Line 257:
  
 - **Scrum:** Scrum often uses burn-down charts and velocity to measure progress. - **Scrum:** Scrum often uses burn-down charts and velocity to measure progress.
 +
 - **Kanban:** Kanban uses metrics like lead time and cycle time to analyze and improve process performance. - **Kanban:** Kanban uses metrics like lead time and cycle time to analyze and improve process performance.
  
Line 320: Line 339:
  
 - Trello - Trello
 +
 - Kanbanize - Kanbanize
 +
 - Jira (with Kanban boards) - Jira (with Kanban boards)
 +
 - LeanKit - LeanKit
 +
 - Asana - Asana
 +
 - Taiga - Taiga
 +
 - ZenHub (for GitHub) - ZenHub (for GitHub)
 +
 - ClickUp - ClickUp
 +
 - Targetprocess - Targetprocess
 +
 - Kanboard - Kanboard
  
training/project_management/kanban.1697048818.txt.gz · Last modified: 2023/10/11 18:26 (external edit)