7
Why DAD? 6 Best reasons why OR Removing the pain of transformation to Agile

Why DAD? 6 Best reasons why OR Removing the pain of transformation to Agile

Embed Size (px)

Citation preview

Page 1: Why DAD? 6 Best reasons why OR Removing the pain of transformation to Agile

Why DAD?

6 Best reasons whyOR

Removing the pain of transformation to Agile

Page 2: Why DAD? 6 Best reasons why OR Removing the pain of transformation to Agile

© Disciplined Agile Consortium 2

1) More than just Scrum or SAFeDAD Scrum SAFe

Includes: - Inception, construction, transition phases - architecture, design, testing, programming, documentation, deployment etc

Focus on Construction Based on Scrum but layers on portfolio and programme levels

Focus on complete solution Focus on software Focus on software

Pragmatic – easily tailored Prescriptive Some flexibility

Lifecycles Inclusive of: - Scrum - Lean, Kanban, Continuous, delivery and hybrids - SAFe

One Approach Based on Scrum (now supports Kanban)

Framework Methodology MixScalable from single team to enterprise

Targeted at single or multiple teams

Targeted at large enterprises

Page 3: Why DAD? 6 Best reasons why OR Removing the pain of transformation to Agile

© Disciplined Agile Consortium 3

2) Goal Driven – removes pain of transformation

• Comprehensive set of predefined goals that can be augmented and tailored to meet the needs of individual projects

• provides guidance, not prescriptions, enabling you to easily tailor a strategy that reflects the situation that your team finds itself in

• process-oriented choices that define the trade-offs• Based on hundreds of enterprises around the world in a wide range of industries and

environments• Each goal has a set of defining factors each of which has a set of options that the

teams can select. The factors vary by goal. The options for each factor often range from ignore to formal acceptance.

• Inception goals focus on setting up a solution to work within the enterprise• Construction goals focus on incrementally building an enterprise solution • Transition goals have only one focus; to get the solution out to production• Ongoing goals focus on:

– Team goals - growing the team members, and improving the process– Project goals – Fulfilling the team mission and mitigating risk– Enterprise goals – enhance existing infrastructure and coordinate activities

Page 4: Why DAD? 6 Best reasons why OR Removing the pain of transformation to Agile

© Disciplined Agile Consortium 4

3) Multiple Lifecycles for flexibility

• Process defines delivery of solutions that comprise software, hardware changes, supporting documentation, improved business processes, and even organizational changes

• Support for:– Scrum– Lean– Kanban– Continuous delivery and – Hybrids– SAFe

Page 5: Why DAD? 6 Best reasons why OR Removing the pain of transformation to Agile

© Disciplined Agile Consortium 5

4) Solid foundation from which to scale Agile

• Supports successful scaling of agile and lean techniques• Defines full delivery lifecycles • Provides a breadth of software development advice• Goal driven approach provides the required flexibility for tailoring your agile

process to meet the challenges faced by agile teams working at scale• Builds in many foundational concepts required at scale, including: DevOps, explicit

agile governance, and enterprise awareness.• describes several strategies for organizing large or geographically distributed teams• describes a range of options for scaling your approach to agile and lean software

development, giving you context-sensitive options

Page 6: Why DAD? 6 Best reasons why OR Removing the pain of transformation to Agile

© Disciplined Agile Consortium 6

5) Solutions, not just software

• Process defines delivery of solutions that comprise software, hardware changes, supporting documentation, improved business processes, and even organizational changes

Page 7: Why DAD? 6 Best reasons why OR Removing the pain of transformation to Agile

© Disciplined Agile Consortium 7

6) DAD is Evolving

• We’re constantly learning as practitioners, learning about and experimenting with new agile and lean strategies all of the time. These learnings are constantly being applied to evolve the DAD framework