Comments on: Kanban vs. Iterative Development

By: uberVU - social comments

uberVU - social comments — Sun, 25 Oct 2009 00:44:49 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by mmarschall: blogged about “Kanban vs. Iterative Development” at Agile Web Operations http://bit.ly/1Bw7Dq…

By: Matthias Marschall

Matthias Marschall — Sun, 18 Oct 2009 19:26:16 +0000

@Henning Yes, seems like a time boxed approach works better when building version 1.0. For maintaining and evolving the product after it is live, a Kanban base process seems to work better.

@Jason Thanks for the comment. You’re right with your remark. Thanks for the link – was a very interesting read!

By: Tweets that mention Kanban vs. Iterative Development — Agile Web Operations -- Topsy.com

Sun, 18 Oct 2009 19:23:38 +0000

[...] This post was mentioned on Twitter by Melanie Cey, Matthias Marschall. Matthias Marschall said: blogged about "Kanban vs. Iterative Development" at Agile Web Operations http://bit.ly/1Bw7Dq [...]

By: Jason Yip

Jason Yip — Sun, 18 Oct 2009 00:38:04 +0000

What you’re describing as “iterative” is more accurately described as “timeboxed”. Iterative development refers to successive refinement which is orthogonal to whether one uses timeboxes.

See http://agileproductdesign.com/blog/dont_know_what_i_want.html

By: Henning Koch

Henning Koch — Sat, 17 Oct 2009 09:13:26 +0000

Once a project goes into production, our clients often need to reprioritize stories on very short notice in order to react to the events of the day. Timeboxing our work into iterations would not work well here. We rather have short cycle times for our stories so we’re free to react to changes in priorities while still delivering a constant flow of value to the project.

This only works well when costs to take an integration point are low. Good test coverage and readily available acceptance testers can make that possible.