1.1 Fundamentals and Lifecycles Flashcards

1
Q

Definition of a Project

A

A unique, transient endeavour undertaken to bring about change to achieve planned objectives

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Definition of a Programme

A

Unique, transient, strategic endeavour to achieve beneficial change by incorporating a group of related projects and BAU activities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Definition of Portfolio

A

Collection of projects and programmes to structure and manage investments to optimise strategic benefits and operational efficiency

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Features of a project

A
  • Set outputs / products / deliverables
  • Transient
  • Finite, planned time
  • Introduction of change (risk management)
  • Different sizes and complexity
  • Quantifiable and measurable benefits
  • Predetermined budget
  • Unique
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Success criteria of a project

A
  • Scope
  • Quality
  • Time
  • Cost
  • Project sponsor makes trade-off decisions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Project vs BAU - Change / Stability

A
  • Project - transformational / step change
  • BAU - maintain stability, incremental change
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Project vs BAU - Time

A
  • Project - unique, defined timescale
  • BAU - repetitive, indefinite
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Project vs BAU - Plans

A
  • Project - bespoke plans, deliver unique change
  • BAU - highly structured procedural working practices
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Project vs BAU - Risk

A
  • Project - actively managed
  • BAU - minimised to reduce threat
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Project vs BAU - Output

A
  • Project - specific one-off deliverables
  • BAU - standardised products
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Project vs BAU - Lifecycle

A
  • Project - number of phases within finite time
  • BAU - build, operation, disposal
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Project vs BAU - Funding

A
  • Project - specific, authorised business case / benefits
  • BAU - normal operational budgets
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Project vs BAU - Team

A
  • Project - dynamic, multi-skilled, specific for project
  • BAU - stable, skilled in particular functions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Core project factors

A
  • Scope (time, cost, quality)
  • Benefits and risks
  • Stakeholders
  • Alignment with objectives
  • Outputs, outcomes, benefits
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Linear lifecycle phases

A
  • Concept
  • Definition
  • Deployment
  • Transition
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Elements during project closure (linear lifecycle)

A
  • Final accounts
  • Handover of library
  • Final drawings
  • Lessons learnt
  • Settlement of contracts
  • Output agreement from Sponsor
  • Disband project team
16
Q

Characteristics & strengths of a linear lifecycle

A
  • Highly predictive
  • Known, fixed scope
  • Low risk
  • Sequential progression through phases
  • Base lifecycle (APM)
  • Standardised structure
  • Clearly defined activities, outputs, and review points
  • Used in highly regulated industries
  • Clearly defined responsibilities
  • Clearly defined resources
  • High-level timeframe
  • Defined and fixed gate reviews
  • Rigid phase structure
  • Phases focused on business case
  • Link progress directly to phases
  • Clear structure
  • Low risk due to high certainty
17
Q

Limitations of a linear lifecycle

A
  • Inflexible
  • Early decisions
  • Wait for benefits
  • Late feedback
18
Q

Characteristics & strengths of a iterative lifecycle

A
  • Pre-project evaluation of options
  • Integrated PMP
  • Evolutionary development
  • Fixed budget and timeline
  • Vague scope / evolving objectives
  • High organisational risk appetite
  • Concurrent activities
  • Product owner prioritises work
  • Product feedback during development
  • Feedback used in requirements definition
  • Short development cycles
  • Frequent reviews of benefits (timeboxes)
  • Change management loosely controlled
  • Functionality frozen before each sprint
  • High level of risk
  • Flexible
  • Accommodates continuous change
19
Q

Limitations of iterative lifecycles

A
  • Complexity
  • Requires agile methods of working
  • Uncertainty
  • Unclear scope, timeframe, and budget
20
Q

Characteristics & strengths of a hybrid lifecycle

A
  • Defined phases with iterative flexibility
  • Benefits from both linear and iterative approach
  • Flexible, accommodating change
  • Clear, defined overall structure
  • Fixed decision gates
21
Q

Limitations of a hybrid lifecycle

A
  • Conflicts
  • Inefficiency
  • Requires clarity of approach
22
Q

Lifecycle differences - Phases

A
  • Linear - concept, definition, deployment, transition
  • Iterative - pre-project, foundations, feasibility, evolutionary development, deployment, post project
  • Hybrid - evolutionary development within linear phases
23
Q

Lifecycle differences - Progression

A
  • Linear - fixed, sequential forward progress
  • Iterative - repetition and opportunity to return to early phases
  • Hybrid - sequential progress through overall lifecycle with repeats within phases
24
Q

Lifecycle differences - Scope definition

A
  • Linear - known, clearly defined
  • Iterative - Vague, unknown
  • Hybrid - balance, known objectives but vague scope
25
Q

Lifecycle differences - Required structure

A
  • Linear - rigid, regulated structure
  • Iterative - little to no structure
  • Hybrid - rigid overall structure with flexibility within phases
26
Q

Lifecycle differences - Change

A
  • Linear - scope is strictly controlled at all stages
  • Iterative - proactive and reactive change management
  • Hybrid - scope controlled at phase boundaries, with more flexibility within phases
27
Q

Lifecycle differences - Environment

A
  • Linear - stable, low risk appetite
  • Iterative - high risk appetite, vague, uncertain
  • Hybrid - balanced approach to risk
28
Q

Lifecycle differences - Benefits realisation

A
  • Linear - after transition
  • Iterative - after completion of timeboxes
  • Hybrid - during deployment phase
29
Q

Characteristics & strengths of extended lifecycle

A
  • Linear lifecycle phases, plus adoption and benefit realisation
  • Adoption phase - users start using outputs
  • Benefit realisation - monitor and review benefits against expectations
  • Entire product lifecycle considered
  • Governance and accountability managed by project
  • Benefits managed by project
  • Scope includes full product lifecycle
  • Planning includes operation, maintenance, and support
  • Financial planning includes cashflow returns from usage of the product
30
Q

Linear vs. extended lifecycle differences - Phases

A
  • Linear - concept, definition, deployment, transition
  • Extended - concept, definition, deployment, transition, adoption, benefits realisation
31
Q

Linear vs extended lifecycle differences - Budget

A
  • Linear - up to transition
  • Extended - full product lifecycle
32
Q

Linear vs extended lifecycle differences - Scope

A
  • Linear - up to transition
  • Extended - full product lifecycle
33
Q

Linear vs extended lifecycle differences - Benefits management

A
  • Linear - identified, planned, and tracked during the project
  • Extended - identified, planned, tracked, embedded, and realised by the project management
34
Q

Linear vs extended lifecycle differences - Governance & accountability

A
  • Linear - handed over to project sponsor / users
  • Extended - maintained by project team until change is fully embedded
35
Q

Choice of lifecycle - Impact of organisational context and culture

A
  • Mission, values, and objectives
  • Organisational structure
  • Governance
  • Decision making
  • Culture
36
Q

Choice of lifecycle - Specific project needs

A
  • Project complexity and uncertainty
  • Stakeholder involvement
  • Regulatory & compliance requirements
  • Time, budget, and resource constraints
  • Concurrency & simultaneous engineering