Capstone project for From Spec to Launch

Expiry dates at receiving: from spec to launch

Mangrove Market throws away stock that expires on the shelf because nobody knows the dates until it is too late. Head office wants store staff to record expiry dates when they receive goods on the Store app's handheld scanners, so the app can warn store managers before stock expires and suggest markdowns. An outside vendor will build the feature; Leila has drafted the screens; Ama's store will pilot it. Take the feature from idea to launch: write the PR/FAQ and a one-page PRD, write the stories and acceptance criteria (including a scanner that goes offline halfway through a receipt and a supplier who delivers cartons with no printed dates), review the design, write the SOW clauses for UAT and the support SLA, and plan the launch from Ama's store to all 320 stores.

What you hand in

A one-page PR/FAQ and a one-page PRD with goals (baseline, target, date), guardrails, non-goals and owned open questions
Eight to ten user stories with Given/When/Then acceptance criteria, covering the offline receipt, missing dates and the non-functional requirements
Design review notes on Leila's receiving screens, with heuristics, severities and the missing states
SOW clauses for UAT (entry criteria, exit criteria, sign-off) and the support SLA with severity levels
A launch plan with the pilot in Ama's store, waves to 320 stores, training, support readiness and a dated post-launch review with success metrics

Check your work

Tick each item when your project meets it. Be strict: this is the rubric the reviewer uses.

The PRD's goals are outcomes with a baseline, target, date and data source, such as the value of expired stock written off per store per month
At least one non-goal rules out something a stakeholder would reasonably expect, with a reason
The offline scenario says what staff see, what is stored on the scanner, and what happens when the network returns
The missing-date scenario has a clear business rule (for example, a manual date or a 'no date' reason code) that a tester can check
Speed requirements name the store handheld model, the conditions and a number; permissions and the audit trail are server-enforced and specific
Design notes rate each issue 0 to 4 and include at least one frontline condition such as gloves in the cold room or one hand holding a carton
UAT exit criteria allow no open severity 1 or 2 defects, and the SLA defines severity in business terms with response, workaround and fix times
The launch plan sets go/no-go criteria before the pilot, avoids a festival freeze, and books the post-launch review with a decision rule

0 of 8 checked

Model answer

The model answer opens once your capstone passes the review, so you can compare your work with an outline of a strong submission.

Hand in your capstone

Your links are checked automatically, then the work is scored against the rubric above, item by item, with comments. A pass counts toward the course certificate and shows on your profile.

Loading…