Chapter 2 Choosing DSDM as your Agile Approach Flashcards
What are the four DSDM Agile manifesto values
1) Individuals and interactions over processes and tools
2) Working software over comprehensive documentation
3) Customer collaboration over contract negotiation
4) Responding to change over following a plan
What is DSDM’s assumption regarding the 80/20 rules
DSDM assumes at 80% of the value of a solution can be delivered with 20% of the effort it would take to deliver the total solution
How DSDM Addresses Key Project Problems?
DSDM requires basic foundations for the project to be agreed at an early stage. This allows businesses to understand the scope and the way it will be created before development starts. This reduces the likelihood of nasty surprises on DSDM projects. (also agreeing the basics is good for orgs with heavy governance or architectural standards
Discuss 9 ways DSDM Differ From Most Agile Approaches?
1) Ineffective communication: DSDM’s emphasis on human interaction (e.g. through the use of workshops), visualisation (e.g. through the use of modelling, prototyping and iterative development) and clearly defined roles is at the heart of excellent project communication.
2) Late delivery: DSDM focuses on delivering on time. The vast majority of the benefit of a solution can still be gained from a solution with the less important features left out.
3) The delivered solution does not meet the business needs: DSDM encourages collaboration and enable visual and verbal communication. Embrace change and new ideas
4) Building the right thing – the business changing their mind: DSDM enables change through iterative development, with regular reviews
5) Unused features: helping the business to prioritise its needs as understanding of the detail grows
6) Delayed or late ROI: DSDM uses incremental delivery
7) Over-engineering: DSDM is a pragmatic approach which focuses on the real business need in order to dissuade a team from being tempted to add the final extras which the business could live without. Prioritisation ensures the whole team are clear about the relative importance of the work to be done and that low value ‘polishing’ of the solution does not impact deadlines and compromise ROI.
8) Fragile Agile: DSDM helps here by placing the right Agile concepts and constructs in a structured and controlled framework that enables a project to respond to change and stay in control,
9) Waterfall dressed up as Agile:The most common example is where iterative and incremental timeboxed development follows on from traditional analysis and design steps in the waterfall and is followed by a traditional testing step
