Agile Fluency in Depth

I found this interesting due to its depth understanding of the stages

Agile Fluency

We’ve observed that Agile teams develop through four distinct stages of fluency. Fluency is how a team develops software when it’s under pressure. Anyone can follow a set of practices when given time to focus in a classroom; true fluency is a skillful, routine practice that persists when your mind is distracted with other things.

For Agile, we’re considering team fluency rather than individual or organizational fluency. Agile development is fundamentally a team effort, and your organization’s success with Agile will depend on the fluency of your teams.

Team fluency depends on more than just the capability of the individuals on the team. It also depends on management structures, relationships, organizational culture, and more. Don’t make the mistake of blaming individuals for low team fluency, or assuming that one highly-skilled individual will guarantee high team fluency

Teams progress through four distinct stages of Agile fluency, which we describe with a “star” system. Each star includes fluency at all previous levels. While it’s theoretically possible for a team to be fluent only at a particular level, we’ve seen that teams progress through the stages in a predictable order.

Each star brings specific benefits, and each involves new adoption challenges. As you read through the fluency levels, remember that every level of fluency brings its own benefits. Since achieving higher fluency takes more investment, consider whether a lower level’s benefits are enough for your organization

Extracted From - http://martinfowler.com/articles/agileFluency.html


Cheers!!!
Ak