PMO Presentation

Editor's Notes

1. P2FP2009-DEL-EN-Slides 1.1Maven Training Ltd 2007 P2FP-DEL-EN-1. Slides 6.5 Maven Training PRINCE2™ Course Slides Maven Training Ltd 2007 P2FP-DEL-EN-1. Slides 6.5 You can give the brief history of PRINCE2 if you like, but this is no longer part of the Syllabus PRINCE was established by CCTA (the Central Computer and Telecommunications Agency) in 1989. CCTA is now the Office of Government Commerce and they continued to develop PRINCE. PRINCE2 was launched in 1996 in response for a project management method that could be used for all sorts of projects and not just IT systems. There are other methods and approaches but realistically PRINCE2 is seen as best practice - probably best evidenced by its wide requirement in many project management job specifications In the UK, the APM have their own Body of Knowledge; in US the PMI have a similar “Body of Knowledge”; the BSI have BS6079 but these are primarily for guidance and do not have the project management structure which resides within PRINCE2 and makes it unique. Give an overview to delegates of how P2:2009 was generated and “split” into two with the Directing manual. Also how this now links in with the other available standards. Office of Government Commerce (OGC), owns the licence: Works with public sector organisations to help them improve their efficiency, gain better value for money from their commercial activities and deliver improved success from programmes and projects APM Group are the examination board Supported by accredited training companies and consultants Important to reassure delegates that the examinations are formally accredited and therefore are well respected in the job marketplace. This is not the sort of course where they simply turn up and get an attendance certificate - their hard work is formally recorded in their examination results. Last point - remind them that PRINCE stands for PR ojects IN C ontrolled E nvironments – consider drawing this on a pre-pared flipchart in your training room
2. Programmes are different from projects in that it is their outcomes that matter not their outputs . Outputs are specified deliverables from projects that are delivered within time, cost and quality constraints. Outcomes are the effects of change and form part of the vision for the programme. Purpose of a programme is to change organisations and deliver the company strategy. Try to give delegates a sense of the difference between project and programme management: Business as usual is very different because of the level of certainty – there are staff who fit very well in this environment because they derive a great deal of security from this structure and if secure then they perform better – but others find it too constraining and thrive in not knowing what they are doing, who they are working with next week. Working from the bottom up – the level of uncertainty grows – BAU provides a great deal of certainty and stability over what is to be done each day. Projects, whilst subject to changes, issues and risks, still have a level of certainty, usually driven from the time constraints that they operate under – projects might deliver a little early or a little late, but in the grand scheme of things, there is general understanding of the milestones and when they will be hit. Programmes, however, are often far longer in duration, and are more uncertain of when things will eventually finish. This is coupled with an evolving project list – whatever projects you think will form part of your programme at the start, they are likely to double in number and extra workstreams will be added – it is just the nature of the work. MF- Personally, I prided myself on enjoying the uncertainty that project management gave me – doing something different every day, working with new people etc. However, when I was promoted to programme manager, I started to look back on project management very fondly, as it was so much more certain than a constantly evolving programme, where the only stake in the ground was the overall vision of what we were going to create ultimately.
3. Maven Training - MSP Foundation Course Slides MSPFP-TRA-EN-1. Trainer Slides 5.6 This diagram is based on the diagrams on p65 and 74 and tries to show delegates the linkages between what they are planning to do – in this case lets pretend that the company is growing and has lots of strategic initiatives that it is following – therefore, whilst it carries out some speculative, operational and support work we would expect to see the majority of benefits being strategic. Note that the words in the diagram are important for the Foundation exam (i.e. Strategic, Speculative, Key Operational and Support) and how these correspond to the various sectors of the matrix (-/+ importance to future organisation and +/- importance to current organisation).
4. P2FP2009-DEL-EN-Slides 1.8 Maven Training PRINCE2® Course Slides Remember our Organisation charts and the levels of management. Here we see how the concept of tolerance and management by exception works. Tolerances are approved always one level higher than who needs them. Exceptions always get raised to the next higher authority Portfolio office: Management dashboard Programme office: Escalated programme issues and risks Benefit review reports Programme progress reports – dashboard End-of-tranche review reports End programme report
5. Example of one of our recent creations in support of a client, the client could use the website before and after the event to both support their learning and embed their learning. Resources page worth a mention with downloadables etc. Questionnaire worth a mention – allows people to assess their level of knowledge prior to attending event