Abstract This session covers understanding the need for scaling Agile projects, benefits of scaling projects and challenges in scaling Agile projects. Session uses a practical case study to explain these. The case study used is not a SAFE agile project, nor it used LeSS/DAD. It is more like Scrum of Scrums Session Takeaways 1. Session helps in understanding the need to scale an Agile project 2. Session helps in Benefits of Scaling Agile projects 3. Session helps in understanding typical challenges faced in Scaling 4. Covers very brief of existing scaling models 5. Case Study

1. Case Study
for
Scaling Agile Projects
Raj Kamal Vasam
Enterprise Agile Coach/Delivery Manager
IBM
https://www.linkedin.com/in/vrajkamal

2. What is Scaling?
Is it same as implementing Agile in all the teams?
Why should we scale Agile projects?
Should we scale all Agile projects?
What are the popular scaling frameworks?
2

3. Case Study - Introduction
Workday
Cloud ERP for HCM
Workforce planning
Compensation
Recruitment
Talent Management
WebMethods
Integration Platform
MDM
MFTS
Enterprise Bus
Sharepoint
Employee Collaboration
Workflows
LoB applications
Document management
Legal
Asset Management
Audit records
Risk Management
Exit surveys
Testing
LOB specific
Team 1 Team 4Team 2 Team 5Team 3
3

4. Challenges with Isolated Teams
• Lack of Agile Maturity
• Inconsistency of timely deliverables
• Lack of vision/Big picture
• Defects, Technical debt
• Lack of coordination & Collaboration
• Not knowing other team’s responsibilities
• Not having common product backlog
• Loss of visibility
• Loss of Agility
• Rework
• Late feedback
• Lack of Traceability
4

5. Results
• Great improvement in DRE
• Significant reduction in Defect Rejection Ratio
• Rework reduced significantly
• Resulted in continuous delivery – delivery stream
• Faster delivery / reduced delivery cycle
• Increased productivity
• Improved quality
• Independent QA teams abolished; QCOE formed
• Dependencies well managed
• Clear accountability for each epic/story
• Predictability
5

6. Challenges in Scaling Agile Projects
www.stateofagile.com
6

7. A glance at Scaling Frameworks
Not a prescriptive method
Easy to understand/scale
Roles remain unchanged
Flexibility in new ceremonies
Big picture
Team, Program, Portfolio
Specific Roles at each level
Involves all levels of organization
Promotes collaboration
High focus on release
Highly prescriptive
Two frameworks depending on
size
Framework-1:
Upto 10 teams
Basic roles are unchanged
Cross team retrospective
Feature teams
Framework-2:
More than 10 teams
Additional role: Area Product
Owner
Easy to scale
Least prescriptive method
People first
Focusses on “Solution Delivery”
Learning oriented
Emphasis on architecture
3 Phases: Inception, Construction,
Transition
Focus on “Potentially consumable
Service”
Less market share
SoS DADSAFe LeSS
7

8. A glance at Scaling Frameworks
8