One key area not considered or talked about in a great deal of project management CVs is the project lifecycle – assuming that the reviewer knows you work through a structured approach is a big mistake. As project practitioners we all work differently, some don’t work through any methodology and governance is none existent. Therefore a great starting point for writing out the remit of each role would be to use the lifecycle framework as a core structure to then build on. Let’s have a look at the project lifecycle:
Initiation – The beginning phase where objectives are defined and a business case is drawn up. At this point a decision whether to initiate the project itself based on a review of core areas such as cost, deliverables, scope, purpose, resources, timescales, structure, impact, etc.
Planning – The project is now assessed in terms of time, cost and resource; as a starting point but should be continuously updated, changed and evolved throughout the course of the project.
Execution – The project actually happens, usually overseen by the project manager and supported by the project team. Activities will be monitored and controlled throughout this phase and regular updates will be presented to the senior management team/sponsors/customers etc.
Close – Like all good things, everything must come to a close. It is especially important that projects are closed down effectively and success celebrated or lessons learnt from failure.
Now take a look at your CV and see if any aspects of the above are actually addressed? I bet there’s a list of skills but no real information or examples; am I right? Then you need to go back to the drawing board and produce a CV which employers want to see and recruiters will fall over themselves to sell you to their clients.