Showing posts with label projects. Show all posts
Showing posts with label projects. Show all posts

Sunday, June 26, 2022

Barriers to project success - an exercise in found data

I love 'found data'. It's the inadvertent information that gets shared and can reveal something deeper about the world we live in. My annual Christmas card audits (the ACCAs) are an example. It's almost as good as 'found art'.

Some art I found previously...

This found data was from a project management course that I completed this month (June 2022). There were nine students on the course, which was conducted remotely over five non-consecutive days. Seven students were from the NHS, one was from a university and the ninth worked for a public sector body. The project management programme was PRINCE2, which is a methodology that has been widely taught (if not widely followed) for a number of years.

PRINCE2 has seven key principles that every project conducted in line with PRINCE2 is meant to adhere to. They are non-optional. The seven principles are:

  1. Projects must have a 'continued business justification' - they need to be checked regularly to see if they are still viable and will provide a useful product and value for money
  2. Projects should be informed by experience, incorporating lessons from other projects and ensuring lessons are learned during the life cycle of the project
  3. Projects should have 'defined roles and responsibilties' in the project team 
  4. Projects should be 'managed in stages' which includes a clear process for starting and ending projects
  5. Projects should also be 'managed by exception', so higher levels of management are only really involved if circumstances change and projects are unable to go as planned
  6. Projects should 'focus on products' - the result or outcome of the project
  7. And finally, project management and design should be tailoured to fit the context of the project

The person leading the course used an interesting approach to get us to discuss (and learn!) the seven principles. He gave all of us seven votes and asked us which of the seven principles we thought were least likely to be adhered to in our workplace. We could assign as many of our votes as we liked to any of the principles, depending how difficult it would be to adhere to particular principles in our workplaces. That was 63 votes in total.

Now, bearing in mind who was on the course, I found the results really interesting.

Top of the pile, with 20 votes - almost a third of all the votes we were allowed - was the first principle: continued business justification. So, basically, the feeling was that once a project got started it was never checked to see if it was still needed. It would just carry on, regardless. It didn't matter if the landscape had changed, new evidence had emerged, technology had advanced or whatever. There was no stopping it. Projects might even get started without a business justification in the first place. It was somebody's pet idea and if that person had enough clout they could make a project happen.

Next in the pile, with 14 votes - which is the rquivalent of two votes from everyone on average - was 'defined roles and responsibilities'. When we discussed this, it was either people not knowing what they were meant to do, people higher up in the system micromanaging and interfering, or trying to get support from the 'not-my-job' brigade who just refuse to undertake roles in projects. 

Both 'focus on products' and 'manage by stages' earned 9 votes each. The focus of projects is often on the process rather than the outcome, and everyone seemed to have a story about a project that started without a defined intended outcome. Manage by stages also seemed to be a difficult one because projects get launched with very little planning and without a step-by-step plan for product delivery. 

Tailouring and learning from experience both earned 7 votes. There is common phrase about reinventing wheels that crops up regularly. I've noticed a reluctance of people in the NHS to learn from other organisations, or even from other teams in their own organisatrion. The default position is that whatever worked up the road couldn't possibly work here because our job doing the same thing is actually so much harder and more complex! It's nonsense, but it's hard to argue with people who find that belief convenient for several reasons.

And then, finally, 'manage by exception' got 4 votes. That seems to indicate that people do bring problems to those above them in the organisations. Mainly that's because they will have run out of money and are asking for more (he says, slightly cynically).

Mathematically adept readers may have noticed that the total adds up to more than 63 votes, so some people obviously got carried away and lost count of their votes. But the general trend feels true to the discussions we subsequently had.

I'm not arguing for the reliability of found data, and I recognise this is a very small sample size. But it does capture the perceptions of people about the barriers to running projects according to an established methodology. And actually, this kind of subconscious sharing of information may be more reliable than if people were asked under formal conditions to give an opinion. This is what people really think about trying to make projects work in these organisations. 

Thursday, July 14, 2011

Building a model railway part 1

Recently I got my old model railway baseboard out from the cupboard where it had lain dormant since about 2004. I've always liked model trains and in the past 2 weeks the bug has bitten deep.

I decided to take up some of the track and reformat the layout. The orginal lay out looked like this - a loop and two sidings.


It was pretty basic and so I decided I wanted to add in another siding and maybe a reverse siding (or two) to lead to an engine shed.

There was a problem, though. When I laid this track I had made the passing loop far wider than it needed to be by adding in some non-standard pieces of track. Unfortunately that threw off my intended new siding so that it ran at a crazy non-parallel angle.


The non-standard add-in piece can be seen in this photo. Removing it also meant I could fit in an extra siding without losing too much track off the top siding.
So up came the track! And down went new track after painting on a roadbed for it.


You can see how the loop track is much closer together, leaving room for two extra sets of points.

The small divergence at the bottom of the picture will eventually be inside an engine shed. I have put in a loop of wiring to power the track from both ends, which means the reverse siding has power. (Bit of trial and error but it works.)

There are still issues with this layout. I'd like to run a platform on the left-hand side, but that track isn't straight on the baseboard (it's the last remaining original length of track from the old lay-out). I have a growing urge to take it all up and relay the lot of it, with proper measuring this time.

I could also shorten the loop and add a few valuable centimetres to the second siding. This is important because the theme of the railway is going to be a railway heritage centre, and I need extra space to store rolling stock.

Speaking of which, now I've bought all the track I felt it was time to treat myself to something new to go on it. I already had 11 wagons and 2 locos from when I first put it together (mostly gifts from my Dad, it has to be said). But today I went and bought myself a crane train from the Hornby Railroad range. HR is the cheaper Hornby stuff made using older moulds, but that kind of fits the bill for a heritage railway! The crane works and I'm very happy with it.


There's plenty of work still to do and I'll be posting updates!