Requirements and Value Techniques

Capturing Requirements and Measuring Value

The final set of techniques in this chapter addresses how requirements are captured and prioritized in iterative delivery, how stakeholders are identified and understood, and how the value a solution delivers is measured against objectives. These four techniques are used from early stakeholder analysis through late-stage value confirmation, and they appear frequently in ECBA situational questions about agile-style delivery and value measurement.

The Four Techniques at a Glance

User Stories

A user story is a short, structured description of a requirement written from the perspective of the person who wants the capability, commonly following the format "As a [role], I want [goal], so that [benefit]." Its purpose is to capture just enough detail -- role, goal, and rationale -- to support estimation and planning, with full detail deferred until acceptance criteria are added closer to development. A BA writes user stories in iterative or agile delivery contexts, where requirements are captured and refined incrementally rather than fully specified up front. User stories are often accompanied by acceptance criteria, which define the specific conditions that must be true for the story to be considered complete, giving the delivery team an unambiguous definition of done.

Backlog Management

Backlog management is the ongoing practice of capturing, ordering, and prioritizing a list of work items -- user stories, requirements, defects -- so the team always works on the highest-value item next. It includes activities such as grooming, which refines and estimates items, and reprioritizing as new information emerges. This technique is used continuously in iterative and agile environments, wherever work is delivered incrementally and business priorities can shift between delivery cycles. A well-managed backlog is continuously refined rather than fixed at the start of an initiative, allowing the team to respond to new information, shifting business priorities, or feedback from previously delivered increments.

Stakeholder List, Map, or Personas

This technique identifies the individuals and groups who have an interest in or influence over an initiative and analyzes them using tools such as a stakeholder list (name, role, interest), a stakeholder map (for example, a power and interest grid), or personas (composite profiles representing a class of users). Its purpose is to ensure the BA engages the right people, at the right level, at the right time, and understands their needs, attitudes, and potential impact on the initiative. A power and interest grid, for example, helps the BA decide how much time and what type of engagement each stakeholder group warrants, from close collaboration with high-power, high-interest stakeholders to simple monitoring of those with lower interest. A BA builds and revisits this artifact at the start of an initiative and throughout, whenever stakeholder composition or influence changes.

Metrics and Key Performance Indicators

Metrics and KPIs are quantifiable measures used to evaluate the performance of a process, solution, or organization against defined objectives. A metric is any quantifiable measurement; a KPI is a metric tied directly to a critical success factor and monitored to judge whether strategic or operational goals are being met. This technique gives stakeholders an objective basis for confirming whether a solution actually delivered the value it promised, rather than relying on assumption. A BA applies it when defining success criteria for an initiative up front, and again after delivery to monitor and confirm ongoing value. Selecting the right metrics early, before a solution is built, ensures the organization can objectively evaluate outcomes later rather than relying on anecdotal impressions of success.

Bringing the Four Together

These techniques typically appear together across a single initiative's lifecycle: a stakeholder list or persona set identifies who the solution is for; user stories capture what they need in small, deliverable increments; a managed backlog decides the order those increments are delivered in; and metrics and KPIs confirm, after delivery, whether the increments actually produced the intended value. On the exam, watch for situational stems that describe agile ceremonies such as sprint planning or grooming -- these usually point to backlog management or user stories -- versus stems that describe confirming or monitoring outcomes after go-live, which point to metrics and KPIs. A stem describing who is affected and how much influence they have before work begins points to the stakeholder list, map, or personas technique.