Exercise 1: A Second User Story — Possible Solution
====================================================================

THE NEW STORY
------------------------------
    "As a PLATINUM member, I want to see my points balance on the
    order confirmation page, so that I know how many points I have
    available to redeem."

    Estimated at 3 points.

RESULTS
------------------------------
    Story 2 independent of Story 1 (redemption): True

    Displaying a balance only READS existing data - the loyalty points
    balance already exists from Software Testing Strategy's own
    capstone, and the redemption story doesn't need to exist first for
    a read-only display to work.

    Total committed: 13 (redemption) + 3 (balance display) = 16
    Fits within known velocity (20.0): True
    Remaining sprint capacity for other backlog items: 4.0

WHY THIS WORKS AS AN ANSWER
------------------------------
This demonstrates the chapter's own Chapter 5 independence check
applied to a genuinely different kind of story - a read-only display
feature rather than a state-changing one. The two stories touch the
same underlying data (points balance) without being dependent on each
other in the sense Chapter 5 cares about: neither story's own
completion blocks the other from starting or finishing, since one only
reads what already exists and the other adds new write behavior on top
of it. The sprint's own capacity (20 points, matching known velocity)
comfortably absorbs both stories with 4 points of headroom remaining
for smaller backlog items.