1.7 Explain why aspects of project management governance are required
- Governance is the framework of authority and accountability that defines and controls outputs, outcomes and benefits from projects, programmes and portfolios
- It is a mechanism for financial and technical control
- The steering group is the governance board
- Business change governance is most applicable to project work, as opposed to operational governance (corporate governance is also important)
It has the following 4 benefits:
- provides confidence to stakeholders
- ensures there is a business case
- ensures there is a recognised life cycle
- ensures there are clearly defined processes and documentation (reviews and audits, PMP, RAM, communication plan
What are the stages of an iterative life cycle?
- Pre-project
- Feasibility
- Foundation
- Evolutionary
- Deployment (repeats with assemble, review, deplo)
- Post-project
3.5 Describe where portfolio management may be appropriate
Where:
- you need assurance of alignment with strategic objectives
- where financial controls need to be applied
- there is need for discrimination between projects and BAU
- you need to verify the organisation has the necessary capabilities for work
- you want to develop a supplier pipeline (sustainable engagement)
- you need evidence of engagement with customers
4.3 State factors which can positively or negatively affect communication
Many factors can be influence communication in a project
- Type/method of communication and body language (verbal, non-verbal, written, virtual)
- Use of technical terms (shared understanding but can be obfuscating so should provide people with supplmentary info)
- Organisational culture and structural hierarchies (intimidation vs engagement)
- Time zones and geography (meeting timing norms, compensation for out of hours working)
- Physical and environmental (feeling safe leads to better communication)
- Planning of communication (ensuring it’s timely, relevant, consistent)
What is the name of the model used to address conflict?
Thomas-Killman
5.5 Explain which factors influence the creation, development and leadership of teams
You don’t necessarily get to choose who joins the team but you have to lead it
Tuckman Model: progress through team stages is facilitated by effective leadership.
* Forming (first point of contact, guarded, leader to make things inclusive and objectives clear)
* Storming (personalities develop, conflicts arise, conflicts need to be managed and resolved)
* - Norming (cooperation increases, focus on tasks, leader to provide process, clear roles and responsibilities, feedback)
* - Performing (delivering targeted performance, problem solving and motivation high, leader should ensure performance is maintained with openess and development of relationships, stopping team reverting)
* - Adjourning (added later, acknowledges effort of team leader in preparing team for end of project and transition back into org)
Another factor that’s been considered is the influence of different personalities working together. Use the Belbin model.
Belbin described nine social roles that people adopt
Indivduals will perform better if they are given a role that suits their strengths
- Action cluster (shaper (drive), completer finisher (subject output to quality control), implementer (plan and carry out efficient strategy))
- Social (team worker (diplomat, versatile), resource investigator (finds ideas), coordinator (focus on objectives and delegate))
- Thinking (plant (support for problem solving and obstacles), monitor evaluator (logical, impartial judgements), specialist (distinct strengths in a narrow area))
6.11 Explain the relationship between stakeholder analysis, influence and engagement
- To ensure success of project, we need to engage stakeholders
- We need to first analyse the stakeholder by assessing their influence (power+interest), opinions on the project, and how risky this is to visability and success of project
- We then need to plan how to enage with them based on these factors
- We should understand how they might react to different communication approaches, and determine what will be most successful to create an engagement plan.
- Two things to note. Firstly, we may or may not want stakeholders to engage with on another
- Secondly, the objectives of stakeholders will rarely be aligned (finance director vs supplier) so political skill is involved in assuring maximum satisfaction
6.6 Explain the relationship between the deployment baseline and the development of a project management plan in linear and iterative life cycles
The project management plan incorporates the scope, schedule, cost, risk, quality and resources of a project
The fundamental of this form the deployment baseline which is approved, along with the PMP
The project then proceeds to the deployment phase where the deployment baseline will be used for progress monitoring and implementation of change control
In a linear life cycle, the assumption is that all work can be defined, estimated, scheduled, risked, resourced and costed at the beginning. A baseline can be established from which deployment can be managed and controlled. Scope and quality as drivers and time and cost are negotiated in reference to them.
In an iterative lifecycle, a baseline plan is still required but assumption is not that all elements are known (flexibility and agility is needed). Resources and schedule are drivers and scope and quality are negotiated in reference to them.
6.12 Explain the importance of managing stakeholder expectations to the success of the project
Managing stakeholder expectations is important to the success of a project for the following reasons:
- It enables more effective risk management (stakeholders are influential and therefore carry risk to the viability, perception and reception of a project)
- It requires improved comms planning (how, why, when and what to communicate)
- This enables more effective engagement with stakeholders in which feedback is incorporated into the project, positive interest is sustained
- It ensures a more productive project team is formed (as internal stakeholders with expertise can be incorporated into the team)
- It increases the likelihood of a project being accepted (fulfilling needs and clarifying these early in project)
6.14 Interpret earned value data
- The cumulative cost plan for the project can be shown on a graph (usually as s curve)
- At any time, the s-curve can be viewed and the the budgeted cost of the scheduled works (BCWS), the actual cost of the of the work that has been performed (ACWP), and the earned value (BCWP) can be plotted
- This allows you to analyse the relationship between these figures to identify cost and schedule variance
- BCWP - ACWP = cost variance
- BCWP - BCWS = schedule variance
- This can forcast future performance and also allow you to assess project status (and associated issues)
6.1 Explain the importance of a business case throughout the project life cycle
- A business case provides justification for undertaking a project or programme, evaluating the benefits, costs, risks of different options
- It usually includes a strategic case (aligning with strategic objectives), economic case (best value for money), commercial case (commercial viability), financial (funding availability), management case (how and by whom will change be delivered)
- Business cases are important because, if a case is ill-defined, the project will always have trouble being delivered and is unlikely to realise benefits
- It is essentially a contract between the project and business so targeted benefits are clear
- Throughout the life cycle: Concept (launchpad, justification), Definition (most effective project management plan selected), used at gate review), Deployment (referenced to ensure ongoing viability) , Transition (reference to test whether benefits have been realised)
6.2 Explain what is meant by benefits management
Projects are initiated in order to deliver change that will bring about benefits
These need to be managed to ensure that they’re realised
Benefits Management Plan: explains how benefits will be managed. It has five stages.
Identification: Benefits outlined and recorded with justification and measurement criteria
Definition: Benefits modeling and mapped to understand how benefits will be realized when transitioned in operational use.
Planning: Capturing baseline measurements, identifying timelines and milestones and targets
Tracking: Tracking whether benefits are being embedded through use of the output
Realisation: When benefits are realised, includes longterm actions and monitoring to ensure they continue + opps for additional benefits
What is the parametric method of estimation?
Parametric: This method uses historical data and statistical relationships.
The specifications of each deliverable are established. Then unit rates would be applied (such as price books) to create an overall cost or schedule estimate.
Provided the scope is accurate and conditions that inform the work and norms are similar, this can be a very accurate method.
Good for deployment stage.
What is the name of the estimation method where supplier and delivererer estimates are added up?
Analytical
6.10 Explain the reasons for and benefits of re-estimating throughout the project life cycles
An estimate is inherently uncertain
However, as the project progresses, uncertainty will decline and a new, more accurate estimating can be done (estimating funnel)
The benefits of resestimating are:
- Reduced contingency reserves
- Technical experts added to project team so accuracy can be increased
- Opportunity to incorporate lessons learned: variances and trends can be incorporated into the next estimates
- Increased likelihood of adhering to overall estimates (actions can be taken early to respond to variances)
- More confidence for stakeholders that project will be delivered successfully
- Minimising effect of estimating error (timely warning of errors)
6.7 Explain the importance of producing a project management plan
- The PMP is produced by the PM through engagement with all relevant stakeholders
- It is the plan for the project and how it is to be carried out
- It acts as a contract between the project manager and sponser (clarifies requirements, expectations)
- It is used as a reference by all stakeholders to understand and monitor the project
- It is important because it ensures continuity throughout deployment (even if there is staff turnover)
- It can be useful in monitoring and performance reviews
How should you think of contingencies in iterative life cycles?
When using an iterative life cycle, it might be more useful to think about contingencies in terms of scope and quality (resources are pre-approved). Timeboxes might have lower priority items that can be sacrificed.
6.15 Explain the benefits of using the interpretation of earned value data
Interpreting earned value data is useful because:
- it enables objective measurement and reporting or project status
- supports effective management of resources, identifying areas that are impacting performance
- establishes basis for estimating final cost and schedule by using earned value in cost performance index and schedule performance index projections
- it provides means of assessing change
You do this by using these formulas: BCWP/ACWP = CPI, BCWP/BCWS = SPI
It is important to note that interpreting earned value is useful but it’s only an indicator of project progress
7.3 Explain how to manage scope through configuration management processes
The ‘configuration’ is the functional and physical characteristics of the final deliverable informed by the Product Breakdown Structure
Configuration management refers to all activity involved in creating, maintaining and changing a scope of work
Once baselined, configuration is subject to formal change control and configuration management.
This ensures that the current version is always known and there is traceability between versions.
Configuration management consists of:
- Planning: outlines procedures, roles, responsibilities
- Identification: breaking down a project into configuration items and creating a referencing system
- Control: changes to configuration are controlled
- Status accounting: records and reports that relate to a deliverable - showing all changes, and when they were done by whom
- Verification: Determining whether a deliverable conforms to requirements and configuration information
7.1 Explain how to define scope in terms of outputs, outcomes and benefits
Scope is the totality of the outputs, outcomes, benefits and the work to achieve them
Scope of work can be identified using a product breakdown structure (PBS),a hierarchical structure with the final product at the stop and all smaller constituent parts lower down. It can be used to do ensure that the products identified are what stakeholders expect.
The project manager would use this in conjunction with a work breakdown structure (WBS), which details the activities and work packages required to deliver output.
Where the objecive is well understood at the start (e.g building a house), the scope is generally defined as accurately as possible at the beginning.
Where the objective is less certain (e.g. iteratively developing a video game), this needs to be more flexible, with priorities defined by stakeholder engagement.
7.2 Explain how to establish scope through requirements management processes
Project requirements are set by stakeholders
Requirements management is the process of capturing, assessing and justifying stakeholders’ wants and needs via a structured process
Here are the key stages:
- Identification (requirements through interviews, surveys, workshops)
- Analysis (in terms of schedule, cost, investment, value)
- Consultation and Agreement (stakeholders debate around options, strategic objectives, funding, acceptance criteria)
Worst-case is delivering only must-haves as a minimal viable product (MVP)
8.1 Describe ways to create and maintain a schedule
- Scheduling allows you to plan when each task or work package in a project should be completed in order to work to final deadlines
- Scheduling products exist but you should have a general understanding before using
- You develop this from the work breakdown structure and estimates for each task for effort/duration
- You then create the schedule by planning out when everything needs to be performed, taking into consideration optimisation, dependencies and resource availability
- You should then verify that the defined schedule meets success criteria
- Dependencies can be shown on a network diagram. A Gantt chart can show dependencies and scheduling. A histogram can show resource requirements.
8.5 Differentiate between resource smoothing and resource levelling
Resource levelling: when resources are limited by time is more flexible. Could redefine scope of activities to be undertaken by a specific resource and moved to another. Redefine the specification (without change to quality of product). Increase task duration to reduce overall resource requirements. Increase resources on earlier work so peaks are avoided later down the line. Moving activities not on critical path to reduce demand at peak times.
Resource smoothing: when time is more important than cost. Could add more resources to complete a task and aiming for smooth use of resources without peaks and troughs, optimising flow of resources from one task to another). Resource smoothing will only help duration of project if applied to critical path activities (Wouldn’t have an impact if applied to those with float). Redefinition of order of work may be required (moving things to happen simultaneously, for example).
8.6 Differentiate between cost planning for iterative life cycles and for linear life cycles
Cost planning is an essential part of the project management process. Project manaers need to understand where costs fall in their schedule to manage resource demand, supplier payments and funding requirements
In an iterative life cycle, the release of funds may be more frequent due to short intervals of work produced and close work with sponsor
In linear life cycle, funds may only be released at decision gates, where current costds are understood and future costs approved
