5th Law = Variability Costs

To follow up on the fourth law, I add as reinforcement the fifth law of agile physics: If you cannot pay for variability reduction, you will pay in one or more of the following ways: Long iteration times and high…

To follow up on the fourth law, I add as reinforcement the fifth law of agile physics: If you cannot pay for variability reduction, you will pay in one or more of the following ways: Long iteration times and high…
I was reading through some old notes this evening and ran across this idea: Consultant: – Delivers Reports – Retains skill Resultant: – Delivers Results – Transfers Skills While I don’t think I want to be…
One page summaries of the values of agile software development.

Variability is the root of all evil in development and must be eliminated.
If you want to ensure success, forget input measures and focus on measuring outputs. Track deliverables completed. Measure quality. Track burn down. Ensure risks are being mitigated. Measure tangible impacts to ensure value is being delivered. Measure customer and stakeholder confidence and user satisfaction.

Stories are the raw materials of development. They should stay in a raw form until needed. Or, as stated by the third “law of development physics”: The value of requirements increases as its production release becomes imminent. Or, you know what you need when you see it, until then, make up a good story.

In my post, What’s so Wrong with Pushing, I showed by analogy how Time Blocked Iterations, Story Points and Burn Down Rate enabled a superior pull mechanism over traditional management for development teams. In this post, I’ll quantify how to…
If you have not already read the philosophies of 37Signals’ development, it is time well spent. You can read Getting Real on-line. It overviews the software development ideas that created such programs such as Ruby on Rails and Basecamp. Using simple language and numerous case studies,…
In agile development, much emphasis is rightfully placed on burn down rate, the number of story points completed within an iteration of development. I’ve never been fully satisfied with explanations for why this measure and control of it is so…

Is the cost of software defects driven more by time than the stage of its discovery?