scaling amdocs pbg from team scrum to a multi-program portfolio using lean and kanban - shirly...

Click here to load reader

Post on 10-May-2015

2.205 views

Category:

Documents

3 download

Embed Size (px)

TRANSCRIPT

  • 1.Scaling Scrum using
    Lean/Kanban @ Amdocs
    September, 2010
    Shirly Paster-Benor

2. Agenda
Amdocs and PBG challenges Agile in PBG Phase 1 Scrum for development teams Phase 2 scaling to Lean& Kanban Roadmap and vision
3. CUSTOMER EXPERIENCE SYSTEMS INNOVATION
we provide state-of-the-art customer experience system products and services, allowing Service Providers to achieve their business goals and gain a competitive edge
4. annual revenuesin excess of
$3 billion
Some of our customers
global employees
17,000+
customers in over
50 countries
5. PBG Division Product Business Group
1500 developers and testers6 locations35 stand alone products5 lines of businessMore than 100 components1 portfolio
6. Galileo
Agile&LeanImplementation in Amdocs Product Business Group (PBG)
7. Agile as Planned organizational Change
Balance
Balance
Balance
Balance
Balance
8. From Team Agility to Enterprise Agility
9. Phase 1 Main Actions
Establish overall end to end agile process
Perform Organizational Changes
Establish organization heartbeat
Define the backlog entities and structure
10. Phase 1 Main Actions
Perform Organizational Changes
11. Change the evaluation process
Change Teams To Co-Location where needed
Remove
Middle Management
Merge Testing and development organization
Perform Roles and responsibilities changes
Product Manager Vs Product Owner
12. Two Strategic Themes for Creating the Change
Culture
Flexibility &Agility
LeadershipFrom Managementto Leadership
Trust
Respect
Openness
Leadership
Making an impact
Culture
Flexibility & Agility
13. Phase 1 Main Actions
Establish organization heartbeat
13
14. Backlog Management Process
Release Plan
Strategy
Managing Release Backlog
Initiations
Opportunity/customerTeam
Solution Overview
High Level Design
Top Priority Mini Release Items
Portfolio Planning
Plan 1
Plan 2
Plan 3
Plan 4
Portf Mini Release 1
Portf Mini Release 2
Portf Mini Release 3
Portf Mini Release 4
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 ProductIntegration
14
15. Phase 1 Main Actions
Define the backlog entities and structure
15
16. Backlog Entities
Release Vehicle
Product/Architecture
Release
Project
Product
Portfolio
MiniRelease
Component
Story
Agile Group
Feature
Sprint
Initiative
Epic
Epic
16
17. We were happy with the results
BUT
More challenges waited around the corner
18. Not enough visibility to E2E process
19. Requirements not ready for design, Designs not ready for development Changes run into sprint
20. Not enough collaboration within Customer teams and with Scrum teams
21. No focus on E2E cycle time
22. No sync between backlog grooming and development
23. The solution:
Lean / Kanban for customer teams, to ensure flow of work
24. Step 1: Value Stream mapping
25. 26. 27. 28. 29. Step 2: Create Kanban board for project/product
30. We started this way
31. Than became more structured
32. e-Kanban in Team Player
(In house development)
33. What is the best granularity?
Features?
Epics?
Stories?
Epics/MMFs!
34. ScrumBan
DONE
READY!
E2E Flow
Scrum Team
Opportunity Team
34
35. 36. Customer (opportunity) team
36
37. Step 3: Limit the WIP and create a pull system
38. WIP limit guidelines for customer teams

  • Set the initial WIP limits

39. Analysis should be made after 1 months and after 2 months. Only then make changes if needed 40. WIP limit is constantly violated probably too tight limit 41. WIP limit is never violated too loose limit, decrease it 42. WIP limit is sometimes violated good. Analyze the root cause for violation and solve it.