First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1AgilePM fundamentals and the Agile Project Management approach
In Agile Project Management, what is the primary purpose of the Foundations phase?
- To build and test the first increment of a working product
- To confirm that the project is both feasible and worth doing before committing to delivery Correct answer.
- To deploy the finished solution into the operational environment
- To run the daily stand-up cadence for the delivery team
Explanation
The Foundations phase establishes the business case, the team, and the initial plans so the organisation can decide whether the project should proceed. Delivery work and deployment happen in later phases.
Question 2AgilePM fundamentals and the Agile Project Management approach
What is a 'timebox' in AgilePM?
- A checkpoint meeting held at the end of each week
- A fixed, immovable period of time within which work must be completed Correct answer.
- A contingency budget held by the project manager for overruns
- A list of prioritised requirements agreed with the business sponsor
Explanation
AgilePM fixes time and cost at the level of the timebox and flexs the scope delivered within it. This is the core mechanism that makes the approach controllable while remaining agile.
Question 3AgilePM fundamentals and the Agile Project Management approach
Which role in AgilePM is accountable for the business case and for ensuring the project delivers the expected business benefit?
- The Team Leader
- The Project Manager
- The Solution Development Team
- The Business Sponsor Correct answer.
Explanation
The Business Sponsor is the single business-focused decision-maker who owns the business case and is accountable for the realisation of business benefits. Other roles support delivery but do not hold that accountability.
Question 4AgilePM fundamentals and the Agile Project Management approach
What is the main purpose of a MoSCoW prioritisation of requirements?
- To agree which requirements are essential for the timebox and which can be flexed Correct answer.
- To estimate the effort needed to build each requirement
- To assign each requirement to a specific developer
- To record the order in which requirements were requested by users
Explanation
MoSCoW separates Musts, Shoulds, Coulds and Won't-haves so the team knows what must be delivered and what can be dropped if time runs short. It is a prioritisation technique, not an estimating or resourcing technique.
Question 5AgilePM fundamentals and the Agile Project Management approach
In the AgilePM lifecycle, in which phase is the solution typically assembled into a form that can be deployed?
- Deployment Correct answer.
- Foundations
- Pre-Project
- Feasibility
Explanation
The Deployment phase assembles the increments into a deployable solution, confirms it is fit for purpose, and hands it over. Earlier phases establish the project and build increments.
Question 6AgilePM fundamentals and the Agile Project Management approach
What does the AgilePM principle 'Focus on the business need' most directly require of the project?
- That every requirement requested by the business is delivered
- That priorities are driven by delivering business value and that the business case is kept current Correct answer.
- That the solution is built using the latest available technology
- That the project manager makes all prioritisation decisions alone
Explanation
This principle requires the team to understand the business objective and to prioritise work by value, revisiting the business case as things change. It does not mean accepting every requirement.
Question 7AgilePM fundamentals and the Agile Project Management approach
What is the purpose of a Daily Stand-up in AgilePM?
- To obtain formal sign-off of completed increments from the business
- To review the business case with the sponsor
- To demonstrate the working solution to stakeholders
- To let the team share progress, plan the day and surface impediments Correct answer.
Explanation
The Daily Stand-up is a short team meeting for coordination: what was done, what is planned, and what is blocking progress. Formal reviews and demonstrations happen in other forums.
Question 8AgilePM fundamentals and the Agile Project Management approach
Which statement best describes the AgilePM view of 'collaboration' as a principle?
- Collaboration is optional if the team is co-located
- Only the Solution Development Team should be involved in shaping the solution
- All stakeholders who can contribute to or are affected by the solution should be involved appropriately Correct answer.
- The business sponsor should approve every design decision before it is made
Explanation
The collaboration principle calls for the right stakeholders to be engaged at the right time so that knowledge and decisions are shared. It applies regardless of co-location and does not require approval of every decision.
Question 9AgilePM fundamentals and the Agile Project Management approach
A team is two weeks into a four-week timebox and reports that a Must-have requirement will not be finished. According to AgilePM, what should happen?
- Add more developers to the team immediately
- Escalate to the project-level roles because a Must-have is at risk and cannot simply be dropped Correct answer.
- Quietly reclassify the Must-have as a Could-have so the timebox still completes
- Extend the timebox by one week to fit the work in
Explanation
Musts are not negotiable within the timebox; if a Must is at risk, the team must escalate so that project-level roles can act within tolerances. Reclassifying or extending the timebox would undermine the fixed time and cost.
Question 10AgilePM fundamentals and the Agile Project Management approach
What distinguishes a 'Should-have' requirement from a 'Could-have' requirement in MoSCoW?
- A Should-have must always be delivered before any Could-have is even considered
- A Should-have is important and normally delivered, but can be dropped if it threatens the timebox outcome Correct answer.
- A Should-have is work that will not be done in this timebox at all
- A Should-have is a nice-to-have that is only done if time permits
Explanation
Shoulds carry real value and are expected to be delivered, but they are the first candidates for flexing when time is short. Coulds are lower-value items taken only if capacity allows.
Question 11AgilePM fundamentals and the Agile Project Management approach
Which AgilePM role is responsible for facilitating the Solution Development Team and ensuring it works effectively?
- The Business Analyst
- The Business Sponsor
- The Technical Coordinator
- The Team Leader Correct answer.
Explanation
The Team Leader is responsible for the team's effectiveness, removing impediments and facilitating communication with project-level roles. Other roles contribute expertise but do not hold this facilitation responsibility.
Question 12AgilePM fundamentals and the Agile Project Management approach
Why does AgilePM insist that the business case be reviewed at defined points during the project?
- Because the sponsor must re-sign the project mandate each time
- Because business circumstances change and continued investment must remain justified Correct answer.
- Because the solution must be rebuilt if the business case changes
- Because the finance department requires monthly reporting
Explanation
The business case is a living document in AgilePM: incremental delivery and evolving requirements mean the justification for continuing must be reassessed. If the case no longer holds, the project can be stopped early.
Question 13AgilePM fundamentals and the Agile Project Management approach
A project has a fixed deadline and fixed budget, but the exact feature set is uncertain. Which AgilePM mechanism makes this situation manageable?
- Fixing the scope and allowing time and cost to vary
- Fixing time and cost at the timebox level and flexing the scope delivered Correct answer.
- Allowing all three of scope, time and cost to float freely
- Removing the requirement for a business case
Explanation
AgilePM fixes time and cost and flexs features, using prioritisation to guarantee the most valuable scope is delivered. This is sometimes summarised as fixing time and cost while flexing scope.
Question 14AgilePM fundamentals and the Agile Project Management approach
What is the role of the Vision in an AgilePM project?
- It expresses the measurable business benefits the project will deliver and guides decision-making Correct answer.
- It is the technical architecture document for the solution
- It is the schedule of timeboxes for the whole project
- It is a detailed specification of every requirement to be built
Explanation
The Vision is a short statement of the business objective and the measurable benefits expected, used to keep the project aligned with the business need. It is deliberately high-level rather than a specification.
Question 15AgilePM fundamentals and the Agile Project Management approach
During a timebox, the team discovers a simpler way to meet a requirement that changes the agreed design. What does AgilePM expect?
- The team should revert to the original design because it was already agreed
- The team should use its empowerment to make the decision within agreed boundaries and inform relevant roles Correct answer.
- The team should log the idea for a future project and continue as planned
- The team must stop work and seek formal change approval from the sponsor before proceeding
Explanation
AgilePM empowers the Solution Development Team to make day-to-day decisions within agreed tolerances, keeping communication open with project-level roles. Formal change control is reserved for changes beyond those boundaries.
Question 16AgilePM fundamentals and the Agile Project Management approach
Which artefact holds the prioritised requirements together with their acceptance criteria and is baselined at the end of Foundations?
- The Benefits Profile
- The Business Case
- The Prioritised Requirements List Correct answer.
- The Timebox Plan
Explanation
The Prioritised Requirements List captures requirements with MoSCoW priorities and acceptance criteria, and is baselined at the end of Foundations for use during delivery. The other artefacts serve different purposes.
Question 17AgilePM fundamentals and the Agile Project Management approach
What is the primary purpose of a timebox review (demonstration) in AgilePM?
- To renegotiate the project budget with the sponsor
- To show stakeholders the delivered increment and confirm it meets the agreed acceptance criteria Correct answer.
- To conduct individual performance appraisals for team members
- To estimate the effort for the next timebox
Explanation
The timebox review demonstrates what has been delivered against the acceptance criteria so stakeholders can confirm fitness for purpose. Planning and budgeting are handled elsewhere.
Question 18AgilePM fundamentals and the Agile Project Management approach
An organisation wants to adopt AgilePM but has a governance requirement for formal stage boundaries. How does AgilePM accommodate this?
- It replaces governance with daily stand-ups only
- It requires the project to be run as a single continuous timebox
- It provides defined phases and end-of-phase assessments while keeping delivery iterative within them Correct answer.
- It removes all formal checkpoints to maximise agility
Explanation
AgilePM combines an iterative delivery approach with project-level phases and assessments, allowing formal governance checkpoints without sacrificing agility. Governance is not discarded.
Question 19AgilePM fundamentals and the Agile Project Management approach
Which of the following best describes a 'Won't-have' in MoSCoW prioritisation?
- A requirement that has not yet been estimated
- A requirement explicitly agreed as out of scope for the current timebox Correct answer.
- A requirement that must be delivered before the timebox ends
- A requirement that the team has failed to deliver
Explanation
Won't-haves are recorded to make the boundary of the timebox explicit and to manage expectations. They are deliberate exclusions, not failures or undelivered Musts.
Question 20AgilePM fundamentals and the Agile Project Management approach
In AgilePM, what is the relationship between the Project Manager and the Solution Development Team?
- The Project Manager directly assigns every task to individual team members
- The Project Manager manages the project externally to the team and does not direct its day-to-day work Correct answer.
- The Project Manager sits inside the team and reports to the Team Leader
- The Project Manager replaces the Team Leader in small projects
Explanation
AgilePM separates project-level management from team-level leadership: the Project Manager focuses on the project's external management and controls, while the Team Leader facilitates the team's internal work.
Question 21AgilePM fundamentals and the Agile Project Management approach
A sponsor asks why the team cannot simply commit to delivering all Could-have requirements in the current timebox. What is the best AgilePM response?
- Coulds are contingency; committing to them removes the flexibility needed to protect Musts and Shoulds Correct answer.
- Coulds must be re-estimated before they can be discussed
- Coulds are forbidden from ever being delivered
- Coulds can only be delivered after the project closes
Explanation
Could-haves act as the buffer that allows scope to flex without threatening the timebox outcome. Treating them as commitments would eliminate that contingency.
Question 22AgilePM fundamentals and the Agile Project Management approach
Which combination of behaviours best demonstrates the AgilePM principle 'Demonstrate control'?
- Avoiding all documentation to move faster
- Planning at multiple levels, using tolerances, and making progress visible through timeboxes Correct answer.
- Delivering everything requested regardless of priority
- Letting the team self-organise without any reporting
Explanation
Demonstrate control means planning appropriately at different levels, agreeing tolerances, and using timeboxes and visible progress to keep the project under control. It is not the absence of control.
Question 23AgilePM fundamentals and the Agile Project Management approach
The team realises that a technical assumption made during Feasibility is no longer valid and affects a Must-have. What is the most appropriate AgilePM response?
- Cancel the project immediately
- Change the Must-have to a Could-have without telling anyone
- Raise it at project level so the impact on the business case and tolerances can be assessed Correct answer.
- Ignore it until the end of the project to avoid disrupting delivery
Explanation
Issues that threaten Musts or the business case must be escalated so project-level roles can assess impact and act within tolerances. Silently changing priorities or ignoring the issue breaks the control framework.
Question 24AgilePM fundamentals and the Agile Project Management approach
Why does AgilePM recommend that the Solution Development Team includes all the skills needed to deliver the solution?
- So that the team can avoid communicating with the business
- So that the Project Manager can delegate all project-level decisions to it
- So the team can make decisions and deliver increments without external dependencies slowing it down Correct answer.
- So that individual specialists can work in isolation on separate components
Explanation
A team with the full range of required skills can self-organise, make informed decisions, and deliver working increments without waiting on outside groups. This supports empowerment and iterative delivery.
Question 25AgilePM fundamentals and the Agile Project Management approach
A project is delivering well but the business environment shifts so that the original benefits are unlikely to be realised. What does AgilePM suggest?
- Remove the Vision because it is no longer accurate
- Increase the team size to deliver faster
- Continue to the original plan because the timeboxes are on schedule
- Reassess the business case and consider stopping or reshaping the project Correct answer.
Explanation
AgilePM treats the business case as the primary justification for continued investment, so a change in expected benefits should trigger reassessment and possibly early termination. Schedule adherence alone does not justify continuing.
Question 26AgilePM fundamentals and the Agile Project Management approach
How many delivery timeboxes does AgilePM typically require a project to contain?
- As many as the schedule allows
- At least two Correct answer.
- At least three
- Exactly one
Explanation
AgilePM structures a project around a minimum of two delivery timeboxes so that the team can learn from an early increment and feed that learning into later increments. A single timebox would remove the iterative benefit that the approach depends on.
Question 27AgilePM fundamentals and the Agile Project Management approach
In AgilePM, which roles sit within the project management team rather than the solution development team?
- Business Sponsor and Project Manager Correct answer.
- Solution Tester and Technical Coordinator
- Project Manager and Business Analyst
- Team Leader and Business Ambassador
Explanation
The project management team contains the project-level roles of Business Sponsor, Business Visionary, Technical Coordinator, Project Manager and Business Analyst. The solution development team contains roles such as Team Leader, Business Ambassador, Solution Developer and Solution Tester.
Question 28AgilePM fundamentals and the Agile Project Management approach
What is the purpose of the Foundations stage in an AgilePM project?
- To confirm that the deployed solution delivers the expected benefits
- To establish the initial project foundations before delivery timeboxes begin Correct answer.
- To deliver the first increment of working solution
- To decompose the whole project into detailed task estimates
Explanation
Foundations establishes the project's foundations, covering the business case, the prioritised requirements list, the solution architecture and the initial plans, before delivery begins. It is deliberately kept short and 'just enough'.
Question 29AgilePM fundamentals and the Agile Project Management approach
Which AgilePM product is used to capture the prioritised requirements and is baselined at the end of Foundations?
- Business Case
- Timebox Plan
- Benefits Assessment
- Prioritised Requirements List Correct answer.
Explanation
The Prioritised Requirements List holds requirements with their MoSCoW priorities and acceptance criteria, and it is baselined at the end of Foundations to give a stable reference for delivery. Changes to it are then managed through formal control.
Question 30AgilePM fundamentals and the Agile Project Management approach
What does the AgilePM principle 'Be collaborative' primarily encourage?
- Working together closely with all relevant stakeholders to build trust and shared understanding Correct answer.
- Delegating all decisions to the Business Sponsor
- Limiting stakeholder involvement to formal stage boundaries
- Documenting every decision so that it can be audited later
Explanation
Being collaborative means involving the right people throughout, communicating openly and building trust so that decisions are made with shared understanding. It favours rich, frequent interaction over formal documentation alone.
Question 31AgilePM fundamentals and the Agile Project Management approach
Which role in AgilePM is accountable for the business case and for the return on investment of the project?
- Project Manager
- Business Visionary
- Team Leader
- Business Sponsor Correct answer.
Explanation
The Business Sponsor is the single point of accountability for the business case and for realising the project's return on investment. The Project Manager supports the sponsor but does not own the business justification.
Question 32AgilePM fundamentals and the Agile Project Management approach
What does the AgilePM principle 'Deliver on time' mean in practice?
- Fixing the timebox duration and varying the scope delivered within it Correct answer.
- Extending the deadline when the team falls behind
- Reducing quality checks to keep to the schedule
- Committing to all requirements regardless of priority
Explanation
Delivering on time means treating timebox duration as fixed and adjusting the scope delivered, using MoSCoW priorities, rather than letting the deadline move. Quality is protected while scope flexes.
Question 33AgilePM fundamentals and the Agile Project Management approach
In AgilePM, what does the 'timebox' concept fix while allowing scope to flex?
- The duration of the delivery period Correct answer.
- The acceptance criteria of each requirement
- The cost and the number of developers
- The technical architecture of the solution
Explanation
A timebox is a fixed period of time, typically a fixed duration, within which the team delivers as much of the prioritised scope as possible. Scope is the variable that is adjusted, not the time.
Question 34AgilePM fundamentals and the Agile Project Management approach
A project is in its second delivery timebox when the Business Visionary asks for a new feature to be added. What is the most appropriate AgilePM response?
- Refuse the request outright because scope cannot change during delivery
- Extend the current timebox so the feature can be included
- Record the request and consider it for prioritisation in a future timebox, keeping the current one stable Correct answer.
- Add the feature to the current timebox immediately because the Visionary requests it
Explanation
Timeboxes are protected from scope changes so the team can deliver a coherent increment on time. New requirements are captured and prioritised for a subsequent timebox rather than injected mid-timebox.
Question 35AgilePM fundamentals and the Agile Project Management approach
Which AgilePM product defines the objectives, scope and constraints of a single delivery timebox?
- Stage Plan
- Project Plan
- Timebox Plan Correct answer.
- Delivery Plan
Explanation
The Timebox Plan is produced for each timebox and sets out its objectives, the requirements to be delivered, and the resources and activities involved. It is the lowest-level planning product in AgilePM.
Question 36AgilePM fundamentals and the Agile Project Management approach
A team leader notices that a Solution Tester is also acting as a Business Ambassador for some requirements. Why is this combination problematic in AgilePM?
- It means the timebox cannot be baselined
- It breaches the rule that no role may be combined
- It prevents the tester from writing acceptance criteria
- It removes independent verification of the solution's fitness for purpose Correct answer.
Explanation
The Business Ambassador represents the business view of what is needed and confirms fitness for purpose, while the Solution Tester verifies the solution against acceptance criteria. Combining them removes the separation that gives assurance.
Question 37AgilePM fundamentals and the Agile Project Management approach
Which statement best describes how AgilePM treats the traditional 'big design up front' approach?
- It requires a complete design to be signed off before any delivery timebox starts
- It designs only at the end of the project during deployment
- It rejects all up-front design in favour of emerging design only
- It does enough up-front work in Foundations to establish a sound basis, then evolves the solution iteratively Correct answer.
Explanation
AgilePM takes a 'just enough' approach: sufficient architecture and foundations are established early, and design is then refined as understanding grows through delivery. It avoids both exhaustive up-front design and the absence of any foundation.
Question 38AgilePM fundamentals and the Agile Project Management approach
During a timebox, the team finds that a requirement marked as Must-have cannot be delivered as specified, but a simpler alternative would meet the business intent. What should happen first?
- The timebox is abandoned and restarted
- The simpler alternative is implemented without discussion
- The team raises the issue with the Business Ambassador and Business Visionary to agree the acceptable alternative Correct answer.
- The Must-have is dropped and a Could-have is delivered instead
Explanation
Must-haves define the minimum usable subset, so the business roles must agree whether an alternative satisfies that intent before the team proceeds. This keeps the business in control of what 'must' means.
Question 39AgilePM fundamentals and the Agile Project Management approach
What is the main purpose of the Daily Stand-up in an AgilePM delivery timebox?
- To obtain sign-off on completed requirements
- To let the team coordinate its work and surface impediments Correct answer.
- To re-estimate the whole project schedule
- To report detailed progress to the Project Manager
Explanation
The Daily Stand-up is a short, team-led event for coordinating work, sharing progress and raising blockers. It is not a reporting forum for management or a sign-off meeting.
Question 40AgilePM fundamentals and the Agile Project Management approach
Which AgilePM product records the justification for the project, the expected benefits and the key risks, and is updated at defined points?
- Vision Statement
- Benefits Assessment
- Business Case Correct answer.
- Risk Log
Explanation
The Business Case captures the justification, costs, benefits and risks, and it is reviewed and updated at defined points such as the end of each timebox. This keeps the investment decision live rather than a one-off approval.
Question 41AgilePM fundamentals and the Agile Project Management approach
A Project Manager wants to reduce documentation to the minimum. Which AgilePM principle best supports this aim while retaining control?
- Be collaborative
- Put the emphasis on the product rather than the process Correct answer.
- Demonstrate control
- Deliver on time
Explanation
Emphasising the product over the process means focusing on delivering a valuable working solution and producing only the documentation needed to support it. Control is maintained through the other principles and products rather than through volume of paperwork.
Question 42AgilePM fundamentals and the Agile Project Management approach
In AgilePM, what is the purpose of the Deployed stage?
- To define the project's initial requirements
- To close the business case permanently
- To confirm the solution is ready for operational use and to hand it over Correct answer.
- To build the first working increment
Explanation
The Deployed stage covers the activities needed to move the solution into operational use and hand it over to the business, including any final acceptance. It follows the delivery timeboxes.
Question 43AgilePM fundamentals and the Agile Project Management approach
A Business Visionary is unsure whether a proposed requirement adds real value. Which AgilePM practice best addresses this?
- Estimating the requirement's development effort first
- Adding the requirement to the next timebox as a Must-have
- Deferring all discussion until the post-project review
- Agreeing acceptance criteria and prioritising the requirement with the business roles Correct answer.
Explanation
Value is clarified by agreeing what fitness for purpose looks like through acceptance criteria and by assigning an appropriate MoSCoW priority with the business roles. Effort estimation alone does not establish value.
Question 44AgilePM fundamentals and the Agile Project Management approach
Which pair of AgilePM principles most directly addresses keeping the team focused on the highest-value work at all times?
- Be collaborative and Never compromise quality
- Focus on the business need and Prioritise to deliver on time Correct answer.
- Build incrementally and Be collaborative
- Deliver on time and Demonstrate control
Explanation
Focusing on the business need ensures effort targets genuine value, and prioritising to deliver on time ensures the most important requirements are completed first within fixed time. Together they direct attention to the highest-value work.
Question 45AgilePM fundamentals and the Agile Project Management approach
A project's delivery timeboxes are progressing, but the Business Sponsor is concerned that the business environment has shifted since Foundations. What does AgilePM expect to happen?
- Continue unchanged until the end of the project
- Review the business case and vision with the business roles and decide whether to adjust or stop Correct answer.
- Re-run the Foundations stage from the beginning
- Immediately terminate the project
Explanation
AgilePM keeps the business case and vision under review so that the project can respond to a changing environment, including the option to stop if the justification no longer holds. The decision is taken deliberately with the business roles.
Question 46AgilePM fundamentals and the Agile Project Management approach
In AgilePM, why is the Technical Coordinator positioned between the project management team and the solution development team?
- To manage the project budget and schedule
- To ensure the solution architecture and technical integrity are coordinated across teams Correct answer.
- To act as the customer representative for acceptance
- To approve all business priorities on behalf of the sponsor
Explanation
The Technical Coordinator provides technical leadership and ensures the architecture and technical coherence of the solution across the development effort. This bridges business direction and technical delivery.
Question 47AgilePM fundamentals and the Agile Project Management approach
A team is deciding how much of the solution to design in Foundations versus during delivery. Which AgilePM guidance applies?
- Provide sufficient architecture in Foundations to reduce risk, and elaborate the design iteratively during timeboxes Correct answer.
- Defer all design decisions until the Deployed stage
- Let each developer design independently without coordination
- Design everything in Foundations so delivery can be purely mechanical
Explanation
Foundations should establish enough of the solution architecture to give confidence and reduce major risk, with detailed design emerging iteratively during delivery. This balances the need for a sound basis against the cost of premature detail.
Question 48AgilePM fundamentals and the Agile Project Management approach
During a timebox review, the Business Ambassador accepts most requirements but rejects one as not fit for purpose. What is the most appropriate AgilePM outcome?
- The rejection is overridden by the Project Manager
- The requirement is returned for rework or re-prioritisation in a subsequent timebox Correct answer.
- The requirement is accepted because the timebox has ended
- The whole timebox is declared failed and repeated in full
Explanation
The timebox review confirms which requirements meet their acceptance criteria; those that do not are handled by rework or by re-prioritisation into a later timebox. The whole timebox is not invalidated by one rejected requirement.
Question 49AgilePM fundamentals and the Agile Project Management approach
An organisation wants strong control but fears that AgilePM's flexibility will undermine governance. Which feature of AgilePM best reconciles these concerns?
- Relying solely on the Daily Stand-up for progress reporting
- Removing formal products to speed up decision-making
- Allowing the team to set its own priorities without business involvement
- Defined products, roles and review points at timebox and stage boundaries that provide control without heavy process Correct answer.
Explanation
AgilePM provides explicit products, clearly defined roles and regular review points at timebox and stage boundaries, which give governance and visibility while allowing scope to flex. Control comes from these defined mechanisms rather than from heavyweight documentation.
Question 50AgilePM fundamentals and the Agile Project Management approach
In AgilePM, which statement describes how the DSDM timeboxing technique handles the MoSCoW priorities during a single timebox?
- Priorities are fixed only at the start of the project and cannot be revisited per timebox
- Should-haves are guaranteed delivery and Must-haves may be deferred to a later timebox
- All Must-haves must be delivered, while Could-haves are dropped first if time runs short Correct answer.
- All requirements in the timebox must be delivered to their full original specification
Explanation
Timeboxing fixes the duration of the timebox and protects the Must-have requirements, with lower priorities flexed to fit the available time. Should-haves are included where possible, Could-haves are sacrificed first, and Won't-haves are excluded. This is how scope flexes while the deadline is protected.