Domain 4 of 4

Requirements and Delivery Alignment

Writing requirements and use scenarios that carry the market problem with them, ranking work with market data rather than volume of complaints, keeping stakeholders informed on a rhythm, and watching product profitability once the thing is shipped.

Concepts

~25%

Of the exam

Practice questions

Concepts in this domain

01Requirements and use scenariosRequirements articulate personas and their problems so the right thing gets built. A use scenario puts the problem in a story so the context travels with it.02Prioritising with market dataRanking requirements on evidence of how many people have the problem and how urgent it is, so the order can be defended without anyone raising their voice.03Stakeholder communicationsProactive communication with the people affected by the product, from strategy through execution, on a rhythm rather than in response to escalation.04Product profitabilityWatching how the product performs in the market, what it costs the company to run, and what it contributes to profit, after the launch has stopped being news.

Try a question from this domain

The framework describes Requirements as articulating and prioritising personas and their problems so that the appropriate products can be built. What does this rule out?

AIncluding acceptance criteria in a requirement
BInvolving developers in writing requirements
CPrioritising requirements against one another
DSpecifying the mechanism, since that removes the design decision from the people best placed to make it and hides the reasoning that would let them make a better one

15 questions on this domain.

One per page, with a worked explanation.

Start the set

Not affiliated with or endorsed by Pragmatic Institute.