...no testing deadlines…the freedom to test as long as I want.

Back in the dark ages, with Scrum, all the sprint Features had to be tested by the end of the iteration.  Since programming generally continued until that last minute (we couldn’t help ourselves), testers were sometimes forced to cut corners.  Even in cases where the whole team (e.g., programmers, BAs) jumped in to help test, there was still a tendency to skimp on testing that would otherwise be performed.  The team wants to be successful.  Success is more easily measured by delivered Features than Feature quality.  That’s the downside of deadlines.

With Kanban, there are no deadlines…you heard me!  Testers take as long as they need.  If the estimates are way off, it doesn’t leave gaps or crunches in iterations.  There are no iterations!  Warning: I fear unskilled testers may actually have a difficult time with this freedom.  Most testers are used to being told how much time they have (i.e., “The Time’s Up! Heuristic”).  So with Kanban, other Stopping Heuristics may become more important.


  1. Ilya Kurnosov said...

    "...no testing deadlines..." Sure, there are deadlines. For instance, marketing have already made an announcement that product is to be shipped on D-day; or new legislation becomes active, and previous version of the product can't handle it; or market situation can change; or a dozen of other "or-s".

    Probably, you meant "...no artifical deadlines...", and I'm just nitpicking.

  2. Eric Jacobson said...

    Yes. I like "no artificial" deadlines. You said it better than I did.

    Yes yes, of course, there will be some deadlines. However, most are imposed on a per feature basis. IMO, this is easier than trying to determine a deadline for a big pack of features.

    Thanks for keeping me honest, Ilya.

  3. Astrosms said...

    Thank you for the article. I just about passed your we site up in Bing but now I'm glad I clicked the link and got to go through it.

Copyright 2006| Blogger Templates by GeckoandFly modified and converted to Blogger Beta by Blogcrowds.
No part of the content or the blog may be reproduced without prior written permission.