Chapter 21: Consideratioms For Organizational Adoption Flashcards
Context
Before creating a projects management method, it must be understood why an organisation wants to do this
By understanding the drivers and objectives, it’s more likely that a method will be created that meets the needs of the organisation
How do we decide who to involve in a new method
People involved should have the right skills and experience; they may be in house experts, consultants or a mix. The method they create must be acceptable to stakeholders
A way of moving to a common method within an organisation is to collect together experienced and respected PMs to compare the way they do things and ask to agree an approach that appears to be acceptable to all.
Maturity definition
A measure of the reliability, efficiency and effectiveness of a process, function, organisation etc. the most mature processes and functions are formally aligned with business objectives and strategy and are supported by a framework for continual improvement
Maturity model
A method of assessing organisations capability in a given area of skill
What are some benefits of using a maturity assessment
Helping organisations decide what maturity level they must achieve to meet business standards
Create a reliable capability baseline against which improvements in performance can be objectively measured
Providing and objective assessment of strengths and weaknesses
Justifying investment in project management infrastructure
Provide validation of an organisations maturity
Look at characteristics of P3M3 project maturity level (Table 21.1)
Look
Maturity levels: 1,2,3,4 explanation
Level 1: Awareness of process
- does the organisation recognise projects and run them differently from its ongoing business?
Level 2: repeatable process
- does the organisation ensure that each project is run with its own process and procedures to a minimum specified standard?
Level 3: defined process
- does the organisation have its own centrally controlled project processes and can have individual projects flex within these processes to suit the project?
Level 4: managed process
- does the organisation obtain and retain specific measurements on its project management performance and run a quality management organisation to better predict future performance?
Consistent terminology - look other side
Consistent terminology is important as using words in a consistent way helps communication and understanding
The organisations methods should reflect the terminology used in the organisation. Problems will occur when different parts of the business use different terminology, neither of which may be wrong
Tailoring the processes
Tailoring the processes, roles and product descriptions are closely linked. An activity in a prince2 process is undertaken by a role to create a management product. Change any one relationship and the relationship between the others may also change.
It’s advisable to start by tailoring the processes, changing them to reflect any new terminology and amend the process model and activity flows if necessary to reflect how the organisation should operate.
Having a defined procedure
Each organisation has to decide how each prince2 theme is reflected in its project management method. On individual projects, this is usually described in the PID.
Having a defined procedure ensures these aspects are covered in a consistent way and saves each PM having to define their own as they can refer to the organisations approach
Project lifecycles
Prince2 doesn’t prescribe use of a particular project lifecycle, but it does require that one is used.
Consider including one in the project management method, describing the purpose of each management stage and linking back to the prince2 processes and themes.
Standardised project lifecycles gives project managers a basis from which to tailor their own. It also enables the organisation to have an overview of the progress of its portfolio of projects
Managing the method
Method needs to be managed and maintained after its been created.
The method should include guides, procedures or processes describing how it’s managed together with associated roles and product descriptions.
Roles should include one to manage overall architecture of the method, ensuring that the process model and its component parts work as a whole
Creating tailoring rules and guidelines
Prince2 has a tailoring principle, so any method derived from it should also allow tailoring. This means that the method should include tailoring rules and guidelines. This may be covered in a few pages of text or may involve a lot of detail.
An organisation may choose to limit the extent to which its project management method can be tailored by defining the following
What rules or guidelines are applicable to the organisation?
What degrees of freedom should each role holder have ?
Who approves tailoring?
Who can advise people on tailoring?
Extra context to tailoring
As prince2 can be used regardless of complexity or scale of project, organisations may consider rating their projects by complexity and providing guidance on how each category should be tailored
The greater the complexity, the more info that is generated. A project manager should ensure that the means of storing and distributing information is efficient and secure. For simpler projects, a log book and wall display may be sufficient, but for more complex projects, especially with distributed teams, information systems will need to be developed and rolled out