The document outlines a stepwise approach to implementing Agile/DSDM processes in an organization. It recommends starting with the foundations like PRINCE2 project management. The next steps involve gradually introducing more Agile elements: user involvement, shorter iterative projects, quality processes, and training. The goal is to eventually make Agile/DSDM processes a natural part of the organizational culture. It cautions not to oversell Agile and to go at the pace that is right for each organization.
2. www.dsdm.org
History of DSDM
• Evolved from RAD
• Created
Collaboratively by
practitioners for
practitioners
• DSDM Consortium not
for Profit
• Agile Manifesto
Founder
• 1995 DSDM V1
• 2003 DSDM V4.2
• 2007 DSDM Atern
• 2011 Agile PM
6. www.dsdm.orgwww.dsdm.org
Development is as Easy as ABC!
Create
Specification
Specificati
on
Choose Vendor Throw Over the Wall
Receive Perfect System
http://www.youtube.com/watch?v=obrKNdv6RH8
7. www.dsdm.orgwww.dsdm.org
WHAT IS AGILE?
• AGILE MANIFESTO
– Individuals and interactions
over processes and tools
(3)
– Customer collaboration
over contract negotiation
– Working software over
comprehensive
documentation(4)
– Responding to change
over following a plan
- Start Simple but know your goal
- Communicate Feedback Continuously
- Respond to changing environment
DSDM
SCRUM
KANBAN
LEAN
11. www.dsdm.orgwww.dsdm.org
Agile Project Management
•Will Proposed Solution Satisfy?
•DSDM Suitable / Risks?
•Possible technical solutions
•Time / cost estimates
•Scope / Prioritise Requirements
•Outline Development
•Identify User Classes
•Risks
•Technical Basis
•Demonstrate / Agree Functionality
•Record Non-Functional Requirements
•Build in non-functional
requirements
•Make fit for delivery
•Deliver System
•Train Users
•Operational Handover
•Determine future requirements
12. www.dsdm.org
DSDM Teams and Roles
• Orange – Business Roles
• Blue – Project Roles
• Green – Technical Development
Roles
• One role does not necessarily
mean one person
• One role may be split between two
or more people
64
14. www.dsdm.org
A step at a time
4
• Step 2a - User Involvement
• Step 2b - Shorter Projects /
incremental delivery
• Step 2c - Involve Quality
• Step 2d - Iterative development
pilots
• Step 2e - general training and
accreditation
• Step 3 - DSDM processes part of
culture
15. www.dsdm.org
A step at a time
4
• Step 2a - User Involvement
• Step 2b - Shorter Projects /
incremental delivery
• Step 2c - Involve Quality
• Step 2d - Iterative development
pilots
• Step 2e - general training and
accreditation
• Step 3 - DSDM processes part of
culture
16. www.dsdm.org
A step at a time
4
• Step 2a - User Involvement
• Step 2b - Shorter Projects /
incremental delivery
• Step 2c - Involve Quality
• Step 2d - Iterative development
pilots
• Step 2e - general training and
accreditation
• Step 3 - DSDM processes part of
culture
17. www.dsdm.org
A step at a time
4
• Step 2a - User Involvement
• Step 2b - Shorter Projects /
incremental delivery
• Step 2c - Involve Quality
• Step 2d - Iterative development
pilots
• Step 2e - general training and
accreditation
• Step 3 - DSDM processes part of
culture "DSDM actually gives you more
quality doesn't it!"
18. www.dsdm.org
A step at a time
4
• Step 2a - User Involvement
• Step 2b - Shorter Projects /
incremental delivery
• Step 2c - Involve Quality
• Step 2d - Iterative development
pilots
• Step 2e - general training and
accreditation
• Step 3 - DSDM processes part of
culture
19. www.dsdm.org
A step at a time
4
• Step 2a - User Involvement
• Step 2b - Shorter Projects /
incremental delivery
• Step 2c - Involve Quality
• Step 2d - Iterative development
pilots
• Step 2e - general training and
accreditation
• Step 3 - DSDM processes part of
culture
20. www.dsdm.org
Summary
• Have your vision
• Set the foundations
• Plan the steps
• Stepwise improvement
• Don't oversell agile
• www.dsdm.org
Ask audience experiences of Agile Myths
- 5 minutes
5 minutes
But surely offshore development makes life easy
Experiment on stage
All we have to do is:
Say WHAT we want
Choose WHO will do it for us
Hand it over to them
And we get what we wanted!
We introduce complexity at the start
We do not communicate and therefore iterate / feedback
Small assumptions lead to chaos
Then we get the wrong answer
5 minutes
Agile 10 years old
DSDM since 94
Real message is iterate/feedback from simplicity to create correct answer
SCRUM; LEAN; KANBAN; DSDM
1. Explain Lifecycle and iteration
2. Explain Processes
Explain Project; solution; other
Explain that it can easily scale (whiteboard how)
Explain empowerment and letting the team get on with things - self organising within boundaries
Page: 37