PMI Agile Certified Practitioner (PMI-ACP) — All Questions
20 questions
The Agile Manifesto values 'responding to change' over:
- a.Working software
- b.Following a plan✓
- c.Customer collaboration
- d.Individuals and interactions
The Manifesto values responding to change over following a plan.
Empirical process control in agile is based on:
- a.Transparency, inspection, and adaptation✓
- b.Fixed long-term plans
- c.Detailed upfront documentation
- d.Command-and-control management
Empiricism relies on transparency, inspection, and adaptation.
Short iterations primarily provide:
- a.Longer planning horizons
- b.Less stakeholder involvement
- c.Frequent feedback to adapt quickly✓
- d.Fewer releases
Short iterations create frequent feedback loops enabling adaptation.
A 'servant leader' in agile primarily:
- a.Assigns all tasks personally
- b.Enforces strict schedules
- c.Reports team members' mistakes
- d.Removes impediments and supports the team✓
Servant leaders serve the team by clearing obstacles and enabling self-organization.
Which items should generally be delivered first in agile?
- a.The easiest items regardless of value
- b.The highest-value and highest-risk items✓
- c.The items with the most documentation
- d.Items chosen alphabetically
Delivering high-value, high-risk items early maximizes value and reduces risk.
Frequent small releases mainly enable:
- a.Early return on investment and faster feedback✓
- b.Longer feedback cycles
- c.More upfront planning
- d.Reduced customer involvement
Incremental delivery yields early ROI and faster learning.
WSJF (Weighted Shortest Job First) is used to:
- a.Estimate team velocity
- b.Assign blame for defects
- c.Prioritize work by cost of delay and size✓
- d.Measure code coverage
WSJF prioritizes by dividing cost of delay by job size.
A Minimum Viable Product (MVP) is:
- a.The final, fully-featured release
- b.A detailed requirements document
- c.A long-term roadmap
- d.The smallest release that delivers value and enables learning✓
An MVP delivers just enough to provide value and validate assumptions.
An 'information radiator' such as a task board is used to:
- a.Hide progress from stakeholders
- b.Make progress and information highly visible✓
- c.Replace all meetings
- d.Track individual performance for reviews
Information radiators make status transparent to everyone.
The main purpose of an iteration review (demo) is to:
- a.Get feedback on the increment from stakeholders✓
- b.Assign blame for missed work
- c.Plan the next year in detail
- d.Finalize contracts
Reviews gather stakeholder feedback on the working increment.
When stakeholder priorities change mid-project, an agile team should:
- a.Refuse changes until the project ends
- b.Ignore the change
- c.Re-prioritize the backlog collaboratively✓
- d.Cancel the project
Agile welcomes change; the team re-prioritizes the backlog with stakeholders.
Effective agile communication favors:
- a.Lengthy status reports only
- b.Formal sign-offs for every task
- c.Communication only at project end
- d.Frequent face-to-face or high-bandwidth conversation✓
Agile prefers frequent, high-bandwidth communication.
An agile team that is 'self-organizing' means the team:
- a.Has no accountability
- b.Decides how to accomplish its work✓
- c.Works without any goals
- d.Is managed task-by-task by a boss
Self-organizing teams choose how best to accomplish their work.
Velocity should be used to:
- a.Help a team forecast its own future capacity✓
- b.Compare one team against another
- c.Set individual performance bonuses
- d.Replace the product backlog
Velocity is a team's own forecasting tool, not a cross-team comparison metric.
A cross-functional team is one that:
- a.Contains only developers
- b.Reports to multiple managers
- c.Has all the skills needed to deliver the work✓
- d.Never changes its members
Cross-functional teams hold the skills needed to deliver value end to end.
The primary purpose of a retrospective is to:
- a.Demo the product
- b.Plan the release
- c.Estimate the backlog
- d.Inspect and improve the team's own process✓
Retrospectives help the team continuously improve how it works.
'Progressive elaboration' in agile planning means:
- a.Planning everything in detail upfront
- b.Refining plans in more detail as more is known✓
- c.Never planning
- d.Planning only once
Plans are elaborated progressively as understanding grows.
A burndown chart shows:
- a.Work remaining over time✓
- b.Team salaries
- c.The number of meetings
- d.Defect severity only
A burndown chart tracks remaining work across the iteration.
Agile planning happens at multiple levels, typically including:
- a.Only a single project plan
- b.Only daily plans
- c.Release, iteration, and daily planning✓
- d.A ten-year fixed plan
Agile plans at release, iteration, and daily horizons.
A daily standup helps detect problems by:
- a.Providing a detailed status report to managers
- b.Replacing the retrospective
- c.Assigning new tasks from a manager
- d.Surfacing impediments and progress every day✓
The daily standup surfaces impediments and coordinates the team quickly.