AgilePM Foundation key terms

A structured project management method that combines an agile, iterative delivery approach with defined roles, products and controls so that projects remain governed while responding to change.

Dynamic Systems Development Method, the agile framework on which AgilePM is based; it supplies the underlying principles, lifecycle and timeboxing concepts that AgilePM adapts for project management.

The set of beliefs underpinning AgilePM: focus on business value, deliver on time, collaborate, never compromise quality, build incrementally, and develop iteratively from firm foundations.

An AgilePM principle stating that no technique should be applied dogmatically; the method is tailored to the project's size, risk and culture rather than followed rigidly.

The deliberate adjustment of AgilePM roles, products, processes and controls to suit a particular project's context, such as scale, complexity, regulatory constraints or organisational culture.

A technique in which work is fixed to a defined period with fixed effort and a fixed deadline, and scope is varied to fit, ensuring predictable delivery dates.

A fixed, indivisible period of time within which a defined objective must be achieved; in AgilePM these occur at project, stage, and iteration or work-package level.

A ranking technique that classifies requirements as Must have, Should have, Could have or Won't have this time, so that lower-priority scope can be dropped to protect deadlines.

The agreed set of Must-have requirements that must be delivered for the product to be acceptable and usable; it defines the scope floor for a timebox.

An approach in which deliverables are refined through repeated cycles, each adding detail or improving quality based on feedback, rather than being produced in a single pass.

Building and releasing a solution in usable portions that each add value, allowing earlier benefit realisation and feedback instead of waiting for a single final delivery.

A short, fixed timebox within a stage during which a team analyses, designs, builds and tests a portion of the solution, ending with a review of what was produced.

The first AgilePM phase, which establishes whether the proposed project is viable and worth doing, producing a Business Case and outline solution before committing larger investment.

The second AgilePM phase, which establishes a firm, agreed understanding of the business need, solution outline and delivery approach before the main build begins.

The third AgilePM phase, where the solution is built incrementally and iteratively through timeboxes, producing tested, usable increments for review and acceptance.

The final AgilePM phase, in which the tested solution is brought into operational use, users are trained and supported, and benefits are confirmed against the Business Case.

The role accountable for overall project delivery, managing the Business Case, plans, risks and resources, and providing the single point of management contact for the project.

The senior role that owns the Business Case, secures funding, makes key decisions and provides the ultimate authority for the project, championing it at senior management level.

The role that defines and communicates the business vision of the project, ensuring the solution stays aligned to the intended business benefit and arbitrating on business direction.

The role responsible for ensuring the technical aspects of the solution are coherent, feasible and aligned, advising on architecture and resolving technical conflicts between teams.

The role that leads the Solution Development Team, facilitating its work, removing impediments and representing the team in management and planning activities.

The role that elicits, analyses and documents requirements and supports the team in refining the solution so it meets the business need.

The empowered, self-organising group that analyses, builds and tests the solution within timeboxes, typically including team leader, business analyst, tester and developers.

The role responsible for verifying that the solution meets requirements and quality expectations, planning and executing testing and providing feedback to the team.

The document setting out the business justification for the project, including expected benefits, costs, risks and timescales, used to decide whether to start and continue.

The AgilePM product that captures requirements with MoSCoW priorities, forming the basis for planning timeboxes and defining the Minimum Usable Subset.

The high-level plan showing the overall project scope, phases, timescales and key milestones, used by the Project Manager to control delivery across the lifecycle.

A plan covering a single phase or stage, showing the work, resources and timeboxes required to achieve that stage's objectives within the overall Project Plan.

A plan describing how a timebox or increment will be delivered, including the work packages, resources and sequencing needed to produce the agreed products.

A defined unit of work within a timebox, assigned to the team with clear products, acceptance criteria and effort, forming the basis for day-to-day control.

The process of confirming that the intended business benefits described in the Business Case are actually achieved after deployment, informing whether the project succeeded.

A structured, collaborative meeting run by a facilitator to gather requirements, agree priorities or resolve issues quickly with the right stakeholders present.

A short, regular team meeting in which members share progress, plans and impediments to coordinate work and surface problems early.

A review held at the end of a timebox or stage in which the team reflects on what went well and what to improve, agreeing actions for the next cycle.

The act of putting a tested increment or the final solution into operational use, including any migration, training and support arrangements needed.

The practice of identifying, controlling and tracking versions of products and changes to them, ensuring the right versions are used and delivered.

The planned and systematic activities that provide confidence that the solution and its products meet agreed quality standards and acceptance criteria.