InfoQ Homepage Continuous Improvement Content on InfoQ
-
Performance Goals For Agile Teams
Inspired by Jon Katzenbach and Douglas Smith's book The Wisdom of Teams, Mishkin Berteig looks at the importance of performance goals for driving a team towards self-organization and accountability.
-
New Book on Lean Software Offers Practical Advice
In 2003 Mary and Tom Poppendieck adapted the revolutionary principles of Lean manufacturing for software development. Their new book offers a blend of history, theory, and practice, drawing on their experience optimizing the software "value stream". They present the right questions to ask, the key issues to focus on, and techniques proven to work for those implementing a lean software process.
-
Book Excerpt: Agile Retrospectives
InfoQ brings you an exclusive chapter excerpt from the recent book "Agile Retrospectives: Making Good Teams Great", by Esther Derby and Diana Larsen. These expert facilitators show how teams can run focused, helpful retrospectives themselves, without an outside facilitator. We asked the authors a few questions about the making of their book.
-
Tips for Effective Kaizen Process Improvement
Agile software development and Lean Thinking go hand-in-hand for many practitioners. Six-Sigma blackbelt Mike Wroblewski has blogged some lessons learned from a recent kaizen session. People are a key variable in both manufacturing and software environments, so his lessons learned in manufacturing are also interesting for Lean Software practitioners using kaizen events for process improvement.
-
Mary and Tom Poppendieck Discuss Their Next Book
Bob Payne interviewed Mary and Tom Poppendieck at Agile2006 about their next Lean book, which focuses even more on software than the last. Mary summarizes it as "So you think Agile is a good idea: now what?" saying it will help people get started with Lean, going beyond the recipes of the first book to provide practical information and case studies to help teams do their own process experiments.
-
Leveraging the Wisdom of Project Newcomers
Experienced newcomers can't be onboarded like programmers just out of school. The experienced professional will have specific but difficult-to-anticipate gaps that will impede their performance. In addition, this provides a great opportunity to get a fresh but experienced feedback on your processes. Gannthead.com offers some pointers wrapped in three fictional Dr. Phil episodes... (really?)
-
InfoQ Article: Exclusive Excerpt from Practices of an Agile Developer
Andy Hunt, one of the originators of the Agile Manifesto, and Venkat Subramaniam have written a compilation of the habits, ideas, and approaches of successful Agile software developers in "Practices of an Agile Developer". InfoQ brings you a free excerpt on Agile Debugging.
-
Agile Work Cheatsheets Posted
It's been said before: Agile may be simple, but it's not so easy. Mishkin Berteig contributes some one-page quick-references to jog our memories and keep us focused on delivering value.
-
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.