🇬🇧 Association for Project Management Qualification (APM PMQ) · subject

Association for Project Management Qualification (APM PMQ) Setting Up and Structuring the Project Syllabus

The Setting Up and Structuring the Project syllabus for Association for Project Management Qualification (APM PMQ) in full: 3 chapters, 15 topics and 24 sub-topics, every one listed below, plus 50 Setting Up and Structuring the Project flashcards with answers.

3Chapters
15Topics
24Sub-topics
50Flashcards

Setting Up and Structuring the Project syllabus: all 3 chapters

Expand any chapter to see its topics and sub-topics.

  1. Project Management Fundamentals and Context

    5 topics
    • Defining projects, programmes and portfolios
      • Distinguishing projects from business-as-usual operations
      • Characteristics: temporary, unique, change-driven
      • Relationship between projects, programmes and portfolios
    • Project management and its value
      • Why projects fail and why structured management helps
      • Benefits of applying project management
    • Programme and portfolio management distinctions
      • Programme management for coordinated change and benefits
      • Portfolio management for strategic alignment and prioritisation
    • The project environment (PESTLE)
      • Political, economic, social, technological factors
      • Legal and environmental factors
    • Operational versus project work
  2. Project Life Cycles

    5 topics
    • Phases of a linear life cycle
      • Concept, definition, deployment, transition phases
      • Extended life cycle and adoption phase
    • Linear, iterative and hybrid life cycles
      • Predictive (waterfall) versus iterative approaches
      • Selecting an appropriate life cycle
    • Phase gates and decision points
      • Gate reviews and go/no-go decisions
      • Authorising progression between phases
    • Benefits of dividing a project into phases
    • Reviews within the life cycle
      • Decision gates versus benefits reviews
      • Post-project and post-implementation reviews
  3. Governance and Structures

    5 topics
    • Project governance principles
      • Governance versus management
      • Aligning the project with organisational policy
    • Organisational structures and their impact
      • Functional, matrix and project structures
      • Effect of structure on authority and resources
    • The business case and its role in governance
      • Purpose and ownership of the business case
      • Whole life costs, benefits and dis-benefits
      • Reviewing the business case through the life cycle
    • Project office and PMO functions
    • Deployment baseline and management plans

Association for Project Management Qualification (APM PMQ) Setting Up and Structuring the Project flashcards — 50 questions with answers

  1. What is the APM definition of a project?

    A unique, transient endeavour undertaken to bring about change and to achieve planned objectives. It has a defined beginning and end, specific objectives, and is constrained by time, cost and quality.

  2. How does APM define a programme?

    A group of related projects and change management activities that together achieve beneficial change for an organisation. Its focus is on delivering outcomes and benefits, not just outputs.

  3. How does APM define a portfolio?

    A grouping of an organisation's projects, programmes and related business-as-usual activities, taking into account resource constraints. Portfolios are selected, prioritised and controlled to align with strategic objectives.

  4. List the three main differences between a project and a programme.

    Projects deliver outputs (a defined product/result), are time-bound, and have lower complexity/uncertainty. Programmes deliver outcomes and benefits, coordinate multiple projects, run longer, and involve greater complexity and strategic alignment.

  5. What is the key distinction between programme management and portfolio management?

    Programme management coordinates related projects to deliver a specific strategic outcome/benefit. Portfolio management selects and prioritises ALL projects and programmes to optimise the use of resources and align the entire investment with corporate strategy ('doing the right work').

  6. Define project management according to APM.

    The application of processes, methods, skills, knowledge and experience to achieve specific project objectives according to acceptance criteria within agreed parameters of time, cost and quality.

  7. State three reasons project management adds value to an organisation.

    It improves the likelihood of achieving objectives, ensures efficient and best-value use of resources, provides control and visibility (governance), manages risk, and satisfies stakeholders' differing needs.

  8. Distinguish between an output, an outcome and a benefit.

    An output is the tangible/intangible deliverable a project produces. An outcome is the changed state resulting from using outputs. A benefit is the measurable improvement (resulting from an outcome) that is perceived as an advantage by a stakeholder.

  9. What does the acronym PESTLE stand for?

    Political, Economic, Sociological (Social), Technological, Legal and Environmental factors of the external project environment.

  10. Why is PESTLE analysis used in project management?

    To identify and assess external environmental factors that may affect a project, helping to anticipate risks and opportunities and ensure the project remains viable in its wider context.

  11. Give an example of a 'Political' and a 'Legal' factor in a PESTLE analysis.

    Political: government policy changes, taxation, trade restrictions. Legal: health and safety law, employment law, contract law, data protection (e.g. GDPR) compliance requirements.

  12. What is the difference between the internal and external project environment?

    The internal environment consists of factors within the host organisation (culture, structure, resources, processes). The external environment consists of factors outside the organisation, typically analysed using PESTLE.

  13. Compare operational (business-as-usual) work with project work.

    Operational work is ongoing, repetitive and produces the same output to sustain the business. Project work is unique, transient (has a start and end) and produces a one-off change/output. Projects deliver change; operations sustain it.

  14. Why is it important to distinguish project work from operational work?

    They require different management approaches, governance and skills. Confusing them risks applying steady-state controls to change activity (or vice versa), poor resource allocation, and benefits not being embedded into operations.

  15. What is a project life cycle?

    The series of phases that a project passes through from its start to its closure, providing a structured framework for managing, controlling and delivering the project.

  16. Name the four typical phases of a linear (sequential) project life cycle.

    Concept, Definition, Deployment (Development/Implementation), and Transition (Handover and Closure). Some models add an extended phase covering benefits realisation.

  17. What happens during the 'Concept' phase of a linear life cycle?

    The need or opportunity is identified, the outline business case is developed, feasibility is assessed, and a decision is made on whether the project is worth investigating further.

  18. What is the main purpose of the 'Definition' phase?

    To develop the detailed business case and the project management plan (PMP), defining how the project will be executed, monitored and controlled before significant resources are committed.

  19. What occurs during the 'Transition' (handover and closure) phase?

    The completed deliverables are handed over to the sponsor/users/operations, acceptance is gained, the project is formally closed, resources are released, and lessons learned are captured.

  20. Describe a linear life cycle and when it is most appropriate.

    A life cycle where phases run in sequence, each completed before the next begins, with the full output delivered at the end. Best suited to projects with well-defined, stable requirements and low uncertainty.

