Downloaded 102 times
Uploaded byMichal Epstein
Agile evolution lifecycle - From implementing Agile to being Agile
This document outlines an agile evolution lifecycle consisting of adoption, adjustment, and advancement. It discusses scaling challenges with initial agile adoption within teams and a lack of visibility outside teams. The adjustment phase emphasizes focusing on small, well-defined user stories and taking responsibility for deliveries. Advancement challenges working agile in organizations needing roadmaps for customers and discusses prioritizing features by business value and cost to fit within scope. The final culture stage involves organizational unity across functions, adapting approaches, and focusing on short cycles of gradual value to keep customers happy.
More Related Content
Similar to Agile evolution lifecycle - From implementing Agile to being Agile
![bussiness communication[1].pptx work and stress](https://cdn.slidesharecdn.com/ss_thumbnails/bussinesscommunication1-251123030028-578a5e39-thumbnail.jpg?width=640&height=640&fit=bounds)
Agile evolution lifecycle - From implementing Agile to being Agile
- 1. From Implementing Agileto Being Agile Agile Evolution Lifecycle Michal Epstein January 2014
- 2. Agile Evolution Lifecycle Adoption Adjustment Advancement Culture
- 3.
- 4. Adoption Scaling •What worked well? • Team spirit and independency • Dev-QA collaboration • What required improvement? • Insufficient visibility outside the team level • Missing ability to plan and predict • Difficult to improve • Focus on tasks and estimations, less on deliveries • Planning process was lacking
- 5. Adjustment Emphasis onlyon few scrum basics: Sprint as a checkpoint for the team efficiency Deliver MVF’s • Work on small and well defined user stories • Focus and WIP limit Be an owner • Take full responsibility over team deliveries. Use tools for visibility and improvement
- 6. Advancement Challenge: Howto work Agile in an organization that needs to reflect a roadmap to its customers?
- 7. Advancement Direction isclear. Path might change.
- 8. Scope to fit - What is the business value we get? - How much are we willing to spend? Estimate the entire release and set strict timelines - When will it be ready? - How much should it cost? Advancement OUT IN
- 9. List features Business value Cost Scope to fit Prioritize Scope to Fit Advancement
- 10. Culture Strong organizational unity (marketing, sales, R&D) Altering internal and external approach Short cycles and gradual value Happy Customers
- 11. Agile Evolution Lifecycle Culture Agile as a Culture Advancement Agile beyond R&D Adjustment Visibility and Adjustment Adoption Learn and Practice
- 12. Don’t let theChange manage you.. Manage the change! Thank you
Editor's Notes
- #4 השלב הראשון הוא שלב האימוץ. כשמתחילים לשחק במשחק חדש, קודם כל צריך להבין את החוקים ולעקוב אחריהם באדיקות. אז למדנו מה זה אג'ייל וקצת גם על מונחים ברוגבי. למדנו למה זה יותר טוב מווטרפול. שיננו את המניפסטו והשתכנענו שזה כדאי. התחפשנו לחזירים ולתרנגולים, התאמנו את עצמינו להגדרות התפקיד בהתאם לדרישות ובנינו workflow ברור ומוגדר היטב. הנסיון שלנו בלייבפרסון היה כזה: From decision phase to implementation – 2 weeks Driven with upper management to accelerate delivery and improve quality Training session for the leadership and development teams Re-organization to fit Scrum roles 3 teams Followed the rules Implementation in teams’ level Not much visibility to the entire organization No tools Only white boards and sticky notes