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:
In June 2012 I replied to a post on a local Freecycle mailing list offering “hundreds of metal CDs”. When I got them home I’d been very kindly given around 195 (give or take a few). I’ve been more or less reviewing one CD a week ever since on my 195 metal CDs blog.
Some weeks are easier than others for finding the time to write a review. For albums that I particularly like I sometimes cheekily listen to it for a further week before scribbling down my thoughts.
I’ve been blogging now for well over ten years, so why has it only just occurred to me to get at least one week ahead of myself and review an album at least a week or two in advance?!
That would clearly take the pressure off. I could write the review whenever I wanted and schedule it for the appropriate Monday. As you can see from this image I plan my reviews well in advance using Trello:
So that’s what I’ve done this afternoon. I had a run of albums by Italian black/gothic metal band Opera IX scheduled for the next few weeks so I’ve just grouped them and reviewed them in chronological order this afternoon.
It will be interesting to see what difference this makes in terms of finding the time to review the albums and how much I enjoy them given that the pressure has been relieved a little.
Yesterday afternoon and this morning Reuben, Joshua and I have been making a “nee naw car” from the box that Isaac’s new Baby Jogger City Classic pushchair arrived in. Here is the almost-finished article.
The car was made from a Baby Jogger City Classic pushchair box, painted with Wickes one coat matt emulsion “Victorian Red” (the same colour as our kitchen and dining room).
The word “FIRE” was cut out from a roll of big labels (a little larger than A5) that we bought at the Borders Scrap Store in Selkirk years ago. As were the lights and radiator.
The ladder was made from cardboard from the box.
The wheels were made using Microsoft Publisher 2010 and coloured in by Reuben and Joshua. The Pontypandy Fire and Rescue Service badge was sourced on the Web and printed out on our laser printer. I was going to draw it but was being climbed on at the time.
Close-up of front
Close-up of the front of the new, homemade Nee Naw Car (featuring Fireman Sam and Firefighters Reuben and Joshua).
The blue flashing light is made from a Robinson’s Fruit and Barley bottle cut off at the bottom and stuffed with blue tissue paper, with black gaffa tape at the bottom to cover the jagged plastic from my hacking attempt at cleanly cutting it off with a pair of kitchen scissors.
The number plate is “RJ 999” for Reuben and Joshua. The radiator and headlights were also coloured-in by Reuben and Joshua.
Improvements to be made based mostly on consumer feedback and rigorous user-testing:
Strengthen area beneath windscreen as Reuben and Joshua hang on to it to climb in and out.
Add a second steering wheel (to stop the fights about who is driving).
Improve the inside of the windscreen / dashboard.
Add silver gaffa tape… not necessarily an improvement, more a request from Reuben and Joshua.
The photograph above, taken a couple of months ago, shows the planning board in our office — an information radiator — that shows us at a glance how many tasks are left to do, what’s currently being worked on, what’s in testing, what’s done and (unlike, I would guess, most other Agile boards) what we’re waiting for.