How to measure the outcome of Agile transformation?Rahul
schedule 1 year agoSold Out!
With many organization moving to Agile environment, it is important to have a model that can help us identify if the Agile Transformation is resulting in the expected outcome. This session would present different measurement models to measure the outcome of Agile transformation in an organization.
The paper covers various measurement models that can be used during different phases of Agile transformation. The session also presents outcome of a survey conducted by the author on how different organizations, Agile coaches & leaders are measuring effectiveness of their Agile implementation. It would present a research on how different organization perceive success of Agile adoption, what are the parameters used by different organizations and how different people present the changes observed by adopting Agile environment.
e.g. 20% respondents each said ‘Delivery cycle time’ & ‘Delivering business value’ as the key parameters. And other 20% mentioned ‘Working Software’ / ‘Customer Satisfaction’ & ‘Reduction in defects, waste & risks’ as the parameters for measuring success of Agile.
The session also presents a case study of Agile transformation where these different effectiveness measurement models were applied successfully. It covers various aspects like Business case definition of Agile implementation, Agile Transformation roadmap, Agile readiness assessment, Agile current state assessment, Agile effectiveness evaluation and ROI of Agile implementation.
The session would also include an Agile Innovation Game, where the attendees would brainstorm with their peers on how they currently capture the changes brought by implementing Agile in their organization.
Where does agile gets its agility?Satish Kamat
schedule 1 year agoSold Out!
While we have been dilly dallying moving to agile practices over last few years, early this year we decided that our small product team needs to be fully agile over next 6 months. The last 12 months of transformation has helped us all see whether Agile is as agile as it is made out!
We saw 40-50% increase in team velocity over waterfall for the same team!
Waterfall focuses on a release that spans across define, design, develop and verify to develop multiple features in an almost assembly line manner. Agile divides the features into user stories (as if sub-feature) and each of these user stories is defined, designed, developed and verified within one or more iterations by a dedicated scrum team. We discovered that this difference between waterfall and agile manifests to accelerate velocity through four sources.
These sources created a transformation, that we had not planned earlier. As we have expanded agile implementation from one team to now 5 teams, focusing on these sources of agility to preserve them is turning out to be key to scaling. This we think is the key to scaling enterprise for agile.