Why AgileEngine dumped Scrum for Disciplined Agile Delivery

DISCIPLINED AGILE DELIVERY

SCRUM IN A PERFECT WORLD

REWRITE STORY

LET’S DO THIS!

How did it go?

Mom, but we followed Scrum!

Why did we still fail?

REAL WORLD

WHAT’S MISSING?• NO big picture planning• NO upfront requirements• NO architecture role• NO early risk mitigation• NO acceptance criteria• NO budget approvals• NO dates

Scrum/Kanban are great for “how”.

But, they do not address “what”.

DISCIPLINED AGILE DELIVERY

DAD extends the development-focused lifecycle of Scrum/Kanban to address the full, end-to-end delivery lifecycle from project initiation all the way to delivering the solution to its end users and beyond

FULL LIFECYCLE

Next Release

Inception Development Release

Envision and plan Incrementally build a consumable solution Release solution

ROLES

PRIMARY ROLES

Team Lead Product Owner

TEAM ROLES

Team Member Architecture Owner

Stakeholder

INCEPTION• User stories• Business rules• Non-functional requirements• Logical Data Model• UX wireframes• UI mockups prototype• Acceptance criteria• Joint application requirements sessions• Architecture and risks

BacklogPlanning Iterations Critical

High

Normal

Low

BACKLOG

Backlog

Critical

High

Normal

Low

New workitems areadded continuously

Daily Work

Workitems are pulledwhen capacity is available

DEVELOPMENT: SCRUM+

DEVELOPMENT: KANBAN+

DEVELOPMENT DAILY• Daily standup• Circulate written requirements and design• Estimate expected/worst hours• Stay lean: build what is needed today• TDD• Gitflow• Code reviews• CI stays green• Demo continuously

RELEASE• Backup existing solution• Deploy new solution• Deployment testing• Data migration• Pilot/Beta testing• Documentation update• Stakeholder education & feedback