It is ironic to start reading a book about a new Agile approach and to find the following quote in it: “The explosion of “branded” agile methods has resulted in a jargon-filled confusion of siloed tribes made up of uncollaborative zealots. — Mark Kennaley, Author SDLC 3.0” Disciplined Agile Delivery (DAD) is defined as “a hybrid approach which extends Scrum with proven strategies from Agile Modeling (AM), Extreme Programming (XP), and Unified Process (UP), amongst other methods. DAD extends the construction-focused lifecycle of Scrum to address the full, end-to-end delivery lifecycle from project initiation all the way to delivering the solution to its end users. The DAD process framework includes advice about the technical practices purposely missing from Scrum as well as the modeling, documentation, and governance strategies missing from both Scrum and XP.” Disciplined Agile Delivery is strongly influenced by RUP and by Scott Ambler’s Agile Modeling and Agile Data approaches that are often cited in the additional resource sections. Starting with the realistic diagnostic that many teams are unable to customize up or down existing software development processes for their own context, the authors have tried to provide a hybrid, goal-driven and lightweight (although it needs 500 pages to describe it) process that will provide a “start from the middle” way. The question remains open if teams that are unable to customize other approaches could easily absorb and adopt DAD? There might be a partial answer in the book “Your organization needs to invest in mentoring, training, and [...]
The post Disciplined Agile Delivery first appeared on Scrum Agile Project Management Expert.↧