Sprint backlog

Delivered sample scope

• Weekly capacity matrix with editable initiative person-days.
• Availability math for time off and non-project commitments.
• Overload, full-capacity, open-capacity, and zero-availability states.
• Baseline/draft comparison, apply, undo, reset, and JSON export.
• Initiative risk summaries, search empty state, storage warning, hash navigation, and responsive layout.
• Unit tests for the planning logic.

Candidate next sprint

Prioritize only after formative sessions show that the existing seeded workflow is understood.

1. Test matrix navigation with screen-reader and keyboard-only participants.
2. Add scenario naming and local history if repeated planning-review need is observed.
3. Define a CSV import only if setup becomes a validated barrier and data-quality/privacy needs are decided.
4. Explore date shifts only after users diagnose allocation conflict; the current signal does not forecast dates.

Non-goals for this increment

Do not add staffing recommendations, productivity scores, burnout conclusions, shared editing, or real-system connections. Each changes the decision boundary and needs separate evidence.

Later, subject to validation

Team-based permissions, system integrations, and collaboration are intentionally deferred until the core planning model is validated.