Explain the direction
How does a Product Vision connect needs, benefits and differentiation?
How do we connect user needs
to a coherent product?
S1 Week 3
What difference matters?
What does the user do?
What deserves attention next?
A list of stories can hide the journey and the reason for building a product. This Lecture connects direction, user activity and decisions about work. All room-booking and equipment-loan scenarios in this deck are fictional teaching examples.
How does a Product Vision connect needs, benefits and differentiation?
How do activities, steps and stories fit together?
How do evidence, value and dependencies shape ordering and refinement?
The Lecture focuses on explaining and distinguishing supplied examples. In the Seminar you will apply the ideas to your own project and identify where evidence is still missing.
A student is organising a group meeting and requests a room.
“I emailed reception to check my request.” One simulated account, not a frequency claim.
“Request sent” is followed by an enquiry. Observed sequence does not establish the reason.
Two requests can compete for the same room and time.
Only one confirmed booking per room and time.
Know whether the room is secured before telling the group.
These identifiers continue the Week 2 teaching case. E1 and E2 inform a candidate need but do not prove its prevalence. Clearer status is a proposed response; reduced checking is an untested benefit hypothesis. E3 and rule B1 are established here and reused in the ordering and slice decisions.
For students arranging group meetings, RoomLink is a room-request service that helps them know whether a room is secured before coordinating with their group.
Compared with a request-sent message alone, it aims to provide an explicit confirmed or unsuccessful outcome.
They need a clear booking outcome.
The expected benefit still needs checking.
Compared with this case’s current workflow.
A Product Vision gives a product a direction by linking its users, need and intended benefit. Differentiation needs a meaningful comparison. Here the comparison is with the fictional request-sent workflow, not a claim about every competing product.
“Build an AI-powered app with login, dark mode, a dashboard and calendar integration.”
“Help meeting organisers know whether a room is secured, using a clear outcome instead of a receipt-only message.”
A detailed feature list can still lack direction. A stronger vision helps evaluate proposed features, but wording alone cannot validate demand or differentiation.
Help meeting organisers coordinate with confidence by making booking outcomes clear.
Eligible students can complete a room request and see an unambiguous outcome in one service.
The vision frames the benefit. The Product Goal gives the team a future product state to plan towards.
Teaching examples. A vision statement is not a required Scrum artefact or a prescribed template.
In Scrum, the Product Goal is the commitment associated with the Product Backlog. Product Vision is a useful broader direction; Scrum does not mandate this particular vision format. A feature checklist does not automatically express either.
A broad purpose in the journey.
Something the user does within that activity.
As a meeting organiser, I want to see whether my booking is confirmed so I can tell my group.
Read levels in context. Granularity varies; these labels are our mapping convention.
An activity groups related user steps. A step describes something the user does. A story describes a more specific user-valued capability or variation supporting the step. Short map cards stand for conversations rather than complete specifications.
Within “Secure a booking”, where does this card belong?
An implementation task. It may support a story, but it is not a user-journey step.
Classification depends on the scope of the map. Here the broader activity and supporting story examples fix the context. Technical tasks matter, but arranging database, API and UI modules across the top hides the user journey.
Perspective: a student organising a meeting. Activities + steps form the backbone.
Position across the map does not set development priority. Optional cards are unvalidated ideas.
The map preserves user context. Across the top, follow the normal sequence from finding a room to knowing the outcome. Below a step, explore supporting stories and variations. A real journey may loop or branch; this map shows one simplified narrative.
Simplify the options while preserving a coherent path.
A minimal working end-to-end path is sometimes called a walking skeleton. It can test integration and expose omissions. It is not automatically a validated MVP. First-slice choices must still satisfy essential constraints and preserve honest outcomes.
Secure a booking → Check outcome
US1: See the outcome.
An ordered, evolving view of work.
PBI-03: The same US1 outcome story, with detail and an ordering rationale.
A backlog may include other product work, not only user stories. Story mapping is a complementary technique.
A map makes the journey and missing connections visible. A Product Backlog makes the current order of work explicit. Linking the same item between views avoids losing its context; the map does not replace the backlog.
As a meeting organiser, I want to see the outcome of my request so I can tell my group whether we have a room.
Reports of checking inform a need for an explicit outcome.
Show confirmed only after an eligible booking is recorded.
Success: room + time + confirmed.
Conflict: no extra booking + unsuccessful.
Passing behaviour checks does not establish this user benefit.
Useful teaching fields, not a mandatory Scrum item template. Simulation rule B1 still applies.
Traceability exposes the reasoning behind an item. Evidence informs N1; design and rule B1 shape acceptance examples. The result must be safe before a confirmation is shown. H1 requires separate investigation with users.
Assume a room/slot feed is available. This is one provisional order for discussion.
The map reads across as the user’s narrative; the backlog orders work by risk, dependency and evidence. PBI-02 belongs to the first slice; attending to it early reflects risk, not layer-first delivery.
This order is conditional, not a delivery schedule. The complete first slice still needs browsing. In this example the core booking risk motivates early attention; if access to slots is uncertain, investigate that dependency earlier. Evidence can change the order.
E3 reports conflicts. Rule B1 permits only one confirmed booking per room/time.
A: handle a taken slot honestly.
B: add custom colour themes.
Ordering is a judgement with reasons. A small or visually impressive item is not automatically the highest-value one. Dependencies, risk and evidence can justify attention to less visible capabilities.
One participant reads “request sent” as “booking confirmed”.
Ask what the participant understood; check the workflow.
Clarify confirmed and unsuccessful cases, messages and checks.
Address ambiguous outcomes, then reassess lower-value options.
Refinement develops shared understanding as information changes. It can clarify, split and reorder items, not merely add text. E4 is one simulated observation and does not establish prevalence or validate a proposed solution.
High value, ambiguous outcome wording, unresolved conflict behaviour.
Low-order idea with no supporting evidence in this case.
Product Owner: accountable for backlog management. Collaboration does not mean one person writes every item alone.
Focus refinement effort on work whose uncertainty matters soon. User perspectives, feasibility and dependencies inform the conversation. The Product Owner remains accountable for backlog management even when others help do the work.
Fictional case: students need to know whether equipment is reserved before collecting it.
Which is the stronger vision?
Within “Arrange a loan”, what is “See the reserved item and collection time”?
One user mistakes “received” for “reserved”. What next?
These are formative practice questions. Explain your reasoning before reading feedback. A better vision can still be incomplete; classification needs a map context; new feedback should trigger investigation and appropriate refinement.
Use your evidence to frame a direction. Map activities, steps and stories; walk through the user journey.
Choose a coherent slice, order traceable items and revise after peer challenge. Record exclusions and questions.
Direction → Journey → Reasoned order
Next: develop scope and release reasoning. Today’s artefacts are starting points, not fixed promises.
Keep evidence, assumptions and design decisions distinguishable. The first Seminar block develops vision and map; the second develops a slice and backlog. Detailed prioritisation methods and release planning are outside today’s Lecture.