We love the feedback, so please feel free to send us any comments or questions you might have.

With my three years of experience i totally agree with ya.

Good work and keep bloggin…..Thanks a lot.

Hassan

Thank you very much for the question.

“One feature at a time” is an ideal, in the same way that “single piece flow” is an ideal. The goal is to reduce batch sizes of work in process. Of course the smallest batch size is 1, but there can be tradeoffs against planning overhead and workflow handoffs. When designing your process, you should try to find the smallest batch size that justifies the planning cost, with an eye towards reducing that planning cost over time.

Also, the value of the critical mass of features depends somewhat on the source of that critical mass property. If it’s a critical mass because that’s the best way to meet customer expectations, then that is a function of design quality and you should strive to please the customer. Obviously, it isn’t useful to ship a car without the brakes installed.

On the other hand, if it’s a critical mass because your requirements lack orthogonality, then perhaps there is further investment to be made in analysis and design capability.

Either way, there can be some queueing of completed work at the end of the process in order to deploy in the right-sized chunk. That shouldn’t let you off the hook for controlling work-in-process to the best of your ability.

Look for a more detailed post on this in the near future.

http://leansoftwareengineering.com/?feed=rss
http://leansoftwareengineering.com/?feed=rss2
http://leansoftwareengineering.com/?feed=rdf
http://leansoftwareengineering.com/?feed=atom

…will get some links up on the sidebar ASAP

I agree about the customer-centric nature of software development.

But… “one feature at a time”? Surely – for many contexts, not all – there’s (a) a critical mass of features to get started and (b) an investment in familiarity with a so-far-perfect version of the product/solution?

What am I missing, here?