Skip to content

Latest commit

 

History

History
19 lines (10 loc) · 2.81 KB

Kanban.md

File metadata and controls

19 lines (10 loc) · 2.81 KB
Raw

Kanban

  • 7 Lean Metrics to Improve Flow - by LeanKit. "With flow, the goal is more about consistently creating economic value than it is about having the fastest cycle time or highest throughput. Maintaining a steady flow of work through your Kanban system can help you deliver value more quickly and reliably to your customers, team, and organization."

  • One Day in Kanban Land - by Henrik Kniberg. A short and simple visual explanation of Kanban.

  • Kanban, Can’tban, and Risky Visualizations - by John Cutler. "Kanban doesn’t care about how you write code, structure and incentivize teams, develop roadmaps and backlogs, manage projects, manage people, scheduled meetings, or release software. Through visualizing our work, Kanban helps guide our continuous improvement efforts."

  • Scrum and Kanban: Make Your Teams Better by Busting Common Myths (Webinar) - by Steve Porter and Daniel Vacanti. Tips on how to combine Scrum and Kanban

  • Scrum and Kanban Revisited - by Mike Burrows. "Do I believe that a combination of Scrum and Kanban can help to deliver this? Yes I do, and I can point to multiple projects where I’ve witnessed it happen."

  • Tutorial - Tracking a Kanban Team - by Atlassian. A tutorial on how to set up Kanban environment in JIRA.

Books

  • Lean & Kanban - by InfoQ.com. "The Lean & Kanban eMag brings together the latest thinking on the application of Lean and Kanban in the software world. It examines topics ranging from identifying and removing waste in the software process, designing for devops and continuous delivery, the overlap of lean, Kanban and agile, practical implementation of Kanban in software development and how these approaches contribute to innovation."

  • Priming Kanban - by Jesper Boeg. "[T]his mini-book offers an easy to follow 10 step guide to taking the initial plunge and start using Lean principles to optimizing value and flow in your system. Each step consists of a section explaining “why” followed by examples of specific tools, practices and rules that have helped other teams better understand and optimize their system. The author's hope is that this will make it easier for teams to get started and quickly understand the importance of value and flow by experiencing it first hand."