Today we are sailing in the journey of transforming ourselves from our Traditional frameworks to Agile (Scrum, XP, Kanban, Hybrids, and Scaling Frameworks).
Since any Agile Framework has a collaborative approach with Customer, the transformation approach depends on the Customer, People, Processes and Tools.
How do we convince our Customers on Transformation?
Let us first categorize our Customers based on Agile Adoption willingness.
- Willing to Adopt
If the Customer
- Understands “Agile”, go ahead and implement Agile and continuously improve. No major challenges foreseen in terms of implementation
- Has not understood Agile: Explain the extent of involvement and collaboration from their side for the success for the project. Explain the benefits and he/she should be ready to embrace agile
- Partially Willing but Skeptical
The Customer has not seen agile in action yet. Demonstrate and show how Agile is a solution to volatile requirements, big bang UAT and large rework efforts due to limited customer interactions. Explain the Implications about the outcome viewing the product only during UAT. Take up a small project whose length is less than 2 months to convert it into agile.
- Totally against
Try to understand why the Customer is against Agile. Analyze the myths and perceptions. Provide the suitable mitigation/solutions for the challenges that customer is perceiving. Provide more insight into the Agile processes. Agree for a pilot project. Once you execute pilot project successfully, customer may be willing to change viewing the product only during UAT. Or a small project whose length is less than 2 months to convert it into agile
- Technically not really challenging but have impact at the organization level.
- Feature/Product that customer can touch/feel.
- Minimum impact to the organizations objective if the project fails.
- Must have the ability to deliver iteratively
- Clear problem statements identified for solutioning by Agile
Measurement of Agile Adoption by OPERA
We may measure our Agile Adoption journey through
- Defined Agile Maturity levels
- Maturity Assessment Frameworks
- Continuous Retrospectives and Brain Storming
- DoDs for each OPERA element based on the project/program
Extended Usage of OPERA
OPERA may be extended to adopt any of the specific Agile practices
- TDD: Measure Adoption by Code Coverage% each sprint and escaped defects
- BDD: % of BDD adopted scenarios
- Continuous Delivery: DevOps Maturity assessment
- Kanban: Measure Cycle time
- Distributed Agile: Measure the Agile Maturity levels in the distributed environment
Success Factors of OPERA
The number of projects that have successfully adopt Agile transformed from the traditional frameworks relate to the success of Agile Adoption by OPERA. Increased demand from Customers on conversion of their existing projects and satisfaction from customers after adoption is also a measure of success. Above all, customer satisfaction is the key to success!
OPERA is a drama to set the music of Agile Transformation!