You are previewing Kanban In 30 days.
O'Reilly logo
Kanban In 30 days

Book Description

Modern and efficient organization that delivers results

  • Find out how Kanban fits into the broader context of Agile, and get to grips with the core components of its philosophy

  • Identify problems and challenges in your current processes and take immediate steps to drive improvement

  • Structured as a 30 day action plan, this book is an accessible and rapid guide to one of the leading Agile methodologies

  • In Detail

    Kanban is a simple and elegant Agile framework that helps to control and improve development processes. Originating in traditional 20th century manufacturing in Japan, Kanban has a renewed relevance today, being a crucial methodology in the world of software development. This book explores the key features of Kanban, and demonstrates how to put it into practice through exercises that will help you make the most of this unique approach to managing collaboration and production.

    Designed as a 30 day action plan, this book will help you understand and implement Kanban – and start seeing results – in a month. Analyze your current situation and define your goals and wider strategic aims, and begin developing a plan to help you and your team confidently work towards achieving them. Involve your team to drive cultural change, learn how to prioritize and organize tasks and projects to efficiently use your time and resources.

    Create your own value stream map to better understand your processes and identify improvement areas, and adapt and use the features tips and examples to overcome challenges you may face when implementing Kanban. Pick up this book and experience the full results of this vital Agile methodology – fast.

    About the Author

    Tomas Björkholm works as a consultant at Crisp in Sweden. Since 2008, he has been helping companies implement and succeed with Kanban and Scrum. He is also a frequently hired speaker and has held more than 150 classes about Agile and Lean for software development.

    This is Tomas' second book but the first in English.

    Jannika Björkholm is the team manager of a developer team, and has been working with Agile methods since 2009.

    Downloading the example code for this book You can download the example code files for all Packt books you have purchased from your account at http://www.PacktPub.com. If you purchased this book elsewhere, you can visit http://www.PacktPub.com/support and register to have the files e-mailed directly to you.

    Table of Contents

    1. Kanban in 30 Days
      1. Kanban in 30 Days
      2. Credits
      3. About the Authors
      4. About the Reviewer
      5. Preface
        1. What this book covers
        2. Who this book is for
          1. Conventions
          2. Reader feedback
          3. Customer support
          4. Errata
          5. Piracy
          6. Questions
      6. 1. Days 1-2 – Understanding Kanban, Lean, and Agile
        1. The four foundational principles of Kanban
        2. The six core practices of Kanban
          1. Practice 1 – visualizing your work
          2. Practice 2 – limiting work in progress
          3. Practice 3 – managing flow
          4. Practice 4 – making process policies explicit
          5. Practice 5 – implementing feedback loops
          6. Practice 6 – improving collaboratively, evolving experimentally (using models and the scientific method)
        3. Lean
          1. The 14 principles of Lean
        4. Agile
          1. Manifesto for Agile Software Development
          2. Principles behind the Agile Manifesto
        5. Self-organization
        6. How to choose between Scrum and Kanban
        7. Summary
      7. 2. Days 3-5 – Getting to Know Your System
        1. Classes of services – different ways of handling feature requests
        2. Mapping the process
          1. Exercise I – draw the process steps
          2. Exercise II – find the time spent on each process step
        3. What makes your customer happy?
        4. Summary
      8. 3. Days 8-9 – Visualizing Your Process and Creating Your Initial Kanban Board
        1. Information dimensions
        2. Visualization dimensions
          1. Characteristics of visualization dimensions
        3. Matching information and visualization dimensions
          1. Prioritizing information dimensions
        4. Visualizing different statuses
          1. Kanban board with stories and tasks
        5. Examples of Kanban boards
          1. Kanban board example – internal operation
          2. Kanban board example – development team
          3. Different processes for different issue types
          4. A board without rows and columns
          5. A board for aggregated status
        6. Electronic versus physical boards
          1. A good tool increases interaction
          2. A good tool is flexible
        7. Summary
      9. 4. Days 10-11 – Setting the Limits
        1. Adding limits
        2. Showing the result in a graph
        3. Simulating the result
        4. What limit should you start with?
        5. Minimum limits
        6. Theory of constraints
          1. Step 1 – identify the bottleneck
          2. Step 2 – align all other steps according to the bottleneck
          3. Step 3 – increase the capacity through the bottleneck
          4. Step 4 – start over from step 1
        7. Summary
      10. 5. Day 12 – Choosing the Roles and Meetings You Need
        1. Introducing new roles
          1. Kanban Master
            1. Master of the process
            2. Servant leader
            3. Shielding the team
          2. Product owner
          3. Chief product owner and/or project manager
          4. Cross-functional or specialized team
        2. Meetings in Kanban
          1. Planning a meeting
          2. Story start meeting
          3. Daily sync
          4. Enterprise sync
          5. Demo meeting
          6. Review meeting
          7. Retrospective meeting
            1. The plus-minus-delta retrospective
            2. Futurespective
            3. The perfection game
            4. Summarizing retrospectives
            5. Warming up before a retrospective
        3. Summary
      11. 6. Day 15 – First Day Running Kanban
        1. 9:00 to 11:00 – first planning meeting
        2. 11:00 to 13:00 – creating your Kanban board
        3. 13:00 to 14:00 – deciding your meetings
        4. 14:00 to 17:00 – start working
        5. A few days later – the first retrospective
        6. Summary
      12. 7. Days 16-29 – Improving Your Process
        1. Edward Deming and PDCA
        2. Measurements to differentiate between improvements from impairments
          1. Value, failure, and false demand
          2. Measuring time to market
          3. Using the right measurements, the right way
          4. Continuing your value stream mapping
          5. Exercise III – handling special tracks
          6. Looking for loops and alternate ways
          7. Finding the time spent on loops and alternate ways
            1. Calculating process efficiency
            2. Finding improvements in the process
            3. Removing unnecessary queues
            4. Prioritizing with algorithms
            5. Prioritizing with severity
        3. Summary
      13. 8. Day 30 – Release Planning
        1. Basing your plan on facts
        2. Taking control over the amount of work
          1. Quick estimating
          2. Estimating with the planning poker
        3. Knowing your capacity and calculating the delivery date
        4. Follow-up progress with a burn-down chart
        5. Communicating the plan
        6. Burn-up graph
        7. Cumulative flow diagram
        8. Taking control over velocity
        9. Summary