PMI-PBA : Needs Assessment (Domain 1)
PMI – PMI-PBA : Certified Professional in Business Analysis - Domain 1 - Needs Assessment
The Needs Assessment domain represents a critical foundational phase in the business analysis lifecycle, accounting for approximately 18% to 20% of the PMI Professional in Business Analysis (PMI-PBA) examination content. This domain focuses on the systematic identification of business problems or opportunities, the evaluation of the organizational environment, and the determination of viable solutions that align with strategic objectives. Historically, organizational failure rates have been linked to inaccurate requirements gathering and flawed front-end analysis, making Needs Assessment a dominant factor in project delivery success. While standard project management frameworks prioritize metrics like schedule compliance and cost variances, business analysis operates at the strategic intersection of project delivery and organizational value. It ensures that solutions address validated problems, align with strategic business architecture, and achieve documented benefits.
1. The Strategic Importance of Needs Assessment
Needs Assessment ensures that organizations invest resources in viable initiatives that address genuine root causes rather than surface-level symptoms. The domain is designed to guide practitioners through the process of analyzing the current state, defining the desired future state, and identifying the gaps that must be bridged to achieve business goals.
The value proposition of this domain lies in its ability to steer complex projects away from scope creep and toward value-driven delivery. By conducting a thorough assessment before a project is fully initiated, business analysts can validate that the proposed solution is the most effective way to address a business need. This involves high-level analysis and management, such as setting appropriate standards and ensuring that the solution aligns with the organization’s strategic roadmap.
2. Defining Business Problems and Opportunities
The primary task in Needs Assessment involves defining or reviewing a business problem or opportunity. This process requires the business analyst to separate actual business issues from requested solutions. Often, stakeholders propose a specific solution without fully understanding the underlying problem. The business analyst utilizes various techniques to clarify the solution scope and provide input for the development of a business case.
Effective problem and opportunity analysis techniques include:
- Brainstorming: Used to generate a wide range of ideas and potential issues.
- Benchmarking: Comparing organizational processes against industry best practices.
- Scenario Analysis: Evaluating different potential future states to understand the impact of various decisions.
- Process Modeling: Visualizing current workflows to identify inefficiencies or gaps.
The result of this task is a solution scope statement that provides a clear boundary for the initiative, ensuring that all subsequent requirements gathering remains focused on the validated need.
3. Information Collection and the Value Proposition
Once a problem or opportunity is defined, the business analyst must collect and analyze information from a variety of sources to contribute to the initiative’s value proposition. This involves assessing the organizational state and evaluating potential solution options. Valuation tools and techniques are used to validate the strategic fit and potential of the initiative.
Key valuation tools include:
- Cost-Benefit Analysis: Comparing the expected costs of a solution against the anticipated benefits.
- Feasibility Metrics: Assessing whether a solution is technically, operationally, and economically viable.
- Force Field Analysis: Identifying the forces that support or oppose a proposed change.
By applying these techniques, the business analyst ensures that the organization understands the potential return on investment and the strategic value of proceeding with a particular project.
4. Establishing SMART Goals and Strategic Alignment
A core responsibility within Needs Assessment is collaborating in the development of project goals and objectives. This ensures that the product or solution is aligned with the organization’s high-level strategy. Business analysts must ensure that objectives are not only clear but also measurable and achievable.
To achieve this, practitioners often use specific guidelines:
- SMART Goals: Objectives should be Specific, Measurable, Achievable, Relevant, and Time-bound.
- OKRs (Objectives and Key Results): A framework for defining and tracking objectives and their outcomes.
- FRAME Approach: Ensuring objectives are Few, Realistic, Agreed, Measured, and Explicit.
By refining goals using these frameworks, the business analyst provides a roadmap for the project team, ensuring that the solution delivered will meet the business need and provide the intended value.
5. Stakeholder Identification and Analysis
Identifying the correct stakeholders is vital to ensure that all appropriate parties are represented, informed, and involved throughout the project lifecycle. The business analyst reviews goals, objectives, and requirements to determine who has an interest in the outcome or who may be affected by the change.
Stakeholders can vary significantly in their influence, communication needs, and acceptance criteria. A thorough identification process prevents the late discovery of requirements, which is a common cause of project delays. The analysis of stakeholders involves understanding their roles and responsibilities, which will later inform the requirements management plan. This ensures that the project team engages with the right people at the right time to gather accurate information and secure necessary approvals.
6. Determining Stakeholder Values
After identifying stakeholders, the business analyst must determine their values regarding the product. Using elicitation techniques, the analyst gathers information to provide a baseline for prioritizing requirements. This step is critical because different stakeholders often have conflicting priorities.
Understanding stakeholder values allows the business analyst to facilitate consensus and ensure that the most critical needs are addressed first. This process provides a foundation for balancing scope, schedule, and budget constraints against the value proposition. It also ensures that the final solution meets the expectations of those who will ultimately use and benefit from it.
7. Root Cause Analysis: Fishbone Diagrams and the 5 Whys
Root cause analysis (RCA) is a fundamental skill in Needs Assessment, used to identify the underlying cause of a stakeholder complaint or a business inefficiency. By getting to the heart of an issue, the business analyst avoids proposing “band-aid” solutions that only address symptoms.
Two primary tools for RCA are:
- Ishikawa (Fishbone) Diagrams: A visualization tool used to categorize the potential causes of a problem to identify its root origin. It helps teams brainstorm and organize complex relationships between causes.
- 5 Whys: A simple iterative technique where the analyst asks “Why?” repeatedly (usually five times) to peel away layers of symptoms and reach the root cause of a problem.
These tools are essential for defining the problem statement accurately and ensuring that the proposed solution scope actually solves the business issue.
8. Strategic Analysis with SWOT and Benchmarking
To understand the organizational environment, business analysts use strategic tools like SWOT analysis. This technique involves evaluating:
- Strengths: Internal attributes that give the organization an advantage.
- Weaknesses: Internal attributes that place the organization at a disadvantage.
- Opportunities: External factors that the organization could exploit to its advantage.
- Threats: External factors that could cause trouble for the organization.
Complementing SWOT, Benchmarking allows the organization to see how it performs relative to competitors or industry standards. These techniques help the business analyst determine whether a project is a good strategic fit and identify potential risks or advantages that should be considered during the development of the business case.
9. Prioritization Models: Kano and Purpose Alignment
In the Needs Assessment phase, it is crucial to understand how different product features or requirements contribute to stakeholder satisfaction and strategic goals.
- Kano Model: This tool categorizes requirements based on how they affect customer satisfaction. It distinguishes between basic needs (must-haves), performance needs (satisfiers), and excitement needs (delighters). This helps the business analyst prioritize features that will provide the most value and impact.
- Purpose Alignment Matrix: This matrix helps in determining the strategic importance of an initiative by assessing whether a feature is a “differentiator” (provides competitive advantage) or “mission-critical” (necessary for operations but not a source of advantage). It provides a framework for deciding whether to invest heavily in a custom solution or seek a standard, cost-effective approach.
10. Modeling the Environment: Context Diagrams and Ecosystem Maps
Visualizing the scope and the organizational environment is a key task in Needs Assessment. These models help stakeholders understand the boundaries of the solution and how it interacts with other systems and entities.
- Context Diagrams: A high-level diagram that shows a system in its environment, including the external entities (users, other systems, or departments) that interact with it and the data flows between them. It is an essential tool for defining solution scope.
- Ecosystem Maps: A broader visualization that shows the entire environment in which a solution will operate. It identifies the relationships between different systems, platforms, and stakeholders across the organization, helping to identify potential dependencies and integration points.
Short-Answer Questions
1. What is the primary focus of the Needs Assessment domain in business analysis? The focus is on identifying business problems or opportunities, understanding the organizational environment, and evaluating potential solutions to ensure they align with business goals.
2. Why is root cause analysis considered critical during the Needs Assessment phase? RCA allows the business analyst to identify the underlying source of an issue rather than just treating symptoms, ensuring the solution effectively addresses the actual problem.
3. How does a context diagram assist in defining the solution scope? It provides a high-level visual representation of the system and its interactions with external entities, clearly defining the boundaries of what is inside and outside the solution.
4. What are the components of a SMART goal? A SMART goal must be Specific, Measurable, Achievable, Relevant, and Time-bound.
5. In the Kano model, what is the difference between a “must-have” and a “delighter”? A “must-have” is a basic requirement that stakeholders expect as a minimum, whereas a “delighter” is an unexpected feature that significantly increases satisfaction.
6. What is the purpose of the Purpose Alignment Matrix? It is used to assess the strategic importance of requirements by categorizing them as differentiators or mission-critical, guiding investment and approach decisions.
7. Define “benchmarking” in the context of Needs Assessment. Benchmarking is the process of comparing an organization’s internal processes, metrics, or practices against industry best practices or competitors to identify areas for improvement.
8. What does a SWOT analysis evaluate? It evaluates an organization’s internal Strengths and Weaknesses, along with external Opportunities and Threats.
9. Why must a business analyst identify stakeholders during the Needs Assessment phase? Early identification ensures that all parties affected by the initiative are represented, allowing their values and requirements to be captured before the project baseline is set.
10. What is the role of the business case in Domain 1? The business case serves as a justification for the initiative, outlining the problem, the proposed solution, and the expected value or return on investment.
Detailed Answer Key
- Focus of Needs Assessment: It aims to define business needs, analyze the current state, and recommend solutions that deliver organizational value.
- Importance of RCA: By identifying root causes, analysts prevent the implementation of solutions that fail to solve the actual business problem, thereby saving time and resources.
- Context Diagrams and Scope: These diagrams act as a boundary-setting tool, showing exactly which external systems and users interact with the solution.
- SMART Components: These five criteria ensure that goals are clear, trackable, and realistic within a specific timeframe.
- Must-haves vs. Delighters: Must-haves are mandatory requirements whose absence causes extreme dissatisfaction, while delighters provide a competitive edge and high satisfaction but are not expected.
- Purpose Alignment Matrix: It helps the business analyst align project efforts with the organization’s business architecture by identifying which features provide a competitive advantage.
- Benchmarking: This technique provides external context and performance standards that help justify the need for a project or define desired future-state goals.
- SWOT Evaluation: This tool provides a comprehensive view of the initiative’s internal and external environment, helping to identify risks and strategic fits.
- Stakeholder Identification: This prevents scope creep and late-stage requirement changes by ensuring the right people provide input from the beginning of the analysis.
- Role of Business Case: It provides the documented evidence and rationale needed for stakeholders to decide whether to invest in the project based on the value proposition.
Advanced Open-Ended Design Scenarios
- Scenario A: An organization is experiencing a 30% drop in customer retention. You are tasked with performing a Needs Assessment. Describe how you would utilize the 5 Whys technique in conjunction with an Ishikawa diagram to present a findings report to executive leadership.
- Scenario B: A company wants to implement a new AI-driven customer service portal. Using the Purpose Alignment Matrix and the Kano model, explain how you would prioritize features that are “mission-critical” versus those that are “differentiators” to ensure the business case remains viable.
- Scenario C: You are the lead business analyst for a merger between two financial institutions. The systems are highly complex and overlapping. Design a strategy for using ecosystem maps and context diagrams to identify stakeholders and define the initial solution scope for integrating their core banking platforms.
- Scenario D: A stakeholder group insists that a new mobile app must include every feature currently available on the desktop version. Explain how you would use Cost-Benefit Analysis and stakeholder value elicitation to negotiate a more focused and strategically aligned initial release.
- Scenario E: Your organization has identified an opportunity to enter a new international market. Conduct a theoretical SWOT analysis and explain how the results would influence the development of SMART goals for the project’s business case.
Glossary of Key Domain Terms
- Benchmarking: The practice of comparing business processes and performance metrics to industry bests and best practices from other companies.
- Business Analysis: The process of identifying business needs and recommending solutions to business problems.
- Business Case: A documented justification for an investment, describing the problem, solution options, and expected value.
- Context Diagram: A high-level visual that defines the scope of a system by showing its interactions with external entities.
- Ecosystem Map: A visualization of the entire environment in which a solution exists, showing relationships between systems and stakeholders.
- Feasibility Study: An assessment of the practical, technical, and economic viability of a proposed solution.
- Fishbone (Ishikawa) Diagram: A tool used in root cause analysis to categorize potential causes of a problem.
- FRAME: A guideline for objectives ensuring they are Few, Realistic, Agreed, Measured, and Explicit.
- Kano Model: A technique used to categorize and prioritize requirements based on stakeholder satisfaction.
- Needs Assessment: The domain focused on identifying problems/opportunities and evaluating solution options.
- OKRs (Objectives and Key Results): A framework used for setting and measuring the success of organizational goals.
- Purpose Alignment Matrix: A tool used to categorize requirements based on their strategic value and mission criticality.
- Root Cause Analysis (RCA): An analytical technique used to determine the underlying reason for a problem.
- SMART: A framework for defining objectives as Specific, Measurable, Achievable, Relevant, and Time-bound.
- Solution Scope Statement: A definition of the boundaries of a solution, identifying what is included and excluded.
- Stakeholder Engagement: The process of involving stakeholders effectively throughout the project lifecycle.
- SWOT Analysis: A strategic tool used to identify internal Strengths and Weaknesses and external Opportunities and Threats.
- Value Proposition: The promise of value to be delivered by a solution, explaining how it solves a problem or improves a situation.
- Valuation: The process of determining the worth or potential return of a proposed initiative or solution.
Leaderboard
No scores saved yet. Be the first!
25 Questions — PMI – PMI-PBA : Certified Professional in Business Analysis - Domain 1 - Needs Assessment
Expand any question to reveal the correct answer and explanation.
-
1 A business analyst is tasked with investigating a 20% drop in production efficiency. Several department heads have already requested a new automated scheduling software. According to the priority rules of Needs Assessment, what should the analyst do first?
Consider the importance of distinguishing between a requested solution and the underlying business problem.
Perform root cause analysis to separate the surface symptoms from the actual business issue.
Needs Assessment Task 1 requires defining the problem before accepting a requested solution, ensuring the organization doesn't solve for the wrong issue.
-
✗ Conduct a Cost-Benefit Analysis of the requested automated scheduling software.
Evaluating a specific solution before confirming it addresses the root cause of the efficiency drop is premature and risks wasting resources.
-
✗ Initiate stakeholder identification to determine who will be affected by the new software.
While stakeholder identification is crucial, it follows the initial definition of the problem or opportunity in the procedural sequence of Needs Assessment.
-
✗ Develop a solution scope statement for the automated scheduling software.
Defining scope for a solution that has not yet been validated against a business problem constitutes a failure to perform proper problem analysis.
-
-
2 When using an Ishikawa diagram to analyze a failure in a service delivery process, a business analyst identifies several 'branches' but struggles to find the specific root cause of the most critical branch. Which technique should be used next to achieve maximum depth?
Focus on the technique that involves asking iterative questions to move from a symptom to a fundamental cause.
The 5 Whys technique
The 5 Whys is specifically designed to drill down into a single cause identified on a fishbone diagram to uncover its fundamental root cause.
-
✗ Interrelationship Diagrams
These diagrams help identify complex cause-and-effect relationships between multiple factors but are less focused on iterative depth for a single factor.
-
✗ SWOT Analysis
SWOT is a strategic tool for environmental assessment (Strengths, Weaknesses, Opportunities, Threats) and is not a deep-dive root cause tool.
-
✗ Benchmarking
Benchmarking compares organizational performance against industry standards rather than investigating internal process failures at a granular level.
-
-
3 During Task 2 of the Needs Assessment, a business analyst evaluates a feature that stakeholders view as a 'taken-for-granted' requirement. Its absence leads to intense dissatisfaction, but its presence does not significantly increase satisfaction. How is this classified in the Kano Model?
Think about requirements that represent the minimum entry level for a product to even be considered viable.
Must-be (Basic) requirements
Must-be requirements are fundamental expectations; they are only noticed when they are missing, causing dissatisfaction, but provide no extra 'wow' factor when present.
-
✗ One-dimensional (Performance) requirements
Performance requirements result in satisfaction that is proportional to the level of fulfillment (e.g., faster speed equals more satisfaction).
-
✗ Attractive (Delighter) requirements
Delighters are unexpected features that provide high satisfaction when present but do not cause dissatisfaction if they are absent.
-
✗ Indifferent requirements
Indifferent requirements are those that the stakeholder does not care about and do not affect satisfaction or dissatisfaction levels regardless of presence.
-
-
4 An organization is considering a project to enter a new market. The business analyst is evaluating external factors such as new government regulations and shifting consumer demographics. Which tool is most appropriate for this environmental investigation?
Identify the acronym that covers political, legal, and social external categories.
PESTLE Analysis
PESTLE (Political, Economic, Social, Technological, Legal, Environmental) is the standard tool for investigating external macro-environmental factors.
-
✗ Ishikawa Diagram
Ishikawa diagrams are used for internal root cause analysis of specific problems, not for external environmental scanning.
-
✗ VRIO Framework
VRIO (Value, Rarity, Imitability, Organization) is used to assess internal resources and capabilities, not external market factors.
-
✗ RACI Matrix
A RACI matrix is a stakeholder responsibility tool used to define roles within a project or process.
-
-
5 When developing project goals in Task 3, the analyst uses the FRAME method. Which element of FRAME ensures that stakeholders have a shared understanding and commitment to the objectives?
Look for the component that implies a collective 'handshake' or sign-off among the parties involved.
Agreed
The 'A' in FRAME stands for Agreed, emphasizing the necessity of consensus and buy-in from all relevant stakeholders regarding the goal.
-
✗ Explicit
While 'Explicit' ensures the goal is clear and detailed, it does not specifically address the consensus or commitment of the stakeholders.
-
✗ Realistic
Realistic focuses on the attainability of the goal given the constraints, rather than the mutual agreement upon it.
-
✗ Measured
Measured refers to the criteria for success and quantification of the goal, similar to the 'Measurable' aspect of SMART goals.
-
-
6 A business analyst is facilitating a session to determine the value proposition of a new product. Several powerful stakeholders have conflicting interests. The analyst decides to use Force Field Analysis. What is the primary objective of this technique in this context?
Think about a tool that looks at 'pros' and 'cons' as dynamic vectors acting on a situation.
To identify and weigh the driving forces for change against the restraining forces.
Force Field Analysis helps visualize the balance of power and the factors that either support or oppose a proposed solution.
-
✗ To rank requirements based on their net present value (NPV) to the organization.
Financial ranking is performed using valuation metrics like NPV, whereas Force Field Analysis focuses on social and organizational pressures.
-
✗ To determine the technical feasibility of the proposed product features.
Technical feasibility is assessed through prototyping or expert judgment, not through the mapping of forces for and against change.
-
✗ To document the bi-directional links between requirements and their origins.
Traceability techniques like a Requirements Traceability Matrix are used for linking requirements, which is a Domain 4 activity.
-
-
7 While conducting stakeholder identification (Task 4), the analyst discovers a regulatory body that will not interact with the product but whose guidelines dictate mandatory security features. How should this entity be categorized in a stakeholder analysis?
Consider that while the regulator doesn't care about the product's success, they can stop the project if their rules aren't followed.
High Influence, Low Interest
Regulatory bodies often have high influence (mandatory rules) but low interest in the daily execution of the project unless a violation occurs.
-
✗ High Influence, High Interest
This category is typically reserved for project sponsors or core team members who are actively engaged and affected by daily outcomes.
-
✗ Low Influence, High Interest
This represents groups like end-users who care deeply about the product but may have little power to change the project's direction.
-
✗ Low Influence, Low Interest
These are peripheral stakeholders who require minimal effort and have no power to dictate mandatory features.
-
-
8 A business analyst is assessing the current state of an organization and identifies that the existing process has $15$ redundant steps that contribute to a $30\%$ delay in delivery. Which analytical technique is best suited to visualize these inefficiencies?
Identify the tool that focuses on 'value-added' versus 'non-value-added' time and activities.
Value Stream Mapping
Value Stream Mapping (VSM) is specifically designed to analyze the flow of materials and information to identify waste and non-value-added steps.
-
✗ Context Diagram
A context diagram shows high-level system boundaries and external entities but does not provide visibility into internal process steps or delays.
-
✗ Persona Analysis
Personas are used to understand user needs and values, not to map the technical efficiency of a delivery process.
-
✗ Cost-Benefit Analysis
This is a valuation tool used to justify investment after the problems and process inefficiencies have been mapped and analyzed.
-
-
9 An analyst is evaluating multiple solution options. Option A has an initial cost of $\$100,000$ and expected benefits of $\$150,000$. Option B has an initial cost of $\$200,000$ and expected benefits of $\$350,000$. If the organization's primary goal is maximizing total return on investment, which metric is most useful for Task 2?
Consider a ratio that compares the value generated for every dollar spent.
Benefit-Cost Ratio (BCR)
BCR allows for the comparison of options with different scales by normalizing the relationship between benefits and costs.
-
✗ Ishikawa (Fishbone) analysis
Ishikawa is used for problem analysis, not for the financial valuation of potential solution options.
-
✗ SWOT Analysis
SWOT is a qualitative strategic tool that does not provide the quantitative financial comparison needed for this decision.
-
✗ Ecosystem Mapping
Ecosystem mapping identifies systems and their interactions, which does not address financial return or cost assessment.
-
-
10 A business analyst is attempting to define stakeholder values regarding a new enterprise resource planning (ERP) system. The stakeholders are highly resistant and fear job losses. Which elicitation technique is most likely to be ineffective in Task 5?
Think about which technique is the least personal and easiest for a resistant stakeholder to manipulate or ignore.
Direct Surveys
In high-resistance environments, stakeholders may provide dishonest or vague answers on surveys; more interactive or observational methods are required.
-
✗ Observation (Job Shadowing)
Observation allows an analyst to see the actual work performed, bypassing the verbal resistance or fears that might skew interviews or surveys.
-
✗ Facilitated Workshops
Workshops, when properly facilitated, can help surface underlying fears and conflicts in a controlled environment to build consensus.
-
✗ Individual Interviews
Interviews provide a safe, one-on-one space where stakeholders might be more candid about their values than in a public or written forum.
-
-
11 What is the primary risk of relying solely on benchmarking during Task 1 of the Needs Assessment?
Consider the difference between meeting a standard and creating a new one.
It can lead to imitation rather than innovation.
Benchmarking focuses on catching up to industry standards or competitors, which may prevent an organization from forging a unique, innovative path.
-
✗ It fails to identify the magnitude of a problem.
Benchmarking is actually effective at identifying problem magnitude by showing how far the organization lags behind its peers.
-
✗ It requires expensive third-party data to be valid.
Benchmarking can be done using public standards or internal historical data and does not strictly require expensive third-party inputs.
-
✗ It is only applicable in Waterfall project environments.
Benchmarking is methodologically neutral and can be applied in Agile, Hybrid, or Waterfall settings.
-
-
12 A business analyst is drafting a business case and needs to ensure that the goals are 'SMART'. The current goal is: 'Reduce customer wait times by next quarter.' What is missing from this goal to make it fully SMART?
A goal cannot be verified if there is no specific quantity attached to the improvement.
Measurable
The goal lacks a specific metric (e.g., 'reduce by 10%') to determine if the goal has been successfully reached.
-
✗ Time-bound
The goal is time-bound because it specifies 'by next quarter' as the deadline for achievement.
-
✗ Specific
The goal is specific enough regarding the focus area ('customer wait times'), though it lacks the quantification to be measurable.
-
✗ Realistic
There is no information to suggest the goal is unrealistic, but the lack of measurement is a structural flaw in the goal statement itself.
-
-
13 During Task 4, a business analyst uses a 'Power/Interest' grid. A stakeholder is identified as having low power but extremely high interest in the project's success. What is the recommended strategy for this stakeholder?
Think about how to handle a cheerleader who doesn't have the authority to change your budget or scope.
Keep Informed
Stakeholders with high interest but low power should be kept informed to maintain their support and use their interest as a positive project force.
-
✗ Manage Closely
Managing closely is reserved for stakeholders with both high power and high interest.
-
✗ Keep Satisfied
Keeping satisfied is the strategy for stakeholders with high power but low interest, to prevent them from becoming blockers.
-
✗ Monitor Only
Monitoring with minimal effort is the strategy for stakeholders who have both low power and low interest.
-
-
14 Task 1 involves the creation of a 'Problem Statement'. Following the standard format, if 'Z' represents the successful solution, what does 'W' represent?
W is the 'what' that is causing the trouble in the first place.
The goal or root cause
In the format 'The problem of W affects X...', W represents the core issue or root cause being addressed.
-
✗ The users or stakeholders
In the problem statement format, X represents the stakeholders or users who suffer the impact of the problem.
-
✗ The outcomes suffered
Y represents the negative outcomes or impact suffered as a result of the problem.
-
✗ The financial budget
Budget is a constraint and is typically not a variable in the standard qualitative problem statement format.
-
-
15 An analyst is using the Purpose Alignment Matrix to evaluate solution features. A feature is identified as having high mission-criticality but low market-differentiation. How should the organization approach this feature?
Think about common utilities like payroll—every company needs them (critical), but they don't make you better than your competitor (low differentiation).
Parity (Minimize cost while meeting the need)
Features that are critical but not unique should be implemented efficiently at market parity without over-investing in custom innovation.
-
✗ Differentiating (Invest to excel)
Differentiating features have both high criticality and high market-differentiation; these are where the company should innovate most.
-
✗ Partner (Outsource or use a third-party)
Partner features have low criticality but high market-differentiation potential, often handled through strategic partnerships.
-
✗ Who Cares (Eliminate or ignore)
The 'Who Cares' quadrant represents features with low criticality and low differentiation.
-
-
16 Which valuation technique used in Task 2 involves determining if a project should proceed by evaluating if the benefits are worth the costs and risks, focusing on 'GO/NO-GO' decisions?
This technique asks 'Can we do it?' and 'Should we do it?' across multiple dimensions like time, cost, and technology.
Feasibility Analysis
Feasibility analysis assesses operational, technical, and economic factors to determine the overall viability of an initiative before heavy investment.
-
✗ Kano Model Mapping
The Kano model prioritizes features based on customer satisfaction but does not provide a holistic 'Go/No-Go' viability for the entire project.
-
✗ SWOT Analysis
SWOT identifies internal and external factors but lacks the specific viability metrics (e.g., technical or operational) required for a feasibility study.
-
✗ Root Cause Analysis
Root cause analysis is performed in Task 1 to identify the problem, whereas feasibility is a Task 2 activity to evaluate solution viability.
-
-
17 In the context of Needs Assessment, what is the 'Priority Rule' when a senior stakeholder requests a specific functional change during an early design workshop?
Think about the necessary step to protect the project from uncontrolled alterations.
Perform a formal impact assessment against the baseline requirements first.
Even during Needs Assessment, any change to established scope or baselines must be documented and evaluated for its impact before approval.
-
✗ Add it to the product backlog immediately to maintain stakeholder engagement.
Adding it without analysis can lead to scope creep and ignores the potential negative impacts on existing objectives.
-
✗ Escalate the request to the project sponsor for an immediate decision.
Escalation should only happen after the business analyst has performed the necessary analysis to provide the sponsor with data for a decision.
-
✗ Reject the request because it falls outside the original business problem defined in Task 1.
Requests should not be rejected outright; they must be evaluated to see if they align with updated business needs or require a change to the business case.
-
-
18 A business analyst is using 'Ecosystem Mapping' in Task 3. What is the primary difference between an Ecosystem Map and a standard Context Diagram?
Consider the scale and number of central focal points in each diagram.
An Ecosystem Map shows multiple systems and their interconnections, while a Context Diagram focuses on a single system.
Ecosystem maps provide a broader view of the enterprise landscape, whereas context diagrams specifically delineate the boundaries of one target system.
-
✗ A Context Diagram includes data flows, while an Ecosystem Map only shows hardware components.
Both can show high-level interactions, but the ecosystem map is not restricted to hardware; it covers systems and organizational units.
-
✗ Context Diagrams are only used in Agile, while Ecosystem Maps are used in Waterfall.
Both modeling techniques are methodologically neutral and can be used in any project environment.
-
✗ Ecosystem Maps are used for root cause analysis, while Context Diagrams are used for goal setting.
Ecosystem maps are scope models, while root cause analysis uses different tools like fishbone diagrams.
-
-
19 While conducting stakeholder analysis (Task 4), an analyst uses a 'Salience Model'. Which three attributes are used to classify stakeholders in this model?
The model uses one attribute related to time-sensitivity, one related to strength, and one related to 'rightful' status.
Power, Urgency, and Legitimacy
The Salience Model categorizes stakeholders based on their power to influence, the urgency of their claim, and the legitimacy of their involvement.
-
✗ Interest, Influence, and Impact
These are common attributes used in interest/influence grids, but they are not the specific components of the Salience Model.
-
✗ Authority, Role, and Skills
These attributes are more common in RACI matrices or resource planning rather than stakeholder salience analysis.
-
✗ Attitude, Beliefs, and Culture
While these are important for communication planning, they are not the structural categories of the Salience Model.
-
-
20 A business analyst is determining stakeholder values in Task 5. The stakeholders are prone to 'groupthink' and have a history of senior voices dominating discussions. Which technique should the analyst use to elicit unbiased values?
Look for a method that ensures anonymity and iterative feedback.
The Delphi Technique
The Delphi technique uses anonymous responses across multiple rounds to reach a consensus, preventing dominant individuals from influencing others.
-
✗ Brainstorming
Brainstorming is often subject to dominant voices and groupthink, as participants can see and hear each other's ideas in real-time.
-
✗ Joint Application Development (JAD)
JAD is a highly collaborative, face-to-face workshop format that is very susceptible to the influence of senior or louder participants.
-
✗ Requirements Walkthrough
A walkthrough is a verification technique to check documentation; it is not primarily an elicitation tool for uncovering hidden values.
-
-
21 During Task 1, an analyst performs 'Benchmarking'. Which of the following is the most significant advantage of this technique?
Benchmarking tells you how 'behind' or 'ahead' you are compared to a yardstick.
It provides a framework for understanding the magnitude of the problem by comparing against recognized standards.
Benchmarking allows the organization to quantify how far they deviate from the industry best, clarifying the scale of the need.
-
✗ It eliminates the need for further root cause analysis.
Benchmarking identifies that a gap exists, but it does not explain why the gap exists; root cause analysis is still required.
-
✗ It ensures that the final solution will be unique in the market.
Benchmarking often leads to parity (matching the industry) rather than uniqueness (innovation).
-
✗ It focuses solely on the internal processes of the organization.
Benchmarking is primarily an external comparison against competitors or industry standards.
-
-
22 In Task 2, 'Force Field Analysis' identifies a 'Restraining Force' related to an upcoming corporate merger. How should the analyst address this within the valuation of the initiative?
Forces that push against change should be viewed through the lens of uncertainty and potential failure.
Analyze the impact of the merger as a risk to the project's feasibility and benefits realization.
Restraining forces identified in Needs Assessment must be treated as risks or constraints that could impede the project's success.
-
✗ Ignore the restraining force until the Analysis domain (Domain 3) begins.
Waiting until Domain 3 ignores critical viability information needed for the initial business case and Go/No-Go decision.
-
✗ Use the Kano Model to convert the restraining force into a Must-be requirement.
The Kano Model is for user requirements; a merger is an organizational constraint or risk, not a product feature.
-
✗ Increase the project budget to counteract the restraining force.
Increasing budget without analysis is premature; the BA must first understand the nature and impact of the force.
-
-
23 An organization uses 'OKRs' (Objectives and Key Results) for Task 3. A business analyst notices that the Objective is well-defined, but the Key Results are qualitative (e.g., 'Improve user happiness'). What is the main problem with these Key Results?
How do you know if 'happiness' has improved if you don't have a number attached to it?
They are not measurable or time-bound.
Key Results in the OKR framework must be quantitative and verifiable to determine if the objective has been achieved.
-
✗ They focus on outcomes instead of activities.
Focusing on outcomes is actually a strength of OKRs; the problem is the lack of quantification for those outcomes.
-
✗ They are too aggressive and unattainable.
There is no indication of the level of difficulty, only a lack of the specific metrics needed to measure progress.
-
✗ They do not align with the organization's mission statement.
The question specifies the objective is well-defined; the failure lies in the structural measurement of the results.
-
-
24 A business analyst is performing a 'Job Analysis' as part of stakeholder identification in Task 4. What is the primary purpose of this technique?
Think about identifying 'who does what' so you don't miss any stakeholders.
To understand the specific tasks and responsibilities of a role to identify their requirements and values.
Job analysis helps identify the specific individuals or roles who interact with a process, ensuring all affected parties are included.
-
✗ To determine the salary range for the project team members.
Salary determination is an HR function, not a business analysis task related to stakeholder identification or value assessment.
-
✗ To create a fishbone diagram for the current system's failures.
Fishbone diagrams are for root cause analysis (Task 1), whereas job analysis is for identifying stakeholders (Task 4).
-
✗ To assess the financial feasibility of automating a specific role.
Feasibility analysis is Task 2; Job analysis in Task 4 is about identifying people and their needs.
-
-
25 When collecting information for the value proposition (Task 2), a business analyst uses 'Document Analysis'. What is a major limitation of this technique?
Just because a process is written in a manual doesn't mean employees actually follow it that way today.
The information may be outdated or no longer reflect the actual 'as-is' process.
Existing documentation (manuals, policies, reports) often lags behind reality as processes evolve informally over time.
-
✗ It is too expensive to perform compared to interviews.
Document analysis is generally one of the most cost-effective techniques as it can be done independently by the analyst.
-
✗ It requires the analyst to have high-level programming skills.
Document analysis is a qualitative research technique and does not require technical coding expertise.
-
✗ It is prohibited under PMI's code of ethics for Needs Assessment.
Document analysis is a standard, highly recommended technique in the PMI-PBA toolkit.
-