Experience of building Agile Center of Excellence (CoE) for organization-wide Agile maturity
When any organization plans to move to Agile methodology, it needs to plan multiple initiatives for successful transition. One of the important initiative would be building an Agile Center of Excellence, a team which would support for consistency of Agile implementation across the organization. The Agile CoE we built worked on multiple aspects such as:
- Defining organization-wide Agile methodology, tailoring it as per organization environment if required
- Build knowledge of Agile across the organization
- Supporting the team members with any ongoing queries
- Support in building required Tools and Templates required implementing Agile
- Assessing Agile implementation of different projects, identifying any gaps or improvement areas
This session would cover practical experience of how we built a successful Center of Excellence, which become a big enabler for successful Agile transformation.
Outline/structure of the Session
- What is Agile Center of Excellence
- What is difference between Agile CoE and CoP (Communities of Practice)?
- The charter we had for Agile CoE
- What are the areas that are handled by CoE?
- Experience of building a successful CoE
- What worked / What did not work?
- Guidelines for building a successful CoE
- How to develop Agile Center of Excellence in any organization, to support organization-wide Agile transformation initiative
- The success criteria for CoE
- Benefits for building Agile CoE
Anyone interested in strengthening Agile environment in their organization
schedule Submitted 3 years ago
People who liked this proposal, also liked:
Rahul - How to measure the outcome of Agile transformation?RahulAgile Program Manager with 15+ years experiencePersistent Systems
schedule 3 years 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.
Ashish Pathak - Why Businesses should not ignore Technical Debt - A Case StudyAshish PathakSr. Process ManagerPersistent Systems Limited
schedule 3 years agoSold Out!
Cases like the Toyota’s Unintended Acceleration case of 2007 highlight the impact of bad engineering practices on the quality of the product. This eventually impacts the business and the organization’s reputation as well. There have been several such instances in recent history, yet business stakeholders get tempted to compromise on the sound engineering practices for having quick gains. This approach, most of the times, is due to lack of understanding of these practices and under-estimating their negative impact in the long run. The aim of this paper is to highlight this impact and present a strong case for paying enough focus on concept like technical debt to reduce and control it in software development context.