Show the other 30 Setting Up and Structuring the Project flashcards
  1. Describe an iterative life cycle and its main advantage.

    A life cycle that repeatedly cycles through phases to evolve the deliverable through successive increments. Its advantage is the ability to accommodate changing/uncertain requirements and incorporate feedback early.

  2. What is a hybrid life cycle?

    A life cycle that combines linear and iterative approaches, using sequential phases for well-defined parts of the work and iterative/agile delivery for parts with high uncertainty or evolving requirements.

  3. How does an iterative life cycle handle requirements compared with a linear one?

    Iterative life cycles define requirements progressively and refine deliverables through repeated cycles, welcoming change. Linear life cycles fix requirements early and discourage later change because each phase depends on completing the previous one.

  4. What is a phase gate (gate review)?

    A formal decision point at the boundary of life-cycle phases where the project is reviewed against its business case and viability, and a go/no-go (or hold/redirect) decision is made before further resources are committed.

  5. What are the typical possible outcomes/decisions at a phase gate?

    Proceed to the next phase, do not proceed (stop/terminate), hold/pause, or proceed conditionally/with rework. The decision is based on continued viability, achievability and desirability.

  6. Who typically authorises continuation at a gate review, and on what basis?

    The project sponsor (often supported by a project/programme board) authorises continuation, based on a review of the updated business case confirming the project remains viable, achievable and desirable (worth the investment).

  7. State three benefits of dividing a project into phases.

    It provides structured control and review points (gates); breaks complex work into manageable parts; enables go/no-go decisions to limit wasted investment; aids resource and stakeholder planning; and improves monitoring of progress.

  8. How does phasing help control the commitment of resources?

    Resources and funding are committed incrementally, one phase at a time. Gate reviews between phases allow the project to be stopped before further investment if it is no longer viable, reducing financial exposure.

  9. What is the difference between a gate review and an audit?

    A gate review is a scheduled, forward-looking decision point assessing whether the project should continue. An audit is an independent, often unscheduled examination of compliance with processes, standards and governance.

  10. What is a benefits review and when does it occur?

    A review that assesses whether the planned benefits have been (or are being) realised. It typically occurs after handover/closure, during the operational phase, as benefits emerge over time rather than at project completion.

  11. What is a post-project review (post-implementation review)?

    A review held after project closure to evaluate performance, capture lessons learned, and assess whether the project delivered its outputs successfully, informing future projects.

  12. Distinguish between project reviews, gate reviews and benefits reviews.

    Project (progress) reviews monitor ongoing performance within phases. Gate reviews are decision points between phases. Benefits reviews assess realisation of benefits after handover, in operations.

  13. Define governance in a project management context.

    The set of policies, regulations, functions, processes, procedures and responsibilities that define the establishment, management and control of projects, programmes and portfolios, ensuring they align with organisational strategy.

  14. State three of the principles of good project governance.

    Clear roles and responsibilities; a single point of accountability (the sponsor); business-case-driven decisions; transparent and timely reporting; coherent organisational policies; and independent reviews/assurance.

  15. What is the relationship between governance and project assurance?

    Governance sets the framework of accountability and control. Assurance is an independent activity within governance that gives confidence to stakeholders that the project is being managed effectively and is likely to meet its objectives.

  16. What are the three main types of organisational structure?

    Functional, matrix and project (projectised) structures. The matrix is often subdivided into weak, balanced and strong matrices.

  17. In a functional organisational structure, who holds authority over project resources?

    The functional (line) manager holds authority. The project manager has little or no formal authority, and team members report primarily to their functional department, which can make cross-functional coordination difficult.

  18. What characterises a project (projectised) organisational structure?

    The organisation is structured around projects. The project manager has high (often full) authority over resources, and team members typically report directly to the project manager. It supports strong project focus but can be inefficient between projects.

  19. What is a matrix organisational structure and its main drawback?

    A structure where authority is shared between functional managers and project managers, so staff have two reporting lines. Its main drawback is the potential for conflict over priorities and resources due to dual authority.

  20. How does the type of organisational structure affect the project manager's authority?

    Authority increases along the spectrum from functional (low/none) through weak, balanced and strong matrix, to projectised (high/full). The structure determines control over resources, budget and decision-making.

  21. What is a business case?

    A document that provides justification for undertaking a project, defining the benefits, costs, risks and timescales, and demonstrating that the project is desirable, viable and achievable.

  22. What role does the business case play in governance?

    It is the central reference for decision-making throughout the life cycle. It is reviewed at every gate to confirm the project remains justified; if the business case is no longer valid, the project should be stopped.

  23. Who owns the business case, and who is responsible for developing it?

    The project sponsor owns the business case and is accountable for its ongoing viability. It is often developed/prepared with input from the project manager, but ownership rests with the sponsor.

  24. Name three typical components of a business case.

    Strategic context/justification, options appraisal, expected benefits, costs, risks, timescales, investment appraisal and the recommended option. (Any three.)

  25. What is meant by a project being 'desirable, viable and achievable'?

    Desirable: the benefits justify the investment and it supports strategy. Viable: it can be afforded and delivered within constraints. Achievable: the organisation has the capability and capacity to deliver and sustain it.

  26. What is a Project Management Office (PMO)?

    An organisational body or entity that provides support, standards, governance, tools and assurance for the management of projects, programmes and/or portfolios within an organisation.

  27. State three typical functions of a PMO.

    Defining and maintaining standards/methods; providing reporting, monitoring and assurance; supporting resource and information management; offering training, tools and templates; and supporting governance and benefits tracking. (Any three.)

  28. What is the difference between a project office and an enterprise/portfolio PMO?

    A project (or programme) office supports a single project/programme with administrative and control functions. An enterprise/portfolio PMO operates at organisational level, setting standards and providing governance and assurance across all projects and programmes.

  29. What is the deployment baseline?

    The reference documentation, agreed at the end of the definition phase, that defines what is to be delivered and how (scope, schedule, cost and management plans). Progress is measured and controlled against it during deployment.

  30. What is a project management plan (PMP) and what is its purpose?

    The output of the definition phase that brings together all the management plans (the 'how, what, why, who, when and how much' of the project). Its purpose is to gain sponsor approval and serve as the baseline document against which the project is executed and controlled.

Association for Project Management Qualification (APM PMQ) Setting Up and Structuring the Project FAQ

What is in the Association for Project Management Qualification (APM PMQ) Setting Up and Structuring the Project syllabus?

Association for Project Management Qualification (APM PMQ) Setting Up and Structuring the Project is split into 3 chapters: Project Management Fundamentals and Context, Project Life Cycles and Governance and Structures. Together they contain 15 topics and 24 sub-topics.

How many chapters are in Association for Project Management Qualification (APM PMQ) Setting Up and Structuring the Project?

3 chapters, containing 15 topics and 24 sub-topics. The largest chapter is Project Management Fundamentals and Context, with 5 topics.

Are there flashcards for Association for Project Management Qualification (APM PMQ) Setting Up and Structuring the Project?

Yes — a 50-card Setting Up and Structuring the Project deck, printed in full in the flashcards section of this page and available in the Examius app with spaced repetition. The free plan covers one exam of your choice, including its flashcards; Examius Pro, a one-time purchase, unlocks every other exam and deck.