Simon Naylor, head of consumer and industrial project management with Cambridge Consultants, said a project manager’s involvement can start at many points – from a blank sheet of paper to a mature design. “But what determines the success, or otherwise, of your project frequently isn’t the technical side,” he warned. “It often comes down to the project’s stakeholders, its leadership team and your ability to control things.”
One of the first things a project manager needs to understand is just who has an interest. “There are always stakeholders external to the project team,” he said. “When I first discuss a project, I hope there are two or three key stakeholders and there is access to them. Fewer than this and the chances are there are stakeholders we don’t know about. In this situation, the project is destined for an unpleasant realignment when missing stakeholders reveal themselves.”
Too many, Naylor added, and you could be in for a difficult time. “You could end up with something ‘designed by committee’ because you can’t make the necessary decisions.”
You should also hope that stakeholders talk to each other and have complementary views and aims. And one should have the authority to make quick and lasting decisions.
Before the project kicks off, talk to the stakeholders, understand who they are and what’s driving their involvement. “If there’s uncertainty, that will be an area of risk and it’s worth investing time to work out the relationships.
“As a project manager, you want to have control over what you’re promising to deliver. The worst case is when there are fixed timescales, development effort and deliverables – for the typical project, that’s a ‘car crash’ waiting to happen.”
But a project manager doesn’t have to be responsible for everything. “They will be responsible for the timescales,” Naylor pointed out, “and the deliverables. But, ideally, they will have a ‘partner in crime’ – the technical authority or lead – who will be responsible for the technical stuff.”
His analogy is a rally car. The project manager is the driver, with the technical authority navigating. “Between you, you work out the best way of getting to where you need to be.”
Another area of risk is a fixed specification. “Specs are things that are hard to make 100% complete and are prone to interpretation differences. It’s an important document and something you need the ability to work on.
“Think of it as a discussion document; one of its purposes is to extract information from stakeholders and to then get rid of possible misunderstandings.”
If you’re handed a complete spec, he added, it might be OK. “But make sure you have control over timescales and costs,” he advised. “However, when things are written down and you weren’t involved, that represents a danger area – you won’t understand why they were written down. In reality, the world is grey scale, rather than black and white, so if you have worked on the spec, you will have a better understanding of what’s really needed.”
Any project leadership team worth its salt should identify the high risk areas. “Pick them out and prototype them,” Naylor said, “or check them against the Laws of Physics to convince yourself the project can proceed.”
There are three important elements to project definition – commercial, technical and management. “All three should be represented,” Naylor asserted. “Commercial people want to sell something, technical people push functionality, while the project manager wants to deliver something. There will always be tension between them.”
Project management triangle
Naylor said there are three elements to project management and these can be considered as a triangle. “They are cost, deliverables and timescales,” he explained. “You can’t have all three; there has to be room for manoeuvre. Quality is a further issue, particularly if you’re developing a medical device. Then, the area of the triangle will become larger. You have to be able to trade these elements off against each other; if they’re fixed, then that’s a big risk.”
Project managers have to perform this trade-off constantly, Naylor continued. “If not, then it will be hard to deliver the project. But the priority at any point depends what’s driving the stakeholders. You might need to show something at an exhibition; that’s a fixed date, so development effort or functionality will need to be flexible. Remember that things change and the project will need continual discussion.”
0 comments:
Post a Comment