Lean thinking has had a dramatic effect on industries from manufacturing to banking to hospitals. In software development, lean principles lead us inevitably to agile software develop – and beyond. Lean is not just about iterative development. It is about transforming customer needs into deployed software rapidly, reliably, and repeatedly.
Lean is not about slowing down and being careful, it’s about catching errors the moment they occur so that you can reliably go fast.
QA is not responsible for finding defects versus preventing them from happening.
Agile doesn’t emphasize speed. Scrum only helps dysfunctional organization.
In queueing theory, Little's result, theorem, or law says: The average number of customers in a stable system (over some time interval) is equal to their average arrival rate, multiplied by their average time in the system. Assume customers arrive at the rate of 10 per hour and stay an average of 0.5 hour. This means we should find the average number of customers in the store at any time to be 5.
Performance is the cycle time how fast the customer needs can be repeatedly convert into the deployed software. Productivity is not how many lines you can write or how many features you can produce over a period of time.
Build only what you need.
Stop when something goes wrong.
Eliminate the waste. (Decide as late as possible. Reduce to-do list. No queues. Small batch. Build quality.)
Amplify the learning.
Optimize as a whole.
Build defects-proof system process, continuous integration and synchronization.
Tony
http://www.poppendieck.com/ (Mary/Tom Poppendieck)
No comments:
Post a Comment