21
DISCIPLINED AGILE DELIVERY

Why AgileEngine dumped Scrum for Disciplined Agile Delivery

Embed Size (px)

Citation preview

Page 1: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

DISCIPLINED AGILE DELIVERY

Page 2: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

SCRUM IN A PERFECT WORLD

Page 3: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

REWRITE STORY

Page 4: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

LET’S DO THIS!

Page 5: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

How did it go?

Page 6: Why AgileEngine dumped Scrum for Disciplined Agile Delivery
Page 7: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

Mom, but we followed Scrum!

Why did we still fail?

Page 8: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

REAL WORLD

Page 9: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

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

Page 10: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

Scrum/Kanban are great for “how”.

But, they do not address “what”.

Page 11: Why AgileEngine dumped Scrum for Disciplined Agile Delivery
Page 12: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

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

Page 13: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

FULL LIFECYCLE

Next Release

Inception Development Release

Envision and plan Incrementally build a consumable solution Release solution

Page 14: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

ROLES

PRIMARY ROLES

Team Lead Product Owner

TEAM ROLES

Team Member Architecture Owner

Stakeholder

Page 15: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

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

Page 16: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

BACKLOG

Backlog

Critical

High

Normal

Low

New workitems areadded continuously

Daily Work

Workitems are pulledwhen capacity is available

Page 17: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

DEVELOPMENT: SCRUM+

Page 18: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

DEVELOPMENT: KANBAN+

Page 19: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

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

Page 20: Why AgileEngine dumped Scrum for Disciplined Agile Delivery

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

Page 21: Why AgileEngine dumped Scrum for Disciplined Agile Delivery