A bed of roses

At the moment it's roadmaps.  I found the best for 'Train Sim World 2'!  It gives a really detailed list of what new trains and routes are due to be released, and the patches and what they're going to fix.  It's more detailed than we want but it does give the 'customer' view.  I think that's really the key here - working out what the different audiences are and what they need to see.

I also got slightly embroiled in prioritisation methods, and nearly disappeared into a rabbit hole that required us to detail OKRs, MoSCoW, and RICE.  I managed to keep my practical head on, though.  The OKRs are pretty much sorted with org and dept strategy.  MoSCoW and RICE are useful tools - where there's a conflict.  If we can see the right order, we don't need to worry too much about being scientific.

On the other hand, there is talk of resurrecting the concept of project 'size' *buries head in hands*.  We've been round that loop so many times...  But that also means we have lots of stuff to look back on and, possibly, dust off.  Because we do now have the people to make it happen.  And it's probably pretty easy to identify a project's 'size' without resorting to tables and formulae.  Curriculum Management is clearly large (you might even say humungous) because it's expensive, involves lots of people, requires culture change and is very, VERY visible.  Study Abroad is medium because it involves fewer people but is a very important piece of work.  I'm struggling to think of a 'small' - all of what we do is important from a reputational perspective, if nothing else.

So, maybe we only need small and large?  Just medium and large sounds odd...

Anyway, enough work-geekery :D  See you next week, DW!