{"id":"pm-sprint-review-shipped-slipped","audience":"product-managers","category":"summarizing","track":"productivity","technique":"verification","title":"Report what shipped and what slipped after a sprint","free":false,"task":"You're sending stakeholders the sprint review summary. Write exactly 3 lines labeled Shipped:, Slipped: and Next sprint:, plain text, under 70 words. Count something as shipped only if it's live for customers, not just demoed or merged, and give the reason for each slip in a few words.","materialLabel":"Sprint notes (attached to your prompt automatically)","material":"Sprint 24 review - Fieldnote mobile (Mar 2-13)\n\nPlanned:\n1. Photo compression on upload - LIVE for all users Mar 11.\n2. Tag suggestions - demoed at review, merged, but behind a flag; NOT live for customers until QA signs off next sprint.\n3. Offline drafts - slipped: sync conflicts with older app versions; moved to sprint 25.\n4. iPad split view - LIVE Mar 12.\n5. Export to PDF redesign - slipped: design changes from the customer interviews came in late (Mar 9).\n\nSprint 25 plan (starts Mar 16): QA and release tag suggestions; offline drafts; PDF export redesign.\n\nOther: velocity 34 points (team average 31). Lena out sick 2 days. Retro action: shorter standups.\n\nAudience: sales, support and marketing leads. They want to know what they can tell customers.","rules":[{"type":"maxWords","max":70},{"type":"plainText"}],"mistakes":[{"title":"Asking for 'a sprint summary'","why":"The AI writes a long report with headings, velocity and retro notes.","fix":"Be exact: \"3 lines labeled Shipped:, Slipped:, Next sprint:. Plain text.\"","checks":["r0","plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting. Ask for a total word limit and it often lands over it.","fix":"Cap each line instead: \"each line under 20 words.\"","checks":["maxWords"]},{"title":"Counting demos as shipped","why":"Tag suggestions were demoed and merged, so the AI counts them as done.","fix":"Add: \"Shipped means live for customers. Tag suggestions isn't live yet.\"","checks":["r1"]},{"title":"Slips without reasons, plus noise","why":"The AI lists slips without why, and adds team stats stakeholders don't need.","fix":"Add: \"Give each slip's reason in a few words. No velocity or team notes.\"","checks":["r2"]}],"promptHints":[{"label":"Shows the labels","patterns":["shipped:","slipped:","next sprint"]},{"label":"Defines shipped","patterns":["live","not (just )?demo","customers can","behind a flag"]},{"label":"Gives slip reasons","patterns":["reason","why"]},{"label":"Drops team noise","patterns":["velocity","no team","retro","sick"]},{"label":"Sets a word limit","patterns":["\\d+\\s*words","word (limit|count)"]}],"hint":"Stakeholders repeat 'shipped' to customers, so it has to mean live. Give the AI the three labels, the definition of shipped, and what to drop.","rubricLabels":["Has exactly 3 lines labeled Shipped:, Slipped: and Next sprint:, in that order","Shipped lists only photo compression and iPad split view; tag suggestions are not called shipped (it may appear under Slipped or Next sprint as not yet live)","Slipped includes offline drafts (sync conflicts with older app versions) and PDF export redesign (late design changes), and nothing about velocity, sick days or the retro appears"]}