CAPM Domain 4: Business Analysis Frameworks & Requirements

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/58

encourage image

There's no tags or description

Looks like no tags are added yet.

59 Terms

1
New cards

What is business analysis (BA) in project work?

The work of identifying business needs, understanding stakeholder needs, defining requirements, and helping determine whether a solution delivers value.

2
New cards

How is a Business Analyst's role different from a Project Manager's?

The BA focuses on needs, requirements, and solution value. The PM focuses on planning, coordinating, and managing project work to meet objectives and constraints.

3
New cards

How is a Business Analyst different from a Product Owner?

A BA elicits, analyzes, documents, and manages requirements. A Product Owner is accountable for maximizing product value and ordering the product backlog.

4
New cards

What is a needs assessment?

A structured process for identifying a business problem or opportunity, understanding the current and desired state, and determining whether action is justified.

5
New cards

What is a business need?

The problem, opportunity, or gap that creates a reason for change.

6
New cards

Why should a team define the business need before choosing a solution?

To avoid jumping to a solution that may not address the real problem; understanding the need allows appropriate alternatives to be evaluated.

7
New cards

What is a business case?

A justification for undertaking an initiative, describing the business need, expected benefits, costs, risks, and rationale for investment.

8
New cards

How is a business case different from a project charter?

The business case justifies why the initiative is worthwhile. The project charter formally authorizes the project and gives the PM authority to use organizational resources.

9
New cards

What is a business strategy?

The organization's broad direction and approach for achieving its long-term goals.

10
New cards

What is requirements elicitation?

The process of drawing out, discovering, and confirming stakeholder needs and requirements using appropriate techniques.

11
New cards

What is an interview useful for in elicitation?

Exploring an individual stakeholder's needs, motivations, details, and concerns through direct questions and follow-up.

12
New cards

What is a workshop useful for?

Bringing multiple stakeholders together to discuss, clarify, prioritize, and resolve requirements collaboratively.

13
New cards

What is observation (job shadowing) useful for?

Seeing how users actually perform work, including tacit steps or workarounds they may not report in an interview.

14
New cards

What are surveys or questionnaires useful for?

Collecting structured input from many stakeholders efficiently, especially when they are distributed.

15
New cards

What is document analysis?

Reviewing existing policies, procedures, forms, reports, or system documentation to understand current processes and requirements.

16
New cards

What should a BA do when stakeholders provide conflicting requirements?

Understand the underlying needs, facilitate discussion, assess impacts and value, and help stakeholders reach a documented resolution using agreed decision authority.

17
New cards

What is a stakeholder requirement?

A statement of a stakeholder's need or expectation that must be addressed for the stakeholder to achieve their objective.

18
New cards

What is a solution requirement?

A capability or quality the solution must have to meet business and stakeholder requirements.

19
New cards

What is a functional requirement?

A description of a behavior, function, or service the solution must provide.

20
New cards

What is a nonfunctional requirement?

A quality or constraint describing how well the solution must perform, such as security, reliability, usability, or response time.

21
New cards

What is a transition requirement?

A temporary requirement needed to move from the current state to the future state, such as data conversion or user training.

22
New cards

What is requirements traceability?

The ability to link each requirement to its source, business objective, related deliverables, and verification or validation activity throughout the lifecycle.

23
New cards

What is a requirements traceability matrix (RTM)?

A tool used to track the requirements throughout the project lifecycle, ensuring all requirements are addressed.

24
New cards

What is requirements verification?

Checking that requirements are written correctly, clearly, consistently, and in a way that can be tested.

25
New cards

What is requirements validation?

Checking that the requirements represent the actual stakeholder and business needs.

26
New cards

What are acceptance criteria?

Specific, measurable conditions that a solution or requirement must satisfy for stakeholders to accept it.

27
New cards

What is a product roadmap?

A high-level view of product direction, goals, and planned capabilities or outcomes over time; it is not a detailed task schedule.

28
New cards

What is release planning?

Deciding which features or capabilities are targeted for a release, considering value, dependencies, risk, and capacity.

29
New cards

How is a product roadmap different from a project schedule?

A roadmap communicates high-level product direction and outcomes. A project schedule lays out activities, dependencies, durations, and dates.

30
New cards

What is requirements prioritization?

Ordering requirements based on factors such as business value, urgency, risk, dependencies, cost, and stakeholder needs.

31
New cards

What is the MoSCoW prioritization method?

Must have, Should have, Could have, and Won't have (this time). It helps distinguish essential requirements from lower-priority items.

32
New cards

What does 'Must have' mean in MoSCoW?

A requirement essential for the solution or release to be viable; without it, the intended outcome cannot be achieved.

33
New cards

What does 'Won't have this time' mean in MoSCoW?

The requirement is deliberately excluded from the current scope or release, though it may be reconsidered later.

34
New cards

What is an MVP in business analysis/product work?

The smallest usable solution that can test a key assumption or deliver enough value to obtain meaningful feedback.

35
New cards

What is solution evaluation?

Assessing a delivered or existing solution to determine how well it meets needs, creates value, and performs against expected outcomes.

36
New cards

What is a solution limitation?

A condition or shortcoming that prevents a solution from fully meeting a need or delivering expected value.

37
New cards

How can a BA evaluate whether a solution delivered value?

Compare actual outcomes and performance with the business objectives, expected benefits, and relevant measures; gather stakeholder feedback and identify gaps.

38
New cards

What is a requirements change's likely impact?

It may affect scope, design, cost, schedule, risk, testing, dependencies, and expected benefits; analyze impacts before approving or implementing it.

39
New cards

What should a BA do first when a department requests a new software platform?

Clarify the underlying business need, current state, desired state, and gap before assuming that the requested platform is the right solution.

40
New cards

What kind of requirement is 'The system must respond in under two seconds'?

A nonfunctional requirement: it specifies a performance quality rather than a function the system performs.

41
New cards

Which activity failed if a requirement is grammatically clear and testable, but users say it does not solve their problem?

Requirements validation.

42
New cards

Which tool helps identify connections when a proposed change affects several requirements and test cases?

The requirements traceability matrix (RTM), which links requirements to related objectives, deliverables, and tests.

43
New cards

Which activity is deciding which capabilities belong in the next release?

Release planning, supported by prioritization of requirements based on value, dependencies, risk, and capacity.

44
New cards

What method fits when classifying requirements as essential, important, optional, or excluded from this release?

MoSCoW: Must have, Should have, Could have, and Won't have this time.

45
New cards

What should a BA evaluate if a project finished on time, but the new solution did not improve the business outcome?

Evaluate solution performance and actual benefits against the business objectives and expected value; identify the gap and possible improvements.

46
New cards

What is the business need?

Why change / what problem.

47
New cards

What is the business case?

Why invest.

48
New cards

What authorizes a project?

Charter.

49
New cards

What ensures the right requirements?

Validation.

50
New cards

What checks if requirements are written correctly?

Verification.

51
New cards

What defines what it does?

Functional.

52
New cards

What defines how well or quality?

Nonfunctional.

53
New cards

What is a temporary transition requirement?

Transition requirement.

54
New cards

What helps trace links and impact?

RTM.

55
New cards

What provides high-level product direction?

Roadmap.

56
New cards

What defines release contents?

Release planning.

57
New cards

What categorizes requirements as essential, important, optional, or excluded now?

MoSCoW.

58
New cards

What evaluates if the solution delivered outcomes?

Solution evaluation.

59
New cards

When you see a Business Analysis scenario, ask yourself

1. What is the real business need?

2. Who has the relevant role or decision authority?

3. What technique would best gather or clarify the information?

4. Are we defining the right requirements, or checking their quality?

5. Does the solution actually deliver the intended value?