Examius
🇺🇸 Certified Associate in Project Management (CAPM) · flashcards
Certified Associate in Project Management (CAPM) Business Analysis Frameworks and Practices Flashcards
57 question-and-answer cards covering Business Analysis Frameworks and Practices as it is examined in Certified Associate in Project Management (CAPM). 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.
24 sample cards from the Business Analysis Frameworks and Practices deck
Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.
What is a use case?
A description of how an actor (user or system) interacts with the solution to achieve a specific goal, including the main flow and alternative/exception flows.
What is a context diagram used to model?
The scope boundary of a system, showing the solution as a single process and its interactions (data flows) with external entities such as users and other systems.
Why is prioritizing requirements important?
Because time, budget, and resources are limited; prioritization ensures the most valuable and critical requirements are delivered first and guides scope and trade-off decisions.
What does the MoSCoW prioritization technique stand for?
Must have, Should have, Could have, and Won't have (this time).
Name two requirements prioritization techniques besides MoSCoW.
Numerical/weighted ranking, voting (e.g., dot voting), the Kano model, time-boxing/budgeting, and value-vs-effort (priority/cost) analysis.
What does it mean to validate requirements?
To confirm that the requirements deliver the intended business value and align with business goals and objectives—ensuring you are building the right thing.
What is the difference between verifying and validating requirements?
Verification checks that requirements are well-formed and meet quality standards (built right); validation checks that they deliver business value and meet the actual need (right thing built).
What is a requirements traceability matrix (RTM)?
A table that links requirements to their origin, to one another, and to deliverables/tests, ensuring each requirement is accounted for and traceable from need to solution.
What is the purpose of managing requirements changes?
To control modifications to baselined requirements through a defined process so impacts on scope, cost, schedule, and quality are assessed, approved, and communicated.
What is a baseline in requirements management?
An approved, formally agreed-upon version of the requirements that serves as the reference point; changes after baselining must go through change control.
What role does a change control board (CCB) play in requirements changes?
It reviews requested changes to baselined requirements, assesses their impact, and formally approves, defers, or rejects them.
What is impact analysis in the context of requirements change?
Assessing how a proposed change affects scope, schedule, cost, quality, other requirements, and stakeholders before deciding whether to approve it.
What does it mean to validate a solution against requirements?
Confirming through testing, inspection, or demonstration that the delivered solution actually meets the documented and approved requirements.
What are acceptance criteria?
The predefined, measurable conditions a solution or deliverable must satisfy to be accepted by stakeholders; they define 'done' and the basis for sign-off.
How is evaluating solution performance different from validating requirements?
Validating requirements confirms the solution meets stated requirements; evaluating solution performance measures, after deployment, whether the solution actually delivers the expected business value and benefits in operation.
What is solution sign-off (acceptance)?
The formal approval by authorized stakeholders confirming the solution meets acceptance criteria and requirements, authorizing transition/release and closure of the work.
What does the BA do to support solution transition?
Identify and manage transition requirements—such as training, data migration, documentation, and cutover—to ensure smooth movement from the current state to the new solution in operation.
What is a product roadmap and how do BAs use it?
A high-level, time-oriented plan showing the planned evolution and major releases/features of a product over time; BAs use it to align stakeholders on priorities, vision, and the sequence of value delivery.
What is a product backlog and how is it managed?
An ordered, prioritized list of all desired work/features (often as user stories) for a product; it is managed by continuously refining (grooming), prioritizing, estimating, and reordering items based on value and changing needs.
What is backlog refinement (grooming)?
The ongoing activity of reviewing backlog items to add detail, estimates, and acceptance criteria, splitting large items, and re-prioritizing so items are ready for upcoming work.
What is a user story and what format is commonly used?
A short, user-centered description of a requirement, commonly written as: 'As a [role], I want [goal] so that [benefit].'
What does measuring business value delivered by a solution involve?
Comparing actual outcomes and benefits realized against the original business goals, objectives, and expected value—often using metrics, KPIs, and benefit realization analysis.
Name two common metrics used to quantify business value of a solution.
Return on investment (ROI), net present value (NPV), payback period, cost savings, revenue increase, customer satisfaction, and cycle-time reduction (any two).
What is benefits realization and when does it typically occur?
The process of ensuring and measuring that the expected business benefits of a solution are actually achieved; it often occurs after deployment, sometimes beyond formal project closure, during operations.
What this deck covers
The Business Analysis Frameworks and Practices deck follows the Certified Associate in Project Management (CAPM) Business Analysis Frameworks and Practices syllabus — 4 chapters and 18 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 14.3 cards per chapter.
Answers are written to be recallable, not just readable — averaging about 165 characters, which is long enough to carry the reasoning and short enough to say out loud.
A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.
Business Analysis Frameworks and Practices flashcards FAQ
How many Business Analysis Frameworks and Practices flashcards are in this Certified Associate in Project Management (CAPM) deck?
57 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.
Are these Certified Associate in Project Management (CAPM) flashcards free?
Yes. The preview here is free to read with no signup, and the full 57-card deck is free inside the Examius app.
What do the Business Analysis Frameworks and Practices cards cover?
They follow the Certified Associate in Project Management (CAPM) Business Analysis Frameworks and Practices syllabus — 4 chapters and 18 topics — so the questions track what is actually examinable.
How should I use these flashcards?
Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.