Saturday, November 14, 2009

“ScrumBan - Evolution or Oxymoron? - InfoQ.com” plus 4 more

“ScrumBan - Evolution or Oxymoron? - InfoQ.com” plus 4 more


ScrumBan - Evolution or Oxymoron? - InfoQ.com

Posted: 14 Nov 2009 02:44 PM PST

Posted by Deborah Hartmann Preuss on Nov 14, 2009

Community
Agile
Topics
Agile Techniques ,
Methodologies
Tags
Criticism ,
Kanban ,
Lean ,
Scrum

Although not new, awareness of Kanban is now growing among users of Agile software methods. Talks, workshops and entire conferences are springing up, and Agile trainers are combining Kanban into their courses.. Practicing Agilists are investigating what this method, adapted from Lean, offers their teams: attractive benefits are cited, from making bottlenecks visible to making more progress faster and happier teams experiencing more "flow". Into this ecosystem, Simon Bennett's The Philosophy of Kanban is Kryptonite to Scrum offers a warning to those who are thinking of incorporating Kanban into their Scrum process. Proponents of Kanban agree with Bennet that Kanban's less agressive approach to impediments is at odds with Scrum's call to remove impediments immediately.

Bennett's blog post, which he declares as neither an anti-Kanban rant nor a "keep Scrum pure" diatribe, states that

If you're going to use Scrum, but ignore or hide the impediments, (or even not raise them in the first place) then you are asking for a world of pain, and a lack of progress. This is what Ken Schwaber and Martin Fowler are talking about when they speak of flaccid Scrum. (at least from a technical debt perspective)

Both Scrum and Kanban prize transparency; but they handle it in different ways – and Scrum builds-in an explicit call to action, which needs to be answered for Scrum to succeed.

Kanban allows for you and your team to simply "accept" impediments, and measure their effect.

His position: their philosophies are at odds: your "Scrum project will weaken as long as the Kanban philosophy is nearby." However, applying a pure philosophy is not the goal: it's quality software, frequently delivered. To this end, he encourages practitioners to examine what kind of projects they have and how successful they are with Scrum, and he provides guidelines on how to choose which to use.

Corey Ladas' 2008 paper "Scrum-ban" described an evolutionary process toward Kanban which, if taken far enough, replaces most of Scrum. Ladas' approach would modify or even replace many of the traditional Scrum practices, such as the daily standup and burn-down charts. Interestingly, Anderson, whose Kanban experience report from Corbis made a splash at Agile2007, and who appears now to be largely focused on Kanban adoption, cites his original intent as not "converting people from Scrum" but rather helping those struggling to adopt Agile. Bennett's post suggests that teams carefully consider before incorporating Kanban: are they getting enough value from Scrum alone? He adds:: "if you really are dancing on the bleeding edge then I imagine you'll come to depend on Scrum."

While Bennet isn't listed among the thought-leaders at Limited WIP Society (intended as "the home of kanban for software development community"), many of those listed have offered supportive comments on the blog's comment thread, including Karl Scotland and David J. Anderson. Anderson agreed:

Yes, Kanban is evolution while Scrum is revolution. I am very comfortable with that positioning.

Of course, any tool can be misused: Chris Sims' article Are Kanban Workflows Agile? reminds readers that if the kanban board is being used to make sure that each of the required activities has occurred, it is being used to enforce the team's definition of done, a job better suited to a simple checklist. And Mitch Lacey was recently overheard reminding us that at the "end of day there are no magic answers. Saying one solves people's problems over another is just that: fairy dust."

There's more about Kanban on InfoQ: Articles, Presentations.

  1. Back to top

    Scrum without the iterations

    Nov 14, 2009 9:09 AM by Machiel Groeneveld

    One that is annoying about Scrum is its insistence on conformance: "If you can't do Scrum, you need to change!". Although correct in Scrum-theory, in the real world even Scrum needs to be fit to the current context. The Kanban method inspired me to replace some parts of Scrum with things that worked better for us.

    A few things that Scrum enforces, but aren't always the optimal solution (in my experience):
    - The use of iterations
    - The use of story estimation
    - Synchronized release, demo and retrospective.

    Bottom line is: Scrum is a valuable set of practices, but be prepared tune Scrum for your situation. Most Kanban initiatives show that you can change Scrum or even replacing it altogether to get better performance and transparency.

    I will be presenting on XPDays with my improved Scrum story.

  2. Back to top

    Re: Scrum without the iterations

    Nov 14, 2009 9:58 AM by Tobias Mayer

    Actually, Scrum says nothing about story estimation, in fact nothing about "stories". Also, nothing in Scrum suggests you have to release at the same time you do a retrospective. So I guess you are not really dropping Scrum practices, except iterations... and I'd be wary of that. If you can find another way to hit a rhythm, and leverage the empirical process for feedback it's probably fine. Often when people (perhaps not you) drop iterations they are more likely to hide things than expose them. Thus, less learning.

  3. Back to top

    Re: Scrum without the iterations

    Nov 14, 2009 10:38 AM by Machiel Groeneveld

    You are right about the stories, I should have called them backlog items.

This content has passed through fivefilters.org.

Sky Work AG - CharterX

Posted: 14 Nov 2009 12:28 PM PST

Skywork was born on the philosophy that integrity, exceptional service and total commitment will produce results which soar above the competition. Skywork president Alex Gribi has devoted most of his life to quality in aviation and this is reflected by a highly competent and dedicated team. Their commitment has turned this philosophy into reality. Skywork is the choice for discerning travellers, and will fly to any destination faster, safer, and more comfortably than any other airline company. Skywork clients can demand the exceptional.

Established: 1983 • Fleet: 6 • Pilots: 20 full time
Certificate: 1039 (CH)
Email: info@skywork.ch
URL: http://www.skywork.ch


Bases


Fleet


This content has passed through fivefilters.org.

Muhlenberg College - Allentown Morning Call

Posted: 14 Nov 2009 12:49 PM PST

Recipient E-mail Addresses

(up to 3, separated by commas) Send me a copy.

From: