PMP (Project Management Professional) Agile & Hybrid Approaches – MCQs
Questions across 3 chapters of PMP (Project Management Professional) Agile & Hybrid Approaches. Pick a chapter, read sample questions with answers, then take a free test. Available in English.
📚 Chapters
✅ Practice questions with answers
The Agile Manifesto values individuals and interactions over:
- responding to change
- working software
- customer collaboration
- processes and tools
Show answer
Answer: D — processes and tools
Value 1.
How to solve:Agile Manifesto: 4 values, 12 principles. Scrum (2020 guide): accountabilities Product Owner, Scrum Master, Developers; events Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective; artefacts Product Backlog (Product Goal), Sprint Backlog (Sprint Goal), Increment (Definition of Done).
A user story is typically written as:
Agile Planning, Estimation & Metrics
- The system shall...
- Task 1, Task 2
- As a <role>, I want <goal> so that <benefit>
- Requirement number 123
Show answer
Answer: C — As a <role>, I want <goal> so that <benefit>
Story format.
How to solve:User stories (As a... I want... so that...), INVEST, story points (relative, Fibonacci), planning poker, velocity, burndown/burnup charts, Kanban (visualise work, limit WIP, manage flow), cumulative flow diagram, cycle time, lead time, MVP.
A project has fixed regulatory requirements for construction and evolving software requirements. The BEST approach is:
- no approach
- hybrid — predictive for construction and agile for software
- pure waterfall for everything
- pure Scrum for everything
Show answer
Answer: B — hybrid — predictive for construction and agile for software
Hybrid.
How to solve:Choose the approach based on uncertainty, risk, regulation, team and stakeholders. Hybrid: e.g. predictive for hardware/compliance and agile for software. Tailor processes, ceremonies and documents. Use agile suitability filters; SAFe/LeSS for scaling.
The Agile Manifesto values working software over:
- individuals
- change
- comprehensive documentation
- collaboration
Show answer
Answer: C — comprehensive documentation
Value 2.
How to solve:Agile Manifesto: 4 values, 12 principles. Scrum (2020 guide): accountabilities Product Owner, Scrum Master, Developers; events Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective; artefacts Product Backlog (Product Goal), Sprint Backlog (Sprint Goal), Increment (Definition of Done).
INVEST criteria for user stories stand for:
Agile Planning, Estimation & Metrics
- Important, New, Valuable, Easy, Simple, Timed
- Independent, Negotiable, Valuable, Estimable, Small, Testable
- Integrated, Necessary, Verified, Estimated, Scoped, Tracked
- none of these
Show answer
Answer: B — Independent, Negotiable, Valuable, Estimable, Small, Testable
INVEST.
How to solve:User stories (As a... I want... so that...), INVEST, story points (relative, Fibonacci), planning poker, velocity, burndown/burnup charts, Kanban (visualise work, limit WIP, manage flow), cumulative flow diagram, cycle time, lead time, MVP.
Factors that favour an agile approach include:
- high requirement uncertainty, frequent customer feedback and a co-located empowered team
- fixed and fully known scope
- no customer access
- strict sequential regulation only
Show answer
Answer: A — high requirement uncertainty, frequent customer feedback and a co-located empowered team
Suitability.
How to solve:Choose the approach based on uncertainty, risk, regulation, team and stakeholders. Hybrid: e.g. predictive for hardware/compliance and agile for software. Tailor processes, ceremonies and documents. Use agile suitability filters; SAFe/LeSS for scaling.
The Agile Manifesto values customer collaboration over:
- working software
- contract negotiation
- individuals
- responding to change
Show answer
Answer: B — contract negotiation
Value 3.
How to solve:Agile Manifesto: 4 values, 12 principles. Scrum (2020 guide): accountabilities Product Owner, Scrum Master, Developers; events Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective; artefacts Product Backlog (Product Goal), Sprint Backlog (Sprint Goal), Increment (Definition of Done).
Story points measure:
Agile Planning, Estimation & Metrics
- relative size or effort of work
- exact hours
- number of developers
- cost in dollars
Show answer
Answer: A — relative size or effort of work
Relative estimate.
How to solve:User stories (As a... I want... so that...), INVEST, story points (relative, Fibonacci), planning poker, velocity, burndown/burnup charts, Kanban (visualise work, limit WIP, manage flow), cumulative flow diagram, cycle time, lead time, MVP.
Factors that favour a predictive approach include:
- frequent change
- innovation with unknown scope
- customer wants to discover needs
- stable requirements, high regulation and low uncertainty
Show answer
Answer: D — stable requirements, high regulation and low uncertainty
Predictive fit.
How to solve:Choose the approach based on uncertainty, risk, regulation, team and stakeholders. Hybrid: e.g. predictive for hardware/compliance and agile for software. Tailor processes, ceremonies and documents. Use agile suitability filters; SAFe/LeSS for scaling.
The Agile Manifesto values responding to change over:
- following a plan
- customer collaboration
- individuals
- working software
Show answer
Answer: A — following a plan
Value 4.
How to solve:Agile Manifesto: 4 values, 12 principles. Scrum (2020 guide): accountabilities Product Owner, Scrum Master, Developers; events Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective; artefacts Product Backlog (Product Goal), Sprint Backlog (Sprint Goal), Increment (Definition of Done).
💡 How to practise
- Read each rule (UCP 600, ISBP, URDG, ISP98) article by article and practise the matching chapter.
- Case-scenario questions test how rules work together — review every explanation.
- Take a timed exam to get used to answering under pressure.
- Repeat chapters where you score below 75%.