IT Solutions Delivery Process and Procedure

 IT Solutions Delivery Process and Procedure


IT Solutions Delivery Process and Procedure


Disciplined agile delivery (DAD) is a process decision framework that enables simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including Scrumagile modelinglean software development, and others.

The primary reference for disciplined agile delivery is the book[1] of same name, written by Scott Ambler and Mark Lines.

In particular, DAD has been identified as a means of moving beyond Scrum.[2] According to Cutter Senior Consultant Bhuvan Unhelkar, "The DAD framework provides a carefully constructed mechanism that not only streamlines IT work, but more importantly, enables scaling.".[3] Paul Gorans and Philippe Kruchten call for more discipline in implementation of agile approaches and indicate that DAD, as an example framework, is "a hybrid agile approach to enterprise IT solution delivery that provides a solid foundation from which to scale."


Key Aspects




The Disciplined Agile Delivery framework identifies that "People, and the way they interact with each other, are the primary determinant of success for a solution delivery project."


DAD specifies a robust set of primary and secondary roles, outlined in the 'Roles' section below.



The DAD process framework promotes the ideas that team members should collaborate closely and learn from each other, that the team should invest effort to learn from their experiences and evolve their approach, and that individuals should do so as well.[11]



DAD adopts and tailors proven strategies from existing methods such as Scrum, Extreme Programming (XP), Agile Modeling (AM), Unified Process (UP), Kanban, Outside-in software development, and Agile Data (AD). Rather than taking the time to adapt one of these existing frameworks, with DAD all of the effort of combining relevant pieces of each technique has already been done.


Full delivery lifecycle

Unlike first generation agile methods that typically focus on the construction aspects of the lifecycle, the DAD lifecycle addresses the entire project from the point of initiation all the way to production and post-delivery production activities.


Process goal driven

The DAD framework approach is goal-driven rather than prescriptive. Compared to Scrum, which prescribes that all work is managed via a product backlog queue, DAD suggests choosing a work-prioritization strategy based on whatever factors are most important to project stakeholders.


In a DAD approach, strategies could be driven by several factors: business value, risk, due date, dependencies, or any combination thereof. DAD describes the tradeoffs associated with each strategy and discusses the viability of each.


Solution focused

Disciplined Agile Development matures focus from simply producing software to providing consumable solutions that provide real business value to stakeholders. While software is clearly an important part of the deliverable, being solution focused means taking a holistic view of the overall problem. This can lead to suggested updates in hardware, business/organizational processes, and overall organizational structures.


Risk-value lifecycle

The DAD lifecycle is risk and value driven. It extends Scrum's value-driven lifecycle which produces potentially shippable software each sprint/iteration so that it explicitly includes light-weight milestones such as ensuring stakeholder consensus as to the scope of the project early in the lifecycle, proving the architecture with working code early in the lifecycle, ensuring sufficient functionality exists before transition, and ensuring production readiness before actual release of the solution.


Enterprise aware

Enterprise awareness is a crucial philosophy of the DAD framework. DAD teams work within an organization's enterprise ecosystem just like any other team. Ideally a DAD team will leverage existing resources in order to reduce overall delivery time and cost, and can work in parallel to other teams in the organization. An important aspect of enterprise awareness is that DAD has explicit DevOps [12] practices and strategies built right into the framework.



Please contact us for details. One of our engineers will be happy to discuss your requirements.

Last modified on Tuesday, 09 February 2016 22:33

Login to post comments
Go to top