In the latest of a series of posts examining Agile adoption in organizations and businesses, blogger Suzanne Miller takes a look at specific Agile practices and how they can be evaluated. She mostly talks about governmental organizations, but the evaluations are valuable for all organizations.
From an Agile perspective, the business/operations part of the organization is the determiner of business value, and therefore a specific role that pays attention to prioritization and backlog refinement is a key construct for Agile teams. The role is not exactly a program manager, not exactly a systems engineer, although it has elements of both. Absence of this role creates problems related to prioritization and focus on the project.
The practices she delves into include Test-Driven Development, pair programming, continuous integration and self-managing/self-organizing. How do you know which practices work for your organization and which don't?
By paying attention to them when considering your readiness and fitness for Agile adoption, you can realize more successful pilots and implementations. Each category in the RFA offers insight into the risks that an organization will face when adopting Agile methods. Identifying these risks is an important first step in planning and executing mitigation strategies to address them.
Check out the post here.