Probar gratis
5 min lectura Guide 710 of 877

How to Use GitScrum for Sprint Planning?

How to use GitScrum for sprint planning?

Manage sprint planning in GitScrum with backlog grooming, capacity planning, and goal setting in NoteVault. Track commitments, balance workload, achieve sprint goals. Teams with structured planning improve sprint success rate by 40% [Source: Agile Planning Research 2024].

Sprint planning workflow:

  1. Prepare - Groom backlog
  2. Goal - Set sprint goal
  3. Capacity - Calculate availability
  4. Select - Choose tasks
  5. Commit - Team agreement
  6. Execute - Work sprint
  7. Review - Assess completion

Sprint planning labels

LabelPurpose
sprint-plannedPlanned for sprint
sprint-committedTeam committed
carry-overFrom previous sprint
stretchIf time allows
sprint-goalContributes to goal
blockedHas blocker

Sprint planning columns

ColumnPurpose
BacklogReady for planning
Sprint PlannedSelected for sprint
In ProgressBeing worked
ReviewBeing reviewed
DoneCompleted

NoteVault sprint docs

DocumentContent
Sprint goalCurrent sprint objective
Capacity planTeam availability
Velocity historyPast performance
Sprint notesPlanning decisions
RetrospectiveWhat to improve

Sprint planning template

## Sprint: [name/number]

### Dates
- Start: [date]
- End: [date]
- Planning: [date/time]
- Retro: [date/time]

### Sprint Goal
[One clear, achievable goal]

### Capacity
| Team Member | Available Days | Commitment |
|-------------|----------------|------------|
| @[person] | [days] | [points/tasks] |
| @[person] | [days] | [points/tasks] |
| **Total** | **[days]** | **[points/tasks]** |

### Planned Work
| Task | Owner | Estimate | Goal-aligned |
|------|-------|----------|--------------|
| [task] | @[person] | [estimate] | ✓/✗ |

### Risks
- [Risk 1]

### Carry-over from Last Sprint
- [Task if any]

Capacity calculation

FactorAccount For
Work daysDays in sprint
PTOTime off
MeetingsStanding meetings
BufferUnknowns (20%)
Actual capacityNet available

Velocity tracking

SprintCommittedCompleted%
Sprint 1302893%
Sprint 2322578%
Sprint 3282796%
Average302789%

Backlog grooming

ActivityWhen
Add detailsBefore planning
EstimateBefore planning
PrioritizeContinuous
ClarifyAs questions arise

Sprint goal criteria

ElementRequirement
ClearEveryone understands
AchievableRealistic
MeasurableCan verify completion
ValuableDelivers benefit

Planning meeting agenda

TopicDuration
Review capacity10 min
Set sprint goal10 min
Select tasks30 min
Assign owners10 min
Identify risks10 min

Task selection criteria

CriterionWeight
Aligns with goalHigh
Ready for workRequired
Right sizeMedium
Dependencies clearRequired

Common planning mistakes

MistakeSolution
Over-commitmentUse velocity
No goalAlways set goal
Unclear tasksGroom before planning
Ignoring capacityCalculate properly

Mid-sprint adjustments

SituationAction
Ahead of planPull from backlog
Behind planReduce scope
Blocker foundEscalate, adjust
Urgent itemDiscuss, trade-off

Sprint review checklist

CheckAssess
☐ Goal achieved?Yes/Partial/No
☐ Committed completed?% complete
☐ Carry-overWhat didn't finish
☐ LearningsWhat to improve

Sprint metrics

MetricTrack
VelocityPoints completed
Commitment rate% completed
Goal achievementMet/partial/missed
Carry-overItems carried

Continuous improvement

Retrospective FocusImprovement
Estimation accuracyBetter sizing
Capacity planningAccount for reality
Goal settingClearer goals
Team collaborationBetter communication