Talk at local Scrum Chapter

1. About me:
Agilist: SAFe, CSP, CSM, CSPO, PMP
Scientist: PhD Space Technology
Engineer

2. Disciplined Agile Delivery
(DAD)
A hybrid Process Decision Framework
By
Farid Askari, PhD,SAFe,CSP,CSM,CSPO,PMP
June 15, 2017
Agile and Scrum Practitioner Forum

3. https://www.disciplinedagileconsortium.org

4.  “The Disciplined Agile Delivery (DAD) process
decision framework is a people-first,
learning-oriented hybrid agile approach to IT
solution delivery. It has a risk-value delivery
lifecycle, is goal-driven, is enterprise aware,
and is scalable.”

6. DAD
SCRUM XP SAFe LEAN/KANBAN AGILE MODELING
AGILE DATA
Disciplined Agile Delivery (DAD)
A Hybrid Process Decision Framework
OPEN UNIFIED PROCESS

11. X
P

12. STANDARD
URGENT
FIXED DATE
SPRINT QUEUE
DEPLOYED
BACKLOG
SCRUM + KANBAN
HYBRID: SCRUMBAN
ANALYSIS DEVELOP TEST

18. Agile
Delivery
Continuous
Delivery
Exploratory
Lean Startup
Release
Management
Operations
Support
Data
Management
Program
Managemen
t
IT Delivery
DEVOPS
IT
Governance
Continuous
Improvement
People
Managemen
t
DA 2.0 (by Mark Lines)
Portfolio
Management
Product
Management
Enterprise
Architecture
Life cycles

19. Agile Philosophies
1. Teams should be whole, all abilities
2. Collaborate effectively, not hand off documents to another
3. Non-solo work is more effective than working alone
Mob programming, XP
4. Physical proximity improves teams effectiveness
5. Simple tools enable collaboration
6. Learn from experiments throughout the life cycle, Retros
7. Agile teams are self organizing
8. We need leaders, team coaches, facilitators
9. Stakeholders have greater visibility into agile teams
Stear agile teams, make decisions

20. 1. Locally owned DEV team own their own process
2. The best architecture and design emerge over time.
3. Do the simplest thing possible
4. Agile teams embrace changing requirements
5. Travel light weight artifacts, concise documents
6. Too much upfront modeling and planning increases
risks
7. Reduce the feedback cycle
8. Test often and early, ideally first
9. Build quality in
10. Deliver quickly to produce greater stakeholder
satisfaction

21.  Team builds solutions not just SW
 Build solutions for a wide range of stakeholders
not just customers
 If something is hard, do it more often
◦ If deployment is hard do it more often
 Repeat results are far more important than
repeatable processes.
 We need to be enterprise aware, go beyond team
see big picture
 Optimize the whole (lean)
 Locally owned, every team owns its process
 Bodies of knowledge should work together

22. DAD TEAM

26. A Lean version of DAD lifecycles

30. Review Analysis
WIP limit
DoneImplementingBacklogAnalysisFunnel
WIP limitWIP limit
Funnel
FEATURES
Breakdown of EPICS
Individual FEATURES
Program EPICS
Example of Program Kanban