SAFE VS DAD
SAFe is a scaling framework and has been empirically
DAD is a "process decision framework"
SAFe focus on three levels of scaling – project, program,
DAD focuses on providing a foundation from which to scale
agile approaches to address the complexities of large
teams, geographic distribution, technical complexity, and
other scaling factors
Core values are
Code Quality ,
DAD core values are people first, learning-oriented hybrid
agile approach to IT solution delivery.
Risk-value lifecycle ,is goal oriented, is scalable and is
SAFe defines an Agile Release Train (ART). Iteration is to
team, train is to program and investment and Theme
funnel for portfolio
DAD promotes a full delivery lifecycle and as a result
defines three explicit phases: Inception where you initiate
the project, Construction where you build/configure the
solution, and Transition where you deploy the solution into
production or the marketplace.
Program level roles are defined
System Team, Product Manager, System Architect,
Release Train Engineer (RTE)
UX and Shared Resources (e.g., security, DBA)
Release Management Team
+ Team Level Roles(Scrum Master,PO, Team)
The primary roles (Team Lead, Team Member, Product
Owner, Stakeholder , Architecture Owner) are the ones that
you will typically see in most agile situations. The
secondary roles (Domain Expert, Technical Expert,
Specialist, Integrator, Independent Tester) are often
needed in scaling situations.