FREE eBOOK – Kanban and Scrum: Making the most of Both

This FREE eBOOK DOWNLOAD by Henrik Kniberg and Mattias Skarin is excellent !   It clears up the fog, so you can figure out how Kanban and Scrum might be useful in your own environment. Thanks to InfoQ for posting it.

There isn’t a single “best” way to do things; you have to think for yourself and figure it out – based on your situation !

LEARN ABOUT…

  • the difference between Scrum and Kanban.
  • their strengths and limitations,
  • when to use each
  • how and when to improve upon Scrum, or any other tool you may happen to be using.
  • how to apply them in real life situations
  • and more….

Mary Poppendieck writes:

Henrik Kniberg is one of those rare people who can extract the essence of a complicated situation, sort out the core ideas from the incidental distractions, and provide a crystal clear explanation that is incredibly easy to understand.  He makes it clear that these are just tools, and what you really want to do is have a full toolkit, understand the strengths and limitations of each tool and how to use them all. The important thing is not the tool you start with, but the way you constantly improve your use of that tool and expand your toolset over time.

David Anderson, the founder of Kanban, writes,

Kanban is proving useful to teams doing Agile software development but equally it is gaining traction with teams taking a more traditional approach. Kanban is being introduced as part of a Lean initiative to morph the culture of organizations and encourage continuous improvement.

Name
Email

..

Share

Filed under Agile-Lean, Books, Hot Topics, Kanban, Scrum, Transitioning to Agility

Comments

One Response to “FREE eBOOK – Kanban and Scrum: Making the most of Both”
  1. martin burns says:
    October 17, 2010 at 5:35 PM

    Not entirely convinced that David A can be credited as the founder of Kanban – I’m sure the nation of Japan (and manufacturing companies in particular) have prior art :-)

    The one thing that Scrum practitioners (and those taking a more traditional approach) will need to take onboard is that the batch mentality of iterations (and indeed projects) needs to break down to gain the Flow that will achieve the gains of lean methods.

    Agile adherents in particular will also need to accept greater degrees of process enforcement than they’re used to, as a necessary precondition.

    However, I believe that maturing Agile teams in an environment of change within known limits (easier with a clean reference architecture than the nightmare that many of us inherit) can and generally should transform towards full Lean methods.

    What’s been described as Lean Software so far is only a small step along the way – it’s Agile with a small evolution to adopt the value system of Lean. Over time, we will all learn to be profoundly more radical. And Kanban is an important learning step along the way.

    If you want to see the future, stop reading Ken Schwaber (I mean: you’ve read and absorbed it by now, right?), and start reading Jeffery Liker instead.