PMGT1860 · Project Initiation and Scope
Best Practices & New Considerations in Initiation
Week 10 is the capstone content week, surveying contemporary and forward-looking considerations in project initiation — the evolution toward Agile and hybrid methods, the strategic role of the PMO, AI-enabled and ethically-framed projects, sustainability, and sector-specific early risks. It is the anchor for the final Learning Journal entry and richer group-presentation framing, and 'why the project exists' and early-output questions appear in the quiz.
What this chapter covers
- 01Business need and justification — why the project should exist (problem/opportunity, strategic alignment, feasibility, priority, cost of not doing it)
- 02The initial Stakeholder Register as the key early output of stakeholder analysis (not a budget/closure report or WBS)
- 03The Project Charter recap — formally authorises the project and defines objectives, high-level scope, assumptions, constraints
- 04Predictive vs adaptive (Agile) vs hybrid approaches
- 05The strategic role of the PMO (Project Management Office)
- 06Sector-specific early considerations — construction/infrastructure (whole-life, maintainability, disruption) vs manufacturing (supply-chain resilience, geopolitics, reputation)
- 07Emerging frontiers — AI-driven and ethically-framed projects, sustainability, unconventional contexts, the 'dark side' of PM
- 08External shocks and long-run operational realities shaping scope, stakeholders, risks, governance and success criteria
Applied: name the purpose, the early output, and the sector-specific risk
- +1(a) Business need and justification answers 'why is this project needed — what problem or opportunity does it address?', along with its strategic alignment, feasibility, priority and the cost of not doing it. It is not about operational logistics like team size, meeting cadence or software choice.
- +1(b) The key early output is an initial Stakeholder Register (who is impacted, who has influence, who needs informing, their needs and concerns).
- +1It is not a budget report, a closure report or a WBS — those come later; the register is the early identification-and-analysis output.
- +1(c) Construction/infrastructure → whole-life asset performance and maintainability, public disruption, service continuity and future demand. Manufacturing → supply-chain resilience, geopolitical/trade uncertainty, reputation and production continuity.
Key terms
- Business need / justification
- The reasoning for why a project should exist — the problem or opportunity it addresses, its strategic alignment, feasibility, priority and the cost of not doing it. The defining question is 'why is this project needed?', not operational logistics.
- Predictive vs adaptive vs hybrid
- Predictive (waterfall) fixes scope, time and cost early; adaptive (Agile) lets requirements evolve throughout; hybrid blends the two. The discipline has been evolving toward Agile and hybrid approaches.
- PMO (Project Management Office)
- An organisational entity that centralises the management of portfolios, programs and projects; its strategic role is a live consideration in modern initiation.
- Sector-specific early considerations
- Distinctive early risks by sector — construction/infrastructure emphasises whole-life performance, maintainability, public disruption and future demand; manufacturing emphasises supply-chain resilience, geopolitical uncertainty, reputation and production continuity.
- Emerging frontiers
- Forward-looking areas of the discipline: Agile and hybrid methodologies, the strategic PMO, ethics and AI-driven projects, sustainability, project management in unconventional contexts, and the critical 'dark side' of PM (e.g. burnout).
- Initial Stakeholder Register (early output)
- The key early output of identifying and analysing stakeholders during initiation — capturing who is impacted, who has influence and their needs — as distinct from later artefacts like the budget, closure report or WBS.
Best Practices & New Considerations in Initiation FAQ
What does 'business need and justification' actually mean at initiation?
It means being able to answer why the project should exist — the problem or opportunity it addresses, how it aligns with strategy, whether it is feasible and a priority, and what happens if it is not done. It is deliberately not about operational logistics like how big the team is, how often it meets or which software it uses; those are downstream. The defining question is 'why is this project needed?'
Why does this week emphasise Agile, AI and sustainability?
Because it is the capstone content week and the anchor for the literature review and the final journal entry, so it surveys where the discipline is heading: the shift from predictive toward Agile and hybrid delivery, the strategic role of the PMO, AI-enabled and ethically-framed projects, sustainability, and even the 'dark side' of PM like burnout. These are the live frontiers you can draw on to make a literature review current.
How do initiation considerations differ by sector?
Different sectors carry different signature early risks. Construction and infrastructure must weigh whole-life asset performance and maintainability, public disruption, service continuity and future demand from the outset. Manufacturing must weigh supply-chain resilience, geopolitical and trade uncertainty, reputation and production continuity, because external disruptions change project assumptions and delivery. The general lesson is that external shocks and long-run realities should shape scope, stakeholders, risks and success criteria early.
How does Week 10 feed the final journal and presentation?
It is the anchor for the final Learning Journal entry, where you reflect on the emerging considerations and pull the semester together, and it gives the group presentation a richer framing — situating your initiation plan against Agile/hybrid choices, sustainability and sector-specific risks. It also recaps the charter's authorising role and the initial Stakeholder Register as the early output, tying Weeks 4–5 back in. Confirm the journal and presentation requirements on Canvas.
Assessment move
Use this capstone week to consolidate rather than learn new mechanics. Be able to state the purpose of business need/justification (why the project exists), the early stakeholder output (an initial register), and the charter's authorising role in one breath each. Learn the predictive/adaptive/hybrid spectrum and one sector-specific early risk for construction and for manufacturing. Pick one emerging frontier (AI, sustainability, hybrid, the PMO) to go deeper on for your literature review. Write your final Learning Journal entry reflecting across the semester, and confirm the journal and presentation briefs on Canvas.
Working through Best Practices & New Considerations in Initiation in PMGT1860? Sia is AskSia’s AI Project Management tutor — ask any PMGT1860 Best Practices & New Considerations in Initiation question and get a clear, step-by-step explanation grounded in how PMGT1860 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
