CAPM Practice: Validate requirements through product delivery
Question 36 of 68 in Validate requirements through product delivery
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: NPS data reveals overall customer satisfaction with the product — declining NPS after a release may indicate that delivered requirements didn't improve experience as intended; improving NPS validates that requirements changes delivered customer value
Explanation
NPS provides aggregate customer sentiment data. When BAs correlate NPS changes with specific feature releases, they can assess whether requirements delivered value (NPS improved) or failed to improve the experience (NPS flat or declining). This connects delivery to business outcomes.
**Why not A:** NPS is not purely a financial metric. It measures customer loyalty and satisfaction by asking how likely customers are to recommend the product. This customer sentiment data directly relates to whether product requirements delivered the intended user experience.
**Why not B:** NPS captures overall product satisfaction, not just marketing effectiveness. When a feature release changes NPS scores, it reflects how well the product requirements met user needs — spanning all aspects of the product, not just marketing-related ones.
**Why not C:** NPS does not measure the quality of requirements documents themselves. It measures end-user satisfaction with the delivered product. BAs use NPS as a post-delivery indicator of whether the requirements they defined ultimately translated into customer value.
Key Concept
This question covers Validate requirements through product delivery under Validate requirements through product delivery (Business Analysis Frameworks).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free