Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tour Montreal 2018

Ad

Getting Agile right - rebooting an
Agile organization in 100 days
MAURIZIO MANCINI | CONSULTANT | EXEMPIO.COM | @QAANDPROC...

Ad

Reboot?

Ad

Sign 2
Teams still early in the Agile
journey - number of flavours of
Agile is equal to the number of
teams you have
3 Mos...

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Hier ansehen

1 von 76 Anzeige
1 von 76 Anzeige

Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tour Montreal 2018

Presentation at Agile Tour Montreal 2018 by Maurizio Mancini of Exempio and Paul T. Ryan CTO of OpenX.

Many organizations think they are Agile when they are not. Here is how to recognize when you need an Agile reboot and how to reboot your organization to become a true Agile organization.

Presentation at Agile Tour Montreal 2018 by Maurizio Mancini of Exempio and Paul T. Ryan CTO of OpenX.

Many organizations think they are Agile when they are not. Here is how to recognize when you need an Agile reboot and how to reboot your organization to become a true Agile organization.

Weitere Verwandte Inhalte

Diashows für Sie (19)

Ähnlich wie Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tour Montreal 2018 (20)

Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tour Montreal 2018

  1. 1. Getting Agile right - rebooting an Agile organization in 100 days MAURIZIO MANCINI | CONSULTANT | EXEMPIO.COM | @QAANDPROCESSGUY PAUL T. RYAN | CTO | OPENX.COM | @PTRYAN123
  2. 2. Reboot?
  3. 3. Sign 2 Teams still early in the Agile journey - number of flavours of Agile is equal to the number of teams you have 3 Most Common Signs you need a Reboot Sign 3 You have Featuritis or Small-ball Sign 1 You have 3 to 4 times more “projects” than your teams can deliver
  4. 4. Bonus 1 You’ve rolled out Agile at least 3 times already Bonus 2 People tell you ‘Agile Doesn’t work’ Bonus Signs
  5. 5. Everyone Was Busy
  6. 6. PLAYING AGILE BEING AGILE TO DO IN PROGRESS DONE
  7. 7. Kick Starting your Reboot The Five Steps
  8. 8. What is OpenX?
  9. 9. # 1 Buy-In from the Top!
  10. 10. # 2 Clear Business Goals
  11. 11. Business Goals
  12. 12. Business Goals
  13. 13. Business Goals
  14. 14. Business Goals
  15. 15. # 3 Clear Ownership
  16. 16. Role Confusion “Why did the engineers build it if it wasn’t going to work?” “I thought the CTO sets development priorities” Process Confusion “Hey -- I just said it would be a good idea to add the feature — I didn’t tell them to do it!” Accountability Resistance “We don’t need any planning — it just slows things down”
  17. 17. # 4
  18. 18. # 5 Get Moving
  19. 19. 100 Days and Counting Our Roadmap
  20. 20. Strategic Assessment Sept 2017 Oct 2017 Team Assessments Dec 2017 Agile Refresher, Tool Realignment Team Assessments and Agile Refreshers Nov 2017 100 Business Days and Counting… Our RoadMap Organization-wide meetings on priorities, accountability & drive Nov 2017 Nov 2017 Tech Roadmap for TechDebt
  21. 21. Go! January 2018
  22. 22. Strategic Assessments
  23. 23. Meet with CTO Gather his perspective Meet with Key Team Members Gather teams perspective of companies Strategic Direction Vision 1 year and 3 year Tech Debt Analysis Quality of current code Strategic Assessment
  24. 24. Strategic Assessment KEY FINDINGS AND RECOMMENDATIONS
  25. 25. Everything is a Top Priority Teams Playing Agile instead of Being Agile Portfolio and Program planning inadequate Strategic Assessment Key Findings Tech Debt Analysis Level was Reasonable TO DO IN PROGRESS DONE
  26. 26. ARB and PC Architecture Review Board and Product Council Weighted Shortest Job First WSJF for Project Ranking Portfolio Kanban for Upper Management WSJF RECOMMENDATIONS
  27. 27. Projects use Scrum or Kanban Dynamic Teams Scrum Kanban RECOMMENDATIONS
  28. 28. Strategic and Team Vision
  29. 29. Team Assessments
  30. 30. Interviewed more than 50 people across various roles Through the use of 1-1 or small group interviews Directors Managers Team Leads Team Members
  31. 31. Conducted a survey-Five Point scale 31 questions on 6 dimensions and a comments section
  32. 32. Agile Basics (6) Values and Principles, Scrum or Kanban roles, Stable Teams, Epics and Stories Product Ownership (5) Available, Vision, Product Backlog Prioritization, Refinement and Readiness, Acceptance Criteria Team Roles and Agile Skills (5) Clear roles, Sprint Planning and Goals, Definition of Done, Predictable Velocity, Building in Quality
  33. 33. Team and Processes (5) Scrum Master assigned, user stories ready, self- organized team, collaborative planning, retrospective and followup Release Management and Delivery (5) Release Planning, product backlog prioritization, business feature estimation and slicing, cross team dependancies, Sprint Reviews Quality (5) Quality goals: corporate, software product, software component. Sprint quality goal improvements, quality measurements being made
  34. 34. Attended a number of team meetings Where I needed a little more insight into how the team or product worked
  35. 35. Team Assessment Results POSITIVE PATTERNS AND ANTI-PATTERNS
  36. 36. Keep it Up! • Team Work • Self Organized Teams • Two Week Release Train • Technical Level of QA Team Members • Continuous Integration was available • Some Dev helping with Automation • Tools were up to date • Separate team doing End to End testing • Some requirements were on the Wiki Opportunities to take it to the Next Level
  37. 37. Opportunities Discovered • Who owns Quality? • Who owns Test Automation? • Accounting for Test Automation • Maintenance • UI Automation Path • Release Process and Cadence • Release Tool and CI process adoption • Process and Tools Team • Tool Tune-Up • Service Desk - Replace • Portfolio Management - Replace Opportunities Discovered • Maturing Agile • Role Clarification • Project Prioritization • Organization of Work • Backlog Cleanup • What’s an EPIC? • One Story at a Time • Release Planning • Estimation • Tech Debt Tracking • Updating Requirements • Dev/QA Ratio • Hiring and On-boarding • Test Environments Many of these Opportunities are Common Anti-Patterns found in many organizations
  38. 38. People Process Tools Key Recommendations
  39. 39. Role Clarification and Maturing Agile
  40. 40. Scrum Master? PM Line Manager? Role Confusion PM PM PO Project Manager Program Manager Product Manager Product Owner
  41. 41. No Full Time Scrum Masters Product Owner role was not clearly defined People Playing Multiple Roles
  42. 42. Agile Refreshers • Scrum/Kanban Short Refresher - ½ day • Scrum/Kanban Full Refresher - 1 day • Scrum Master Training - ½ day • Product Owner Training - ½ day • Being an Agile Manager - ½ day
  43. 43. We focused on: • Getting back to the basics • Fixing the misconceptions • Ensuring everyone had the same foundation • The roles Agile Refreshers
  44. 44. Who own’s Quality?
  45. 45. 1. QA Director-Advocate of Who owns Quality 2. Promote the implementation of a DevOps culture 3. Holding a QA education event Top 3 Recommendations
  46. 46. Aligning the Process
  47. 47. Recommendation • Minimum - Close all issues older than 1 year. • Issues older than 6 months. Backlog Cleanup Most common Anti-Pattern “We have this large number of issues in the backlog because ‘one day’ we may come back and do the work…” • Projects with hundreds of issues older than 2 years.
  48. 48. • Sounds basic, but not really • Scaling Agile confusion in definition • EPIC was being used to manage Projects What’s an EPIC? Recommendation Bring it back to the basic definition
  49. 49. One Story at a Time • Stories were too large - Some were EPICs • Stories were just work tasks • Teams needed to focus • Stop Starting, Start Finishing!
  50. 50. Process and Tools Team
  51. 51. The Importance of the Process and Tools Team • Mechanics of the triad • Not just tool configuration • Team owns the triad! • Agile Coaches and Scrum Masters • Community of Practice (CoP)
  52. 52. Aligning the Tools
  53. 53. Aligning the Tools-OpenX Context • 22 Teams-Mostly Software Teams, some Operational Teams • Projects -Mostly Software, a few Operational • PMO -Required Portfolio Management
  54. 54. TOOL CONFIGURATION SPECTRUM Use the tool out of the box - No Configuration OpenX Why did you buy a packaged software? OOB Extreme
  55. 55. Common Anti-Patterns • Tools are being used improperly • Tools are not optimally configured Tools are impacting the effectiveness of the teams and the process
  56. 56. Teams told that tools couldn’t do something when they could Never shown the potential of the tools Previous tool experience - impacting higher level reporting Impact of tool mis-use and configuration on the Teams
  57. 57. Implemented Process to use the wiki collaboration with the task management tool. Replaced Homegrown service desk with a modern service desk Intervention We optimized the task management tool through a deep intervention. Aligning Tools for the Reboot
  58. 58. Portfolio Management • Projects Products • Replaced the more complex tool • Start Simple - Get the basics working • Portfolio’s are complex - Some data manipulation
  59. 59. Results — 10 Months
  60. 60. The Good The Bad The Ugly
  61. 61. The Good • 28 Projects completed • Clear project prioritization • Scrum & Kanban both used • Project teams have all skills required to launch • All teams have scrum masters, product owners and are self- empowered
  62. 62. The Bad Project Portfolio • Monotonically increasing backlog w/o grooming • Phases of a project without any value attainment • Inadequate estimates of value & no value accountability Staffing • Too many multiple-project assignments (key resources) w/context switching problems
  63. 63. The Ugly Go To Market (GTM) • Not used to project completion Prioritization • Objectives -> Initiatives -> Project prioritization Staffing • Managers moving around resources
  64. 64. Quality • Solid progress on culture change - quality owned by everyone • Dev/QA wall slowly coming down • DevOps culture slowly starting to emerge
  65. 65. The Tools • Optimized for OpenX reality • 1-1, Task Management - Wiki Space association • Moved to a simpler Portfolio Management tool • Migrated from home grown service desk to modern Service Desk
  66. 66. Key Takeaways and What we would do differently
  67. 67. Transformation is Hard!
  68. 68. It Starts from the Top Exec Portfolio Kanban
  69. 69. Start with the Basics
  70. 70. How we would start the journey today… • Metrics First • Staffing Consistency • Real Value Estimation • Limit & Groom Backlog • Go To Market (GTM) • DevOps Culture
  71. 71. The Power of the Cloud
  72. 72. MAURIZIO MANCINI | CONSULTANT | EXEMPIO.COM | @QAANDPROCESSGUY PAUL T. RYAN | CTO | OPENX.COM | @PTRYAN123 Thank you! Merci!

×