InfoQ Homepage Continuous Improvement Content on InfoQ
-
Google's Lean Software Process
On the Manageability.org blog, Carlos E. Perez asked "how closely do Google's development practices match Lean software development?" and compared their process against the seven Lean Software practices: Eliminate Waste, Amplify Learning, Empower the Team, Deliver as Fast as Possible, See the Whole, Build Integrity In, Decide as Late as Possible.
-
TOC More Powerful than Six-Sigma, Lean
A manufacturing study has shown that TOC is twenty times as effective as Six Sigma, and nearly ten times more effective than lean at causing cost savings. This is the only scientific double-blind study of its kind performed "in the wild", i.e. in actual business plants. These ideas are frequently discussed in Agile circles and integrated into Agile methodologies.
-
Personal Retrospective: How Did I Do?
Nynke Andering gives us an inside view of a process of self-retrospective, which she uses after a consulting engagement. She shares not only her questions, but her answers, in four categories: Collaboration, Learning, Consulting, Responsibility.
-
Ruby Coverage Tool Making Rapid Progress
Earlier this week, Mauricio Fernandez released version 0.4 of Rcov, his tool for simple code coverage analysis in Ruby. Rcov is fast, feature-packed and progressing rapidly.
-
Meeting the Challenge of Collective Code Ownership
The challenge: find the balance between pure practice and local compromise. Martin Fowler has brought us a story of a team in trouble, which took a step back to improve coding discipline and brush up on the basic practices that support collective ownership. In addition to the short-term gains of increased velocity and improved morale, the overall quality of the team's output improved as well.
-
Thirty Days to Better Software
J.T. King describes the idea that you can slowly improve the way that you work over time by trying something for 30 days, giving it a fair chance, then assessing how well it worked for you.
-
Is the Feedback Loop Worth the Time?
John Brothers, on Indefinite Articles, blogged an interesting conversation last week between Mary Poppendieck and Robert Bogue. Drawn from the Agile Project Management newsgroup, it pointed out two different stances on the relative cost and value of "frequent feedback", a key component of Agile methodologies.
-
Improving Processes in Small Settings
The Software Engineering Institute is forming the IPSS Working Group, a three-year project to collaboratively explore the unique challenges of improving processes in small settings.