Your SlideShare is downloading. ×
Safedad
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Safedad

68
views

Published on

Scaled Agile - Is SAFe and DAD are complimentary

Scaled Agile - Is SAFe and DAD are complimentary

Published in: Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
68
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SAFE DAD
  • 2. SAFE VS DAD SAFeSAFeSAFeSAFe DADDADDADDAD SAFe is a scaling framework and has been empirically derived DAD is a "process decision framework" SAFe focus on three levels of scaling – project, program, and portfolio 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 , Program Execution, Alignment, Transparency. 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 enterprise aware. 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.
  • 3. THANK YOU