There’s no incentive to look the other way when we notice bugs at the last minute.
We are planning to release a HUGE feature to production tomorrow. Ooops! Wouldn’t you know it…we found more bugs.
Back in the dark ages, with Scrum, it’s possible we may have talked ourselves into justifying the release without the bug fixes; “these aren’t terrible…maybe users won’t notice…we can always patch production later”.
But with Kanban, it went something like this:
“…hey, let’s not release tomorrow. Let’s give ourselves an extra day.”
- Nobody has to work late.
- No iteration planning needs to be rejiggered.
- There’s no set, established maintenance window restricting our flexibility.
- Quality did not fall victim to an iteration schedule.
- We don’t need to publish any known bugs (i.e., there won’t be any).
3 comments:
Subscribe to:
Post Comments (Atom)
RSS
Doesn't sound inherently Kanbanesque to me, dude. Sounds like you work with real, free-thinking human beings who know how to appreciate risk and tradeoffs in software projects.
Turns out I do! But for some reason we were all stymied by this thing we all heard about called Scrum. This thing that we awkwardly tried to plug ourselves into for years. This thing with a heavier process than I remember waterfall ever being. This thing that chopped off quality every 4 weeks in the name of meeting the planned iteration goals.
i hate to work late nights but no other options left as to finish my work fast but with quality and this involves lot of hard work and can understand the same that your efforts