Sandeep Paudel presented on "Beyond Scrum and SAFe - How to Choose the Right Framework for your Teams or Organizations" at the DC Scrum User Group (DCSUG) on June 11, 2021. Are you confused why Scrum is not working for your software development teams; then you moved to Kanban, which turned out to be a worse decision too. In this presentation, I will share the importance of the Strategic Product Development Life Cycle and not just the Software Development Life Cycle (SDLC) when building software products. You will uncover the Cynefin Framework and how you can apply it to your use case to find the Right Software Delivery Framework for your Teams and Organizations.

1. Confidential
Beyond Scrum and SAFe
How to Select a Right Product Delivery Framework for your Teams or ARTs?
Sandeep Paudel
RTE and Agile Program Lead, Capital One Bank
Friday, June 11, 2021

2. Confidential 2
Capital One is Hiring

3. Confidential 3
Agenda
1. State of Agile Report (2007 - 2020)
2. Importance Product Lifecycle for Soware Products
3. Cynefin Framework to Determine the Right Delivery Framework for your Product
4. Should you always Scale Agile?
5. Q&A

4. Confidential 4
State of Agile Report

5. Confidential 5
Understand your Product LifeCycle (contd.)
New Product Development
COTS/
Open Source
Maintain
Legacy
Invest Divest
TIME
Adoption

6. Confidential 6
• Special Skills
• Need for Analysis
• Multiple
Workstreams
Complicated
• Cookie Cutter
• Predictable
• Routine type of
Soware
Development with
few customizations
Obvious
• Legacy/Mainframe
products
• Decline Stage of the
Product Life Cycle
• Spaghetti
Architecture
• New option is not
available or is too
expensive to replace
• Firefighting
Chaotic
What Category is your Product?
• Uncertain
• Experimental
• Evolving
• Building a New
technology
Complex
TODAY’S FOCUS

7. Confidential 7
Delivery Frameworks Based on Product Category
Chaotic
Act-Sense-Respond
Obvious
Sense - Categorize - Respond
Complicated
Sense - Analyze - Respond
Complex
Probe-Sense -Respond
Cynefin Framework
disorder

8. Confidential 8
A PMO Level Delivery Framework Suggestion
- Products were not complex or mostly requiring new development
- Balancing flow of different pieces of work is important
Class of Service Backlog Ready In Progress Done
Expedited Story e
Maintain/Ops 1. Story a
2. Story b
Fixed Date
3. Story c
4. Story d
Features Work
5. Story f
6. Story g

9. Confidential 9
State of Agile Report Scaling Agile (2020)

10. Confidential 10
Scaling Agile
Vertical and Horizontal Integration
- Upstreams and downstreams products or
logic for a product line
a. Credit Card (Vertical Integrations)
Marketing/Campaign - Eligibility -
Decisioning - Fulfilment
b. Horizontal Integrations
IOS - Android - PC
No Integrations
- No strong interrelationship among the
teams or Products line
a. Set of Similar Tools under one
Umbrella/Leadership

11. Confidential 11
Scaling Agile
Vertical and Horizontal Integration
Scale Up
- Adding more people or more teams
to an existing effort (involving one or
more interrelated products)
No Integrations
Scale Out
- Introducing Agile to multiple teams,
regardless of their interrelations

12. Confidential 12
Confidential 12
Do not Scale Up if
● You can achieve your goals with a single team*
● You have a single team and it cannot deliver
effectively using Agile principles and practices,
succeed with a single team first*
● purpose is to bring up uniformity or collect
common set of metrics
Should you always Scale up?
12
Confidential
*ScalingAgile Manifesto

13. Confidential 13
Selecting Scaling Agile Framework
Product Category Scale Up Scale Out
Complex LESS
Complicated SAFe (LPM)
Obvious
Mixed SAFe, DAD

14. Confidential 14
Build Your Own Agile Framework

15. Confidential 15
Thank you

16. Confidential 16
Appendix
State of Agile Report Link https://stateofagile.com/#