Addressing another Agile Myth (we don't need no analysts!), Shane Hastie, Chief Knowledge Engineer at Software Education, outlines how the Business Analyst can help Agile teamwork - when properly aligned with the business, rather than the development team.
Dave Nicolette, Agile Coach with Valtech, addresses the question are short iterations better than long. Dave demonstrates that short iterations: allow for more rapid response to change, the opportunity to discover and fix problems more often. He also deals with the concerns that short iterations might lead to burnout and other issues.
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.
Many teams optimize only a portion of the software value stream, but Kenji Hiranabe shows how we can adapt Lean Manufacturing's Kanban tracking system for communication with more of the organization. 7
Michael Spayd tells us that both contractors & permanent employees can play a "consultant" role, and can use contracts to help create stellar results for clients while respecting their own values. 2
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