Tag Archives: PMO CV

How to put together a winning CV – PMO CV Tips

PMOs play an integral role in most organisations which have a number projects and programmes being delivered across the business. There are many types of PMO such a Programme Offices, Project Offices, Centre of Excellence and Portfolio Offices. Taking this into consideration and the subtleties within each, it can make for a much more interesting CV which can really pique the interest of recruiters and employers and demonstrate your knowledge and understanding of the field.

When putting together a CV we need to address some of the key criteria for a PMO professional:

Type of PMO:

  • Supportive: Providing on-demand expertise, templates, best practice, access to information etc.
  • Controlling: An environment where tighter regulation is required so there is usually the use of specific methods, templates, governance and forms etc with the likelihood of regular reviews by the PMO.
  • Directive PMO: Taking a step further than the controlling PMO and actually taking over projects by the provision of PM experience and resources to manage the projects.

puzzle

Size of PMO

  • Stand alone (1 person)
  • Team PMO (>1person)
  • Types of programmes / projects being supported?
  • How many programme / project managers feed into the PMO?

Once we have established the type of PMO and talked through the volume and types of projects and programmes, it is time to address what your involvement is. Firstly is the PMO something you have set up or reengineered or already in place? Then we want to know your role, are you managing it, an analyst, coordinator, consultant etc. Then run through the core competencies involved – what do you do on a daily basis? From this you will also be able to pull out some key achievements such as impact on project capability.

 

The PMO as you know is all about communication and how you apply that to the task in hand, there are many elements that go into this and all organisations are different. Some organisations employ business managers to manage projects and these types of PMs generally require a great deal of hand holding, think about coaching, training, workshops etc which you may have facilitated. Include this information into your CV along with the above to give the reviewer a holistic view of the role and what it actually means within your business.

PMO CV Vs Project Manager CV – Q&A

Hi Nicola, I am a PPM professional with a mix of both managing projects and implementing/managing PMOs – I am looking to secure my next contract position and want to know whether I should have two CVs, one pitched at each audience? Nadia, PMO/Project Manager; London.

Hi Nadia, many thanks for your question – one of my favourites and aimed at all those out there who have more than one string to their bow. I believe the skill-set you have is perfect for the market today as organisations are always looking to save money so having more knowledge and experience about supporting and managing projects provides exceptional value for money to employers. I also believe it is very important for project professionals to have had exposure to these two elements of PPM; it certainly makes for a more effective environment when you have sat on both sides of the fence. Keeping this in mind I suggest you ideally would have one main CV, a “master copy” which lists all of your experience and an equal number of PMO and PM achievements. This makes the CV rather long but you can strip out the PM achievements or PMO achievements for each application as relevant. That way you are still keeping in the core experience within each remit but highlighting the achievements which would be deemed most appropriate for the role you are applying for and requires a little work for each application. Some roles may be hybrid PM/PMO positions so a combination of the two elements in achievements would be useful here.PM Vs PMO That said I always believe a little tweaking is required for every job application, ensuring the relevant information for each position is demonstrated. There is generally more emphasis placed on specific competencies within a job description / job advert so bringing out more detail in these areas, re-jigging the order and stripping back detail on the competencies not asked for will always assist you in gaining more attention from the reviewer. In regard to the detail in the role remits, always ensure you place an introductory statement before you bullet the competencies, context is very important so talking through what it was you have been tasked to achieve and some detail about the complexity, team sizes etc is important. The bullets need to talk through how you delivered, do not fall into the trap of just listing a few keywords like a job description, remember every project/organisation/department works differently so do not assume the reviewer will know what you are talking about without adding in some context.

What a PMO CV should say

What should your PMO CV say – it’s all well and good telling us you support / manage / set up PMOs in your CV but do you give the recruiter or hiring manager enough information for them to get a feel for your exposure? Often I am sent CVs from PMO professionals asking for feedback and although basically it is well written, there are huge gaps leaving me wanting more detail. Recruiters and hiring managers are unlikely to pick up the phone to ask you questions when they already have an inbox full of applications, they simply move on to the next CV.

What do we want to know? Here are a few points to consider:

  • The PMO itself – what kind of PMO is it? Is it corporate level, satellite (department based, permanent for say IT), or temporary (set up for a specific programme and disbanded once the programme has delivered)
  • How big is it? Some PMOs are just one person, others run into 20’s to much larger
  • How mature is the PMO, are we talking rather new and currently creating & embedding structures, enterprise level or somewhere in between
  • How many programmes and / or projects feed into the PMO
  • What are the programmes / projects which are being supported
  • What level of support is offered – purely admin or as intended, consultants to the project management team
  • Who does the PMO report into – is it an interface between project management and the senior management team

As a PMO manager or consultant have you addressed these points?

  • What type of PMO manager are you – do you set up PMOs and move on to new assignments once you have implemented structures and handed over to someone else to manage
  • Do you have a PMO tool kit of templates which you can adapt for business needs
  • Are you all about process or pragmatic in your approach to implementing structures
  • Do you pick up existing PMOs and mange going forward as opposed to setting them up
  • What is your key specialism – do you look to address overarching business needs and work on communications
  • Are you a coach / trainer to project managers

These are few areas which require consideration when putting together a CV; too many times I have seen CVs which list a lot of bullets such as:

  • Risk & Issue Management
  • Stakeholder Mapping
  • Change Management
  • Planning

Put like this – it doesn’t tell the reviewer a great deal and does tend to read like a job description not a CV, think about adding in some context and really adding some meat to the bones. It is easy to assume that others will know all about your role at XXX plc but the reality is that we don’t, by taking time to think about how you may describe to others what you do and your environment you can really make a difference to your CV.

When a PMO CV can be too good

I have been working with a new client who is a PMO guru – she has an impressive portfolio of contract positions in a variety of industries and is highly regarded in her field. When I was first presented with her CV for a review I was pleased to tell her that her CV says all the right things although it was missing some key facts, and as a recruiter I would be delighted to receive her CV. However I also stated that her CV was a little too good, as a recruiter passing on CVs to potential clients my fear was that it is just too good. Now at this point you may ask how can a CV be too good – well you need to think about who will be screening CVs when you apply for roles, as a project management specialist I can understand the terminology, but a great deal of clients would struggle to get their heads around it. Also when you apply for roles you may not be sending your CV to a PMO specialist – there are a great deal of recruiters with no specialist knowledge in the project management field and also HR representatives alike.

My suggestion was to add in the key areas missing in the CV and break down the information supplied into a more reader friendly piece of information. Not dumb it down but use plain English with a good level of keywords put into context within the CV.

Don't make it too complex

Assuming the reader will know what it is you are trying to say is one of the biggest mistakes professionals can make when writing CVs – by sitting on the other side of the table you can start to think about how you communicate with non-project personnel, perhaps in a work environment. Therefore you are demonstrating on your CV an ability to be able to turn complex pieces of work into easy to digest information.

Working with my client has been very interesting – we agreed a plan of action and worked together to clearly promote her experience and skill-set so she has a balance of what is expected recruitment wise and what she wants to say.

This is a clear example of a client recognising she needs to do something right with her CV and accepting that change is the order of the day – that’s a great project person, taking a pragmatic approach to ensuring she comes across in the right light.