Wednesday, 12 August 2015

Prioritisation and a joker

We had a SSB this week - Service Strategy Board, and high on the agenda was how we prioritise projects. What factors to take into account, what is the relative priority of our existing projects, and where do new ones fit. A lot of preliminary work has already been done, and we have a priority list already - based on a number of criteria, including whether something is statutory or strategic, and what is its reach and impact. Whether they are the right criteria is of course still up for discussion. I'd like to see more account taken of innovation and improving the user experience,  but there is still some more work to do.  I was amused to see that there was the provision for a wildcard, or joker, which I was told I could only use once ;-)  We also looked at the large pieces of work we do in the department that aren't classed as projects, and how we prioritise them. Perhaps the first question might be, why aren't they classed as projects? In some organisations any piece of work that takes more than a certain number of days is classed as a project. This work is linked to discussions that have been taking place on how we handle the workload in the development team and how that is prioritised.

Then yesterday we had a internal discussion following the workshop a couple of weeks ago on Digital Transformation, and how some of the work we want to do in this area sits with the priorities work. Given that what we want to do by setting up some sort of Digital and Innovation team is work in a Mode 2 way (if you're talking Biomodal working), does this sit completely outside this work?  We also looked at some of the work that we might do under the umbrella "Digital transformation", and the resources we might need to do it.

All matters for discussion over the coming weeks.

No comments: