← Back to blog

First Sprint: What to Expect in Your First Month of Scrum

scrum beginners agile

Getting started with Scrum is like learning to ride a bike: the first few meters are clumsy, but once you find your balance, it feels natural. Here’s what to expect during the first few sprints.

Before Sprint 1

What you need ready

  • Roles defined: who’s the PO, who’s the Scrum Master
  • An initial Product Backlog: a list of desired features
  • Tools set up: board, communication channels, estimation tooling
  • Sprint length decided (recommended: 2 weeks)

Sprint 1: The Awkward One

What will happen

  • Long planning session (3-4 hours): the team is still figuring out how to estimate
  • Unpredictable velocity: the first sprint is always a guess
  • Lots of questions: everyone is learning the process
  • A nagging sense of “we’re doing this wrong”: perfectly normal

Realistic expectations

  • 40-60% of planned work will be delivered
  • Estimates will be off by roughly ±50%
  • The team will question whether Scrum is even worth it

Tips

  • Plan for less than you think will fit
  • Focus on following the process, not delivering everything
  • In the retrospective, be honest about the struggles

Sprint 2: The Adjustment

What will happen

  • Faster planning (2-2.5 hours): now there’s a reference point
  • First real sense of velocity: “we delivered 18 last time”
  • The team starts internalizing the rituals
  • Daily Standups might still drag on

Realistic expectations

  • 60-75% of planned work will be delivered
  • Estimates off by roughly ±30%
  • Some ceremonies start to flow more naturally

Tips

  • Use Sprint 1’s velocity as a rough guide (with buffer)
  • Adjust your Definition of Done if needed
  • Introduce Planning Poker if you haven’t already

Sprint 3: Finding the Rhythm

What will happen

  • Planning settles at ~2 hours: the team gets the format
  • Velocity begins to stabilize
  • The team starts questioning the process constructively
  • Dailies become more focused

Realistic expectations

  • 70-85% of planned work will be delivered
  • Estimates off by roughly ±20%
  • The team starts self-organizing

Tips

  • Begin calibrating estimates: review Sprint 1 and 2 outcomes
  • Introduce backlog refinement if it doesn’t exist yet
  • Encourage pair programming on complex tasks

Sprint 4 and Beyond: Consistency

What will happen

  • Planning driven by real data
  • Velocity shows a detectable pattern
  • Ceremonies stay within their timeboxes
  • The team suggests process improvements

Realistic expectations

  • 80-95% of planned work will be delivered
  • Estimates off by roughly ±15%
  • The team operates in a self-organized fashion

Signs it’s working

✅ The team leaves planning knowing exactly what to do ✅ Daily Standups don’t turn into status reports ✅ Reviews have active stakeholder participation ✅ Retrospectives produce implemented action items ✅ Estimates improve sprint over sprint ✅ The team enjoys the process (or at least doesn’t dread it)

Red flags

❌ The team doesn’t understand why they’re doing ceremonies ❌ Product Owner is absent or disengaged ❌ Sprint Planning still takes more than 4 hours after Sprint 3 ❌ Nobody looks at the board outside of ceremonies ❌ Retrospectives produce zero action items ❌ Velocity swings wildly with no pattern (e.g., 10, 30, 15)

Each role’s responsibilities early on

Product Owner

  • Provide a refined backlog
  • Actively participate in planning
  • Be available for questions during the sprint

Scrum Master

  • Facilitate ceremonies
  • Educate the team on the process
  • Clear blockers quickly

Development Team

  • Show up and stay engaged during ceremonies
  • Estimate honestly
  • Commit to the Definition of Done

Conclusion

The first few sprints are intentionally rough. Don’t aim for perfect — aim for consistent. After about 4 sprints, the process should feel natural. If it still feels chaotic after 6 sprints, the problem probably isn’t Scrum itself — it’s something in the implementation that needs adjusting.