Why Use Time Boxes In Agile Software Development?
I recently made a response to a post about time-boxing in the Agile Coaching group at LinkedIn. As it turns out, the author of the post was well aware of the Parkinson's Law angle, and so are probably most agile team leaders. However, even if you do know about Parkinson's Law, you might be interested in the other reason. It is (in my opinion) more important, but less well understood. Here is my response to the LinkedIn post: Two reasons. One is Parkinson's Law: Work expands so as to fill the time available for its completion. You can read about it here: http://en.wikipedia.org/wiki/Parkinson%27s_Law Parkinson's Law isn't scientifically proven. It is just an observation about the results of human behavior. The other reason is also a law, but a scientifically proven one. Little's Law says that for a stable system: t = I / T t = Lead time I = Number of items T = Throughput (Items processed per time unit) Note that if you want to reduce t, as in reduce project lea