Kanban is becoming a popular way to visualize and limit work-in-progress in software development and information technology work. Teams around the world are adding kanban around their existing processes to catalyze cultural change and deliver better business agility. This book answers the questions: What is Kanban? Why would I want to use Kanban? How do I go about implementing Kanban? How do I recognize improvement opportunities and what should I do about them?
When Kanban is used in the field of software engineering, it is used in a much broader sense. Kanban is a change management approach that employs a WIP limited pull system. For me it is an approach to change your process into one that focuses on end to end value and reliably delivering stuff, with high quality. The limited set of rules and principles help people focus on customer value and avoid building up half finished work, which is still a common issue in the software industry.
When Kanban is used in the field of software engineering, it is used in a much broader sense. Kanban is a change management approach that employs a WIP limited pull system. For me it is an approach to change your process into one that focuses on end to end value and reliably delivering stuff, with high quality. The limited set of rules and principles help people focus on customer value and avoid building up half finished work, which is still a common issue in the software industry.
Title Kanban for Skeptics: Clear Answers to Kanban in Software Development
Author(s) Nick Oostvogels
Publisher: Leanpub.com (2013)
Language: English
eBook: https://leanpub.com/kanbanforskeptics
Author(s) Nick Oostvogels
Publisher: Leanpub.com (2013)
Language: English
eBook: https://leanpub.com/kanbanforskeptics
No comments:
Post a Comment