PRO4801 ASSIGNMENT MOST COMPREHENSIVE 2026
QUESTIONS EXAM LATEST VERSION SOLVED QUESTIONS
& ANSWERS VERIFIED 100 %
What does the use of phases in a project lifecycle facilitate?
Assign roles
Monitoring and reporting
Stakeholder of engagement
Provide a definition for a linear project lifecycle
Waterfall
Highly predictable
Assumes a high degree of knowledge at start of project
Provide a definition for an iterative project lifecycle
Agile
Adaptive which operates in uncertain environments
Provide the definition for a hybrid project lifecycle
Combination of iterative and linear lifecycle
What are the features of a linear project lifecycle?
Series of consecutive phases
Gate reviews
Gate review must be passed before moving to next phase
Each phase only performed once
What projects would a linear lifecycle be most appropriate?
Where schedule, scope and costs are known and can be baselined in planning
phase
What are strengths of a linear project lifecycle?
Clearly defined goals , solutions and requirements at start of project
Allows for clear direction and provision of resources
What are the weaknesses of a linear project lifecycle?
Planned budget and duration can be exceeded due to focus on delivering agreed
scope
Rigid structure that reduces opportunity of change (project scope, budget, time was
agreed with stakeholders at beginning of project)
What are the features of an iterative project lifecycle?
, Page 2 of 44
Initial phase happens once
planning, deployment and control stages repeated multiple times
Work focused in short bursts (timeboxes/ sprints)
Each iteration followed by feedback that informs next iteration
For which projects would an iterative lifecycle be most appropriate?
For projects where feedback is essential
Where timely project delivery is crucial
Where scope is unclear
What are the strengths of an iterative project lifecycle?
each sprint cycle offers opportunity to review and adjust
more flexibility
frequent client collaboration and feedback
Able to deliver MVP before project completion
What are the weaknesses of an iterative project lifecycle?
With regular feedback product may end up very different from original conception
More difficult to plan, unable to accurately assess what resource will be needed and
when
More difficulty co-coordinating as multiple workflows taking place in parallel
Communication is more difficult when work taking place simultaneously
For which projects would a hybrid lifecycle be most appropriate?
Where some aspects of the project are predictable and other aspects are unclear
What is the purpose of the extended lifecycle phase of a project?
Ensures accountability and governance of the investment remains with project team
until change is embedded
Ensures change is adopted and benefits realised
What activities does the extended project lifecycle include?
Tracking and measuring benefits
Identifying problems relating to quality and performance of product
Identifying opportunities
Capturing lessons learned from investment
Name some of the features of the concept phase of a project
Appointing a sponsor
high level requirements identified
, Page 3 of 44
Options evaluated and identified (including do nothing)
Outline Business Case developed and signed off
Name some of the features of the Definition phase of a project
Appointment of PM
Confirmation of preferred solution
Development of detailed requirements and scope
Creation of PMP
Updating/ refining business case
Sign off PMP and business case
Name some of the features of the Deployment phase of a project
Implement plans in PMP
Optimise and sign off solution and design
PM monitors and controls implementation
Manage risks, issues, changes
Progress updates and reports to stakeholders
Name some of the features of the Transition phase of a project
Project outputs handed over and accepted by Sponsor
Handover of project documentation
Review project performance
Close down project team and associated infrastructure
Lessons learned
Differentiate between linear, iterative and hybrid lifecycles
LINEAR: Need to have a well defined vision of what you're producing!! Involves a lot
of early planning, but perfect for projects where you know what the end product will
be and the project is deemed low risk. It consists of defined phases where each step
is dependent on the previous one. It allows us to have greater control over budget,
scope, plan. There are decision gates between each step where the sponsor makes
a go/no go decision allowing each stage to be managed and reviewed thoroughly.
ITERATIVE: In this approach, you start with an overall understanding of what you're
going to produce, then each step in the delivery feeds back more information into the
project. This lets you to adapt future iterations, and is often also referred to as an
'agile' approach.
HYBRID: Many organisations recognise the need for flexibility when deciding how to
structure and deliver projects; a one-size-fits-all approach isn't suitable for all
projects within a portfolio. Hybrid life cycles adopt tools from other approaches that
best meet the needs of a specific project. For example, a more agile approach may
, Page 4 of 44
be suitable for the initial project phases when uncertainty is high. Once the
requirements are clearer, you might be able to adopt a linear life cycle approach.
-linear good for low risk. iterative good for ambiguity
-linear regimented, iterative flexible
-iterative get products out of every cycle, linear product at end
-iterative new requirements can be built in in every stage, linear it is defined at the
start
Explain why projects are structured as phases in a linear life cycle.
1. Appropriate focus on the work which is current.
2. You identify and assign resources for each phase, which aids both planning and
cost control
3. Facilitates management control by reviews of each phase (stage gates/ go/no go
decision)
4. You can apply lessons from early phases to subsequent phases
5. Iteratively authorising funding and the continuation of the project enhances your
management control and mitigates risk
6. Aligning key project milestones with the end of a phase improves your
communication with stakeholders
Differentiate between a project life cycle and an extended life cycle.
Project lifecycle: Includes from where the project starts to when a product has been
produced at the end of a project, it includes the phases Concept, Definition,
Deployment, and Transition
Extended Lifecycle: It is important to use what you've built in order to realise the
benefits, two extra phases Adoption and Benefit relalisation captures the period of
use and benefit realisation
You also get the product lifecycle after this which includes Operation where you use
the product and use will become more efficient and then Termination where you
close down, demolish or decommission the output.
Outline the role of knowledge and information management to inform decision
making.
Knowledge management: Once you've gathered and analysed the information for a
project - it may have even been passed on to other stakeholders at this stage - the
knowledge within this information must be kept up-to-date and maintained. KM
focuses on supporting people in sharing what they know. Ensures relevant resources
and info can be accessed by employees when they need it, important knowledge is
kept within the business, avoids duplicated efforts
Information management: IM allows you to capture evidence that you can later use
to support stakeholder buy-in, learning and assurance of projects. Projects can
generate large amounts of information, and because of this they can hold a lot of
power. Ultimately, teams and stakeholders must be able to use the information to
make informed decisions so that they can fulfil their roles in cost-efficient and
effective ways. The information you gather should be sturdy, accurate and timely.
Quality of info is important.
Explain the benefits of conducting reviews throughout the life cycle (including
decision gates, benefits reviews and audits)
They give you the opportunity to review and confirm viability of your work. Gain and
maintain commitment from key stakeholders by keeping project visible. Early
warning of risk events, trigger release of funding, trigger early termination.
DECISION GATES: Purpose: To decide whether your project should continue to the
next step, or stop.