PMGT5871 Chap.1 Project Types and Planning Methodologies
Project Types and Planning Methodologies
The unit begins by separating projects from routine operations: a project is temporary, unique, team-based and constrained by time and money. It then sorts projects into four planning types by how clear their goals and methods are, and matches each type to an approach, from detailed upfront planning with PRINCE2 or the 10-step method to iterative Agile delivery.
The four-phase lifecycle and the four Agile values complete the frame used for every later week. In the exam, Week 1 material tends to appear as classification: deciding whether a piece of work is a project, which planning type it belongs to, which methodology fits, or which PRINCE2 principle a described practice illustrates. Precise vocabulary therefore earns marks quickly.
The Week 1 tutorial also asks teams to discuss which methodology suits their own area of work, which is good practice for justifying a choice rather than naming one.
What this chapter covers
- 01
Projects compared with operational work
- 02
Four planning types and the approach each suits
- 03
What a project management methodology contains
- 04
PRINCE2 principles, themes and processes
- 05
The 10-step project management methodology
- 06
Initiation, planning, execution and closure
- 07
The four Agile values
Worked example · free
Choosing a planning approach for two briefs
- 1Classify the footbridge as a Type 1 project with defined scope and little expected change.
- 1Recommend detailed upfront planning with a traditional method such as PRINCE2.
- 1Classify the app as closer to Type 3 because requirements must be discovered with users.
- 1Recommend Scrum, which does not need full requirements first and delivers increments for feedback.
Key terms
- Methodology
- A defined project lifecycle together with its deliverables, roles, responsibilities, processes, forms, tools and governance.
- PRINCE2
- PRojects IN Controlled Environments, a governance framework developed by the UK government agency CCTA.
- Management by exception
- A PRINCE2 principle under which stages proceed within agreed tolerances and escalate only when a tolerance is breached.
- Four-phase lifecycle
- The traditional sequence of initiation, planning, execution and closure.
Project Types and Planning Methodologies FAQ
What separates a project from operational work?
A project is temporary and creates something unique, with a team assembled for one objective, limited funds, a fixed timeframe and high levels of risk and opportunity. Routine operations such as a fortnightly payroll run repeat indefinitely, even when they have deadlines.
Which projects suit Scrum according to the planning types?
Type 3 projects, which need heavy front-end work on requirements and stakeholder engagement, are described as well suited to Scrum because it does not require detailed requirements upfront. Type 2 projects can also suit Agile or Lean delivery.
Why do organisations adopt a methodology?
A methodology makes work repeatable and consistent, gives managers a shared footing for comparing performance and assuring quality across projects, and warns early when a project starts to struggle. It is a standard way of working that can still be tailored to the environment.
What are the four planning types?
Type 1 projects can be fully planned at the start and change little. Type 2 projects need more back-end work through testing and pilots and are planned at milestone level. Type 3 projects need front-end work on requirements and engagement. Type 4 projects are highly complex and uncertain and need iterative, flexible plans.
What are the phases of the traditional project lifecycle?
Initiation defines the project and gains authorisation to start. Planning develops the project management plan with stakeholders. Execution does the work while monitoring and controlling change, time, cost and quality. Closure shuts the project down and captures lessons learned for future projects.
What is the 10-step project management methodology?
It is a practical, execution-focused methodology built around action-oriented steps rather than complex theory. The Week 1 slides note that it is used in technology projects, especially information-system implementations, and that it is less comprehensive than PRINCE2 or the PMBoK but offers a clear step-by-step approach.
Exam move
Start by learning the four planning types as a two-axis picture: clarity of the goal and certainty of the method. For each type, write one example project of your own and the approach it suits.
Then pair each PRINCE2 principle with its artefact on flashcards, because multiple-choice items often swap them: tolerances with management by exception, the lessons log with learning from experience, stage plans with management by stages. Finish by explaining the four Agile values aloud with their qualifier, that the left-hand items are valued more without the right-hand items being worthless.
Revisit this chapter after Week 9, when the Agile values return in detail. When you practise, keep the reasons short and tied to the definitions: a planning type is justified by goal clarity and method certainty, and a methodology is justified by what it supplies, such as governance, repeatability or a clear sequence of steps.
Working through Project Types and Planning Methodologies in PMGT5871? Sia is AskSia’s AI Project Management tutor — ask any PMGT5871 Project Types and Planning Methodologies question and get a clear, step-by-step explanation grounded in how PMGT5871 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
