Project Methodologies - Not A Silver Bullet

Over the last few years there has been muchthreatening the complete project ( or even
emphasis on project management methodologiesprogramme ). This isn't to say that software project
such as Prince2. The introduction and roll out of thesemanagers need to know how to programme for
structured techniques helps set expectationsexample; but if for instance they don't understand
amongst the wider community about what thethe difference between representative and
project manager will do, and the manner in whichunrepresentative test harnesses for unit testing then
communication will take place.the system integration could be appallingpainful.
For instance the project stakeholders will not beThe team obviously have a vital role to play but the
surprised to see a project manager having a set ofteam can feel inhibited from telling their boss that he
documents includingor she is wrong. Even if the message is delivered it
¨ Business Case,can be discounted, or confused with a lack of
¨ Project Initiation Document,discipline. Independents can play a valuable role
¨ Product flow chartuncovering these and other challenges that the
¨ Product descriptionsproject may face.
¨ Highlight reportsQuite apart from the challenges that arise from the
¨ Risk Log.need to define management deliverables there are
The development of the standard processes isoften serious issues with the estimates and
obviously helpful as these, together with standardassumptions made as part of specialist deliverables
templates for the documents used, help manythat are to be delivered through the project. These
project issues to be anticipated and worked around.assumptions are of critical significance to the whole
In order to be credible the methodologies need toproject and often need a detailed technical and
cope with the most complex situations (e.g. Buildingbusiness review to bring them to light. The technical
the Olympic venues for London 2012)staff within a project may not be aware their
The size and scope of some of the methods caninterpretation of the business requirements has
give rise to serious issues as the project managerembedded unsafe assumptions.
seeks to decide which elements from theExamples of some unsafe assumptions that the
methodology can be treated as optional and tries toauthor has uncovered during past project reviews
downscale the approach to smaller projects. The levelare:
of detail or the number of stages of plans is all a¨ Expecting the client to synchronize identifiers
matter ofjudgement, as is the appropriatebetween systems on a regular basis.
membership of a supervisory board within a Prince2¨ Misunderstanding the speed of response
approach. Sometimes this reduction can be triggeredrequired to support call centre staff when designing a
by external time commercial and time pressures withcomplex integration to back office systems.
people asking why you don't stop creatingProject reviews
documents and get the team to concentrate onMore recently much attention has been given to
actually producing something; but it can also be'gateway reviews'. In the UK the OGC have published
decided by the personnel available to provide thea gateway review process that organisations may
supervisory roles and structures envisaged.have adopted. It is worth recognising, however, what
The project manager and the teamthese reviews do well, and what they omit. The
The role of the project manager and the team inreviews focus on 'buy' rather than 'build', and they
making sure that the documents and controls are ofask whether the project management controls are
appropriate quality can also sometimes be givenworking and the project will deliver the benefits to its
insufficient attention.stakeholder community. The reviews do NOT focus
¨ It is difficult to know when a risk log isor consider which assumptions may make the project
complete. This log is sometimes compiled usingoutputs meaningless. This is assumed to be happening
brainstorming or other collaborative techniques, butas part of the project management process. A
the obvious need to have few un-mitigated risks canreview that actually looks at the real deliverables can
lead to 'game playing'.be valuable to make sure that the project will still
¨ Deciding on the work breakdown structuredeliver something.
and the product interdependencies can be reallyConclusion
challenging.So whilst project management methodology is rightly
As project methodologies have become moreseen as a means to avoid some of the more obvious
prevalent, the author has noticed a tendency for thepitfalls that have been seen in projects, practioners
subject knowledge of project managers to beshould be wary of assuming that the adoption of a
treated by some as less important. The projectparticular methodology will be a miracle cure for all
manager may be more of a generalist whoprojects.
understands the process of project managementOnce the views of the team and other stakeholders
rather than an individual who has experience of thehave been gathered it is worth getting independent
particular challenges arising from the activities involvedreview to assess your plan and the assumptions.
( e.g. software development, building an airport ).Periodic refresh as the project unfolds can be
There is little substitute for the experience thatworthwhile, depending on the extent of change
allows a project manager to judge when a small issueexperienced during the delivery period.
is one that will remain small or could grow into a issue