This week I’ve started a project to restore a very precious gift, from a very precious period of my life, my Moulinex blender lamp.
In the autumn of 1996, I moved into Flat 3, Lansdowne Centre, Law Street, Bermondsey. At the time I thought this would be a sojourn before moving in with a friend but I settled in quickly and it remains today one of the best places I’ve ever lived.
One misunderstanding that I’ve encountered a lot over the last couple of years in relation to DSDM agile project management is in the area of prioritisation, and in particular how MoSCoW prioritisation works. In this post I hope to make things a little clearer
One of the things that we’re taught when learning the DSDM agile project management framework is that, unlike traditional project management approaches where the project manager manages the team on a day-to-day basis, in DSDM the project manager manages by exception.
Just over a year ago I was sitting in a classroom learning about and sitting two exams on DSDM Atern Agile project management.
Something that I wished had been available at the time was some kind of cheat sheet that broke down each of the DSDM phases (pre-project, feasibility, foundations, exploration, engineering, deployment, and post-project), indicated which products (usually documents) belonged to which phase, and who was involved in the creation of each product.
I couldn’t find anything suitable, so I created my own, pulling out all that information from appendix C of the DSDM Agile Project Management Handbook into a RACI matrix.
Over the last year I’ve found this to be a really useful resource. I have it printed out on A3 and stuck on the wall next to my desk; I refer to it a lot.
You’re welcome to use it and adapt it for your own needs: