The discussion of applying lean principles to software development has largely focused on identifying and eliminating waste (in Japanese: muda). Lean Thinking equally aims to remove overburden (muri) and unnecessary variation (mura). Roman Pichler discusses the relationship of the "three M's" and proposes to eliminate overburden as the first step toward a leaner process.
In this InfoQ article Kenji Hiranabe applies lessons learned while working with Japanese manufacturers. While many Agile teams are optimizing only a portion of the value stream, Hiranabe proposes a simple way to adapt lessons from Lean Manufacturing's "Kanban" visual tracking system to make process visible to more of the organization, for better communication and process improvement.
Coach Michael Spayd tells us that both contractors and permanent employees can play a "consultant" role, and should think about developing consulting contracts or "designed partnerships" with their clients - not about the exchange of money, but to help create stellar results for the client while working in a manner that adheres to their own values and preferences.
In this article J. B. Rainsberger looks at at a common holiday season communication problem, and shares one of his secret weapons for team building: the Satir Communication Model. 4
Based on traditional Earned Value Management (EVM) metrics, AgileEVM is adapted for an Agile PM context. It allows Agile and traditional projects to be tracked within a single program. 8
Can refactoring and TDD create “working software” that survives real life? Michael Nygard suggests that "leaky abstractions" ambush us at 5AM when we've paid too little attention to architecture. 25
Agile software development, shunning up-front design, has grown up in parallel to the emergence of "user-centered design," with its detailed user research and modeling. Can these be used together? 7
A recent "Agile SOA" project used frequent feedback and a platform that grows as the SOA portfolio grows, to provide early and continuing value. InfoQ interviewed the author of the experience report. 1
Sometimes, a new requirement is actually a changed business rule. James Taylor looks at how a business rules engine can help Agile teams work more effectively in certain situations.
Using logging seams you can easily create unobtrusive unit tests around legacy classes, without needing to edit class logic as well as avoiding behavior changes. 3
David Spann introduces Jean Tabaka's book, in which she shares stories and facilitation techniques to make teams and entire organizations effective, and provides templates to get them started.
Take a BAT to the legacy code you inherit: Build, Automate, Test. Jared Richardson shows how to create a safety net, to ensure that your code continues to work the way you want it to. 19