Contingent Project Management - A Definition

In an IT systems context, contingent projectensure that the appropriate processes are selected
management ("CPM") is the ability to select anfor a project and that they are applied judiciously so
appropriate methodology to apply to and successfullythat the project is not strangled by administration
deliver a project, tuning the method as the projectand red-tape.
proceeds. 'Contingent Leadership Style' is analogous.This choking of projects by heavy methods was
Wikipedia (Fiedler) provides an explanation ofobserved by the author in an investment bank. The
contingent leadership.project managers running a large number of smaller
Yes, a project manager can have a contingentprojects were unable to meet the centralised project
leadership style, but may not have a contingentreporting requirements imposed on them, leading to
project management approach.frustration in the managers, frustration in the
Let us look at a range of project managementprogramme office, and frustration in and with the
framework processes:'methodology police'. The recommended solution was
Waterfall (gather requirements, design, build, test,to
deliver, train) - the 'traditional' way of building- Prioritise the projects according to risk (measured
systems. This worked well for systems where theon several dimensions), report project status on an
rate of business and technology change was low,'exceptions' basis, and tune reporting frequency to
having grown out of engineering and construction. Itproject risk.
still works well in a construction (civil engineering)This levelled the project managers' workload, and the
context, where generally, the rate of technologycentralised need for control of risk and comfort.
change is low. Requirements of a building may changeSo, what of contingent project management?
during construction, but the rate of scope creep isIt is clear that a significant degree of experience is
still low as compared with many IT projects. In thenecessary to be able to select the appropriate
right circumstances, it can still work well with ITmethodology for a project, and the programme
projects.board is not always best placed to decide for
Agile methods (gather and prioritise requirements,reasons mentioned earlier - investment and political
design a prototype, test, deliver, re-cycle - design,capital for example.
build, test, deliver, train and go live). On the scale ofAn effective project manager will have
low risk/low complexity to high risk/high complexity- the wisdom and experience to select the correct
some of the methodologies would be: XP, Scrum,tool for the job based on his or her perception of
DSDM ®, RUP ®. Note that risk andthe risk profile; the ability to persuade the
complexity do not always equate - some lowprogramme board or sponsor of the relevance of the
complexity systems can have profound organisationalmethodology and the basis of selection; worked with
risk associated with them.a number of methodologies experience enabling the
Prince ® could be used in either of these'heavy' or 'light' touch application of a methodology;
contexts for governance of the project on a wideran innate sense of the risks and their relative
organisational scale, or locally on a smaller scale.salience, meaning that a focus is developed and
Indeed, the advent of Prince2 moved themaintained on the things that matter; finally, the
methodology into a wider non-IT specific context.ability to dynamically tune the methodology to
Agile methodologies are most appropriate forcircumstances without loss of control (finance,
example where requirements are unclear at thetimeline and quality), as the 'things that matter'
outset, and/or the technology is new or beingchange
stretched, and/or a new business model is beingDynamic tuning means applying the tool judiciously -
adopted (to name just a few reasons). The range ofsome projects may require very high levels of
Agile methods also relate to scale of project andstakeholder communication, others will have to be
team size.highly focused on technology/ performance and
Sophisticated organisations may have their own 'pet'proof of concept, others may have political
methodology, maybe having invested heavilygovernance issues, new or immature business
(financially, managerially and politically) in developingmodels, and so on. Some projects, of course, will
their way of doing things, even 'branding' theexhibit all of these risks and more beyond. This list
methodology. After all this investment, they will wantand balance of risks will change significantly during the
to 'sweat this asset'. Projects will have to fit into thelifecycle of the project. In addition to ongoing Risk
corset they impose - this can cause strangulation atreview, CPM requires ongoing process review and
the extreme, building a high probability of failure intochange.
a project, even before it is initiated.How is it that more than 30% of projects fail? It is
After all, Prince ® was developed in the UK Publicbecause failing projects continue in the same old vein,
Sector (and the UK Government still has massivewithout contingent project management being
problems delivering projects). At the top end ofdeployed and the management not responding
projects, Prince is often seen as excessivleyappropriately to changes in risks.
bureaucratic, but it shouldn't be like that. CPM should