deanpeters/Product-Manager-Skills / plugins/pm-develop/skills/sprint-planning
sprint-planning
VerifiedPlan a sprint around a goal, real capacity, and named risks. Use when a team's sprints end with carryover, a pile of unrelated tickets, or a goal nobody can state.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.8 KB |
| examples/sample-industrial.md | markdown | 1.9 KB |
| examples/sample.md | markdown | 2.0 KB |
| template.md | markdown | 1.5 KB |
examples/sample-industrial.md
View on GitHub# Sprint Planning Example: Industrial
**Team:** Northfield firmware team (5 engineers), 2-week sprint, NFA-500 bring-up
**Dependency:** a supplier radio-module sample promised for day 4
**Why this example exists:** a physical dependency with real lead time. The goal had to survive a
late part.
---
```markdown
## Sprint goal
> Firmware boots on the production NFA-500 board and reports a fault code over the service port.
Flexible: can be met on the dev board if the radio sample slips; the radio is the stretch.
## Capacity
| Person | Days | Leave/meetings | Focused |
|---|---|---|---|
| 5 engineers | 50 | 4 leave, 8 meetings, 5 lab-sharing | 33 |
**Focus factor:** 0.8 → ~26 days. Last three sprints finished 7, 8, and 6 items; plan 7.
**Slack held:** 2 items (about 25%): lab bookings fall through; board revisions arrive late.
## Selected work
| Order | Item | Ready? | Size |
|---|---|---|---|
| 1 | Bring up bootloader on production board | Yes | M |
| 2 | Fault-code table over service port | Yes | M |
| 3 | Watchdog configuration | Yes | S |
| 4 | Radio driver smoke test | **Blocked on sample** | M |
| Stretch | Power-cycle test rig script | Yes | S |
## Risks and dependencies
| Item | Owner | Needed by | Fallback |
|---|---|---|---|
| Radio sample | Supply chain lead | Day 4 | Move item 4 to next sprint; goal unaffected |
| Lab slot for thermal test | Test lead | Day 6 | Book a backup slot on day 8 |
**Most likely to break the goal:** the production board revision arriving late.
## Commitment
Believed with one condition: if the board slips past day 2, drop to the dev board and re-plan.
```
## What to learn from this
- **The goal doesn't depend on the late part,** so the supplier slipping costs scope, not success.
- **Slack is larger (25%)** because physical lead times are less forgiving.
- **The condition is named in advance,** so the day-two decision is already made.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |