Tag Archives: DSDM

Book review: Agile Project Management and Scrum v2

front-cover-webIn two of my previous posts I wrote about DSDM and UX Design and Agile Project Management and Scrum v2. This is another little book in the same style. And this booklet too can be read as an addendum to DSDM’s Agile Project Management Framework.

Andrew Craddock is the author of the book ‘Agile Project Management and Scrum v2‘.

The booklet starts with a comprehensive overview of Scrum based on the Scrum guide 2013 and an explanation of the Agile manifesto.

Next we get an overview the combined AgilePM / Scrum process framework. The project delivery context is based on AgilePM and the evolutionary development context is pure Scrum.

In this combined framework we see the following changes / additions in comparison with the original AgilePM framework:


AgilePM AgilePM/Scrum
Process Evolutionary Development Scrum Development
Product Prioritized Requirements List Product Product Backlog


Timebox Plan and Timebox Review Record Sprint Goal, Sprint Backlog and Sprint Review Record
Roles adding the PO, SM roles

An enhanced Scrum two-week Sprint contains some minor embellishments to the standard Sprint:

  • In comparison with a standard Sprint we now see a split in two parts: Refinement (7 days) and Consolidation (2 days).
  • Within the Consolidation part we see a Consolidation Scrum to confirm progress to date and to explain what will be ‘Done’ by the end of the Sprint.

A new event, the Project Planning Event, is added. This event takes place at the boundary of timeboxes and can be used, by project stakeholders, to influence the the work of the Scrum Team without compromising the way Scrum is used.


All roles are explained within this combined framework with special attention for the Product Owner role including relationships and interactions with the Technical Coordinator, PM, Business Visionary, Technical and Business Advisors and the Development Team.

Final paragraphs explain the usage of multiple Scrum Teams, Regulatory, and financial governance, the usage of Barry Boehm’s Cone of Uncertainty and some optional techniques (MoSCoW prioritisation, Facilitated Workshops and Modelling).

Conclusion: For those who are using AgilePM in combination with Scrum this is a must read. It gives a nice overview of the changes and a good explanation of the PO role including all relationships and interactions.

To order: Agile Project Management and Scrum v2

This is the last post in a series of three. DSDM and UX design was the first and Agile risk management and DSDM the second.

Review: Agile Risk Management and DSDM

riskIn one of my previous posts I wrote about DSDM and UX Design. This is another little book in the same style. And this booklet too can be read as an addendum to DSDM’s Agile Project Management Framework or separately to enlarge your knowledge about risk management in an agile context.

Talking about a little book, in the foreword you can find a reference to the famous episode, The Protégé, of the programme Seinfeld. It’s about a 700 page risk management book. Look for yourself and have fun.

Alan Moran is the author of the book “Agile Risk Management and DSDM“. He did a great job explaining risk management in an agile environment.

Agile risk management considers, like PRINCE2, not only treats (negative risks) but also opportunities (positive risks) and is concerned with the identification, assessment, prioritization, treatment and monitoring of project risks.

As a starting point for risk identification the following generic risk drivers are high lighted: requirements risk, technical risk, schedule risk, project (approach) risk, supplier risk and people risk. These can be highlighted in the enterprise and project risk driver maps.

In a next paragraph the agile risk management process is explained. It starts with the understanding of the project objectives, context and risk environment, risk scoping (identification of risk drivers and appetite), risk tailoring (embedding risk management in agile process), risk management (identify, analyse, manage and monitor) resulting risk optimized agile process.

Agile risk management is founded on three principles: flow (ensure that events do not inhibit or delay progress), balance (deliver the same reward with less risk) and transparancy (make visible and accessible all risk artefacts). In the book you will get a mapping to the eight DSDM principles.

In the following paragraphs you get an explanation who (DSDM role) performs which risk management activities and how you have to make amendments to the practice of DSDM to cover the overall project risks.

The author explains several risk tools: enterprise and project risk driver maps, the risk log (register), risk reward prioritization matrix, the risk rainbow mapping of risk exposure to risk response strategies (when to apply which risk response strategy), risk tagging (identify the agile (DSDM) practice(s) to mitigate the risk), risk modified timebox plan, risk modified team board, risk burndown chart, risk walling (making visible the project risk driver map, risk log, risk modified timebox plan or team board, risk burndown chart). See the attached figure for some examples.

Dia1The final chapter explains the social and cultural aspects. A common typology of risk stances is: risk-averse, risk-seeking, risk-tolerant and risk-neutral. Individuals tend to be influenced by conscious, subconscious and affective factors.

In summary DSDM enables a new perspective on risk management by injecting elements of cadence (e.g. performing risk analysis at the start of each timebox), transparancy (e.g. using risk modified team boards including risk burndown charts) and agility (e.g. by using risk tagging). 

Conclusion. Many people will say we are using agile techniques so no need to have a separate risk management strategy. This book gives a good approach to cope with risk management within an agile environment. You get an overview of risk management and how it can be tailored and used in a DSDM environment and it can be applied within other agile frameworks too.

To order: Agile risk Management and DSDM

This is the second post in a series of three. DSDM and UX design was the first and Agile Project Management and Scrum v2 will follow

Review: DSDM and UX Design

dsdm_and_ux_design_pocket_bookHelen Sharp, Laura Plonka, Peggy Gregory, Katie Taylor and Mike Rowlands wrote a nice little booklet DSDM And UX Design. The book gives you an under standing of User eXperience (UX) Design and how it fits in DSDM’s Agile Project Framework. Even if you don’t use DSDM’s framework this booklet is worthwhile reading to get a better understanding of UX Design.

Every product that is used by someone has a user experience. Think e.g. about newspapers, ketchup bottles, administration systems, apps, portals, etc. In practice, UX Design involves a wide range of activities, including: user research, interaction design, user interface design, information architecture, user evaluations, and delivering business value.

UX Design uses the concepts of usability and user experience goals. When looking at usability you have to take the following goals into account: effectiveness, efficiency, safety, utility, learnability and memorability. User experience covers a wide range of goals including: satisfying, enjoyable, fun, entertaining, helpful, motivating, aesthetically pleasing, supportive of creativity, rewarding and emotionally fulfilling.

In DSDM there is no explicit mention of UX Design but it can be easily embedded (as it can with other agile frameworks). The booklet shows how it fits during Feasibility and Foundations as well as during Evolutionary Development. Key is that you should avoid producing pixel-perfect designs too early. Due to prioritization not every feature or user story will be developed. A common integration framework suggests that UX Designers work one timebox ahead of developers. Looking at the DSDM roles and responsibilities the authors show that all roles will have some UX Design responsibilities and make sure that UX Designers and the DSDM role players will put conscious effort into the collaboration (mutual awareness, negotiating progress, engaging with each other, expectations about acceptable behavior.

The last part of the book talks about challenges that arise and how to improve these in the areas of communication and collaboration, how much precision is needed in upfront design, design documentation and how and when to conduct user evaluations.

Conclusion: A good booklet to get a basic understanding of UX Design. If you are using DSDM AgilePF you will get some additional information how to fit UX Design into the framework. If you are using other agile frameworks most of the topics mentioned are still worthwhile reading.

To order: DSDM and UX Design

This is the first post in a series of three. Agile Risk Management and DSDM and Agile Project Management and Scrum v2 will follow