1 / 31

Scaling Agile In Amdocs PBG

Scaling Agile In Amdocs PBG. Erez Katzav. Your presenter…. Erez Katzav Agile implementation manager in Amdocs PBG Division. Focusing on: Agile Coach for teams and executives Change Management and effective agile transition

abigail-vega
Download Presentation

Scaling Agile In Amdocs PBG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Scaling Agile In Amdocs PBG Erez Katzav

  2. Your presenter… • Erez Katzav • Agile implementation manager in Amdocs PBG Division. • Focusing on: • Agile Coach for teams and executives • Change Management and effective agile transition • 11 Years of experience in the Software industry: Project management, Program management, Development manager • Find me: erezkat@amdocs.com

  3. Agenda A little background Our organisation Our complex business Our transition How we planned our organisation transition Managing our complex backlog Our transition timeline Did we improve? Phase 1: Scaling Scrum. Phase 1.5: Change organization structure and improve backlog Phase 2: Control and track the backlog grooming process

  4. PBG Product Business Group

  5. What is so complicated? 50 Products 100 Components 1 Portfolio 1500 R&D employees 6 Countries, 9 Locations

  6. Business Unit VP Business Unit $ Product Product Product $ C Dev Director Dev Director Dev Director C Component Component Component Dev Manager Dev Manager Dev Manager Dev Manager Dev Manager Dev Manager Component Component Component Component Component Component $ C Product Structure Release Strategy Organization structure Locations P&L Culture

  7. Agenda A little background Our organisation Our complex business Our transition How we planned our organisation transition Managing our complex backlog Our transition timeline Did we improve? Phase 1: Scaling Scrum. Phase 1.5: Change organization structure and improve backlog Phase 2: Control and track the backlog grooming process

  8. Galileo Agile Implementation in Amdocs Product Business Group (PBG)

  9. Agile as Planned Organization Change Balance Balance Balance Balance Balance

  10. Implementation Strategy Implementation Strategy

  11. Stage 1.5 Implementation Start – Stage 1 Stage 2 Pilots Project Kick Off Mar 2008 Oct 2007 Aug 2009 Mar 2008 July 2007

  12. Agenda A little background Our organisation Our complex business Our transition How we planned our organisation transition Managing our complex backlog Our transition timeline Did we improve? Phase 1: Scaling Scrum. Phase 1.5: Change organization structure and improve backlog Phase 2: Control and track the backlog grooming process

  13. Step 1 – Main Actions Establish overall end to end agile process Establish organization heartbeatto synchronise the integration of all products, Scrum Teams, Scrum Masters, customer Teams… Define the backlog structure that support the heartbeat and product/Architecture structure

  14. Backlog Management Process Release Plan Strategy Managing Release Backlog Initiations Opportunity/customer Team Solution Overview High Level Design Top Priority – Mini Release Items Portfolio Planning Plan 1 Plan 2 Plan 3 Plan 4 Portf Mini Release 4 Portf Mini Release 2 Portf Mini Release 1 Portf Mini Release 3 Portfolio Heartbeat Products Iterations Scrum Team Portf Mini Release 2 Portf Mini Release 3 Portf Mini Release 4 Portf Mini Release 1 Portfolio Integration Lab Releases Development Product Integration

  15. Product/Architecture Backlog Entities Release Vehicle Release Project Product Portfolio Mini Release Component Sprint Story Agile Group Feature Sprint Initiative Epic Story

  16. Product/Architecture Backlog Entities Release Vehicle When scaling to enterprise there are many ways to see the backlog Teams View Product View System View Release View Project View Product Portfolio Mini Release Component Sprint Story Story Sprint Initiative Epic Release Project Feature Agile Group

  17. Product Product Product View View View Release Manager Project Manager Product Manager Agile Manager

  18. Opportunity Team Project Project Opportunity Team Feature PDM Backlog Items Product Backlog PDM Architect PgM QA Design Development Scrum Team

  19. Take Away… Find the right view tune /optimize your backlog to efficient the process Keep your stakeholders informed -with appropriate views of your backlog Watch the dependencies - make them visible in your backlog Involve the organization in evolving the methodology Keep the message of change clear and constant, say it in different ways

  20. Agenda 10 Min A little background Our organisation 10Min Our complex business Our transition How we planned our organisation transition Managing our complex backlog Our transition timeline Did we improve? 25Min Phase 1: Scaling Scrum. Phase 1.5: Change organization structure and improve backlog 20Min 20Min Phase 2: Control and track the backlog grooming process

  21. Challenges… No sync Between Backlog Grooming and Development Waste in Requirement Definition, idle resources Not Enough visibility to the end to end process Not enough focus on E2E cycle time Not Enough Collaboration inside Opportunity team and with Scrum teams Not Enough Quantitative Measures Hard to show success, Hard to identify concrete areas for improvement focus Big features Less ability to control Flow and improve time to market Pure Support Teams Planned Iterations don’t work

  22. Change the evaluation process Change Teams To Co-Location where needed Change Agile Group Structure Remove Middle Management Merge Testing and development organization Perform Roles and responsibilities changes Product Manager Vs Product Owner

  23. User Stories

  24. Outbound Customers Roadmap Product Backlog Initiations Inbound Product Manager Product Owner Scrum Team

  25. Take Away… Formalize user stories when you trust the teams to deal with the how… Differentiate Product Owner from Product Manager Structure Teams according to business rather then architecture

  26. Agenda 10 Min A little background Our organisation 10Min Our complex business Our transition How we planned our organisation transition Managing our complex backlog Our transition timeline Did we improve? 25Min Phase 1: Scaling Scrum. Phase 1.5: Change organization structure and improve backlog 20Min 20Min Phase 2: Control and track the backlog grooming process

  27. Continuous Flow-Based Opportunity Process • Based on Lean/Kanban Pull/Flow • Manage Work in Progress • Ensure sufficient READY buffer

  28. Pull/Kanban Project Backlog Tree Backlog Tree Opportunity Team Development Requirements (3) Solution Overview (4) HL Functional Design (4) Elaborated/Sniffed by the Team (5) Development Epic Feature A Feature B Feature A S. Story Story S. Story S. Story S. Story S. Story S. Story Epic Story Story Feature D Feature C Feature B Epic Epic S. Story Story In Progress In Progress In Progress In Progress In Progress Done Done Done Done Done WIP Lead Time

  29. Project/Component Kanban Board DONE READY! E2E Flow   Scrum Team Opportunity Team

  30. Take Away… Keep tools and process flexible Choose your battles and pace your change Visual control (Kanban) help enhanced team work Visualization Visualization Visualization Choose the model that works best for your organization

  31. Thanks Erez Find me: erezkat@amdocs.com

More Related