Jason Fried of 37signals posted recently about how they choose the essential vs. non-essential requirements for v1.0 of their products. This got me thinking that:
a) what a great idea, it makes perfect sense
b) how many client-driven projects would allow such a thing to happen?
![](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_uUGH8D61G62aNTdwIVm4YqnwZszS4vTrBNVFMtWOor9ri966OgLNBHxh9UaMCUfCL1Iwlor_51-ikK9zmndUN11bYEjbWf3J8vrIOyU3ip6ZTuIHrx9ijZ_gQnt4rDdNKxhRjWja4=s0-d)
With agile development and the process of release & iteration planning in particular, essential requirements would be moved in front of non-essential ones, so maybe when dealing with external client-driven projects the first iteration (or so) would produce the 37signals' v1.0 release?
Technorati Tags: Jason Fried, 37signals, Agile, Release Planning, Iteration Planning, Andrew Beacock
a) what a great idea, it makes perfect sense
b) how many client-driven projects would allow such a thing to happen?
Technorati Tags: Jason Fried, 37signals, Agile, Release Planning, Iteration Planning, Andrew Beacock
Comments