Case Study: Developing a Custom Agile Practice Adoption Strategy
It's all too easy to get caught up in the energy of trying out new agile practices like pair programming, iterative development, and test driven requirements, and lose sight of the original motivating factors behind instituting those practices in the first place.Elssamadisy's approach to agile practice adoption does not promote one particular named methodology over another, or insist on a minimum canon of practices, but rather helps a team intelligently pick and choose those practices that will best help them achieve their organizational goals. The following three points summarize his approach:
- Determine Business Value
It is all too easy to forget who the real customers are.
- Weigh Activities and Technologies in relation to Business Value
Change for the sake of change tends to dilute the desired results of becoming Agile.
- Incrementally Apply Sets of Practices that Correspond to Value Sought
You don't need to adopt every popular agile practice to see a positive change, but rather a focused, diagnostic approach will help get you where you want to go faster and easier.
Look for Elssamadisy's book on InfoQ in February, designed to help your own team craft a custom "Agile practice adoption strategy".