Adoption
The Mac Iver Group, LP Outformations, Inc.Are you seeing and hearing about the benefits of agility in other organizations and wondering how to get there? The Agile Adoption stage will point the way. In many ways how an organization transitions to agile principles is unique, but in this stage we are looking for real-world stories of success and learning from which we can glean some pointers of what’s common and help organizations, divisions, teams and individuals move forward.
The Agile Manifesto is about balance, “while there is value in the items on the right, we value the items on the left more”. Transitioning to agility is about helping both experienced and new practitioners achieve that balance.
The Agile Adoption stage focuses on doing that by answering questions like these:
- Is an organization even “ready” to transition? What would better prepare them?
- What business models better enable the transition to agility?
- What should be considered before selecting a transition approach?
- How do we manage risk and minimize disruption during the transition?
- How do we get organizations, divisions, teams, and individuals to think beyond just practices and embrace agile principles and values?
- How do we engage the business in transitioning to agile principles?
- What parts of the organization will be impacted the most? Or impacted first?
- How can we help team members understand how their roles and responsibilities will change?
- What roles are most impacted?
- How should we balance an agile adoption between agile practices, software engineering practices, and organizational change?
- How long does an agile transition take?
- What results should we expect to see first?
- How do we recognize that organizations and teams are reverting back to their old ways during the transition and keep them moving forward?
- How do we continue to evolve once the basics of agility begin to take hold?
The Agile Adoption stage wants to hear from executives, managers, leaders, and team members, coaches and consultants who have been there. We want to hear experience reports, start discussions, learn coaching and facilitation techniques, and provide a real-world view of the transition to and the adoption of agile practices and values.
If you’re submitting an experience report, please note: Your session can be 30-, 45- or 60-minutes long. Please indicate your preference in the Process/Mechanics area; it will override your choice in the duration dropdown above. The stage producer might ask you for a different session length based on the subject matter and scheduling criteria. Experience report papers are encouraged but not required this year. Since attendees like to learn details and specifics from experience reports, if you do not submit a paper, your presentation needs to be absolute dynamite, especially if it’s on the short side.
Reviewers
snowdolphin inc. Marakana.com Surpetition Kumido Adaptive Strategies Quality Tree Software, Inc. Software Engineering Management consultant