The Sprint

A new sprint typically kicks off with a plan session. The team facilitator will have scheduled this in advance.

A typical flow of events for a sprint looks something like this:

  • Kickoff and Plan session
  • Build and Test (many cycles of coding, code review, demo to QA, QA)
  • Sprint Review
  • Release
  • Retrospective

Schedule recurring interactions

When a sprint kicks off the team facilitator will confirm all interactions have been scheduled and the correct role players are attending. At sprint level the recurring interactions are typically the daily standup.

Non recurring interactions

Non recurring interactions like the sprint review and retrospective happen at the end of the sprint and will be scheduled by the team facilitator once the team have completed work on the last ticket in the sprint.

Product Change

Product change interactions happen when the product associated with the sprint is new. are considered at the beginning of each new sprint. When the sprint starts it is important to introduce the product and code to any people who have not yet been exposed to them – or to any one who feels an overview would be valuable. The team may also discuss the objectives as they relate to the team’s strengths.

Both the functional overview and code overview are timeboxed, even for team members who have had no exposure to the systems. The theory is knowledge will be gained iteratively. Someone new to a very complex system should continue to request these meetings as new sprints kick off in order to build up their knowledge over time.

A stable team will eventually often skip these and this is the reason they are not part of our more ritualistic agile interactions and ceremonies.

Business value and functional overview – 1 hour

Sometimes the product owner will run through a high level overview of the product the team is about to start work on.

This presentation occurs when there is someone in the team who hasn’t had exposure to the product. Or perhaps there is someone in the team who would like a refresher. The meeting is mandatory when the team has someone with no exposure to the product. People (even those experience with the product) can always request this meeting at the time team changes to the product.

Code overview – 1 hour

The lead developer will run through some high level code structures that relate to the product the team is about to start work on.

This presentation occurs when a developer on the hasn’t had exposure to the product. Or perhaps there is someone in the team who would like a refresher.¬† The meeting is mandatory when a developer with no exposure to the product. joins the team. Anyone on the team (even those experience with the product) can always request this meeting at the time team changes to the product.

This presentation may also have a more targeted approach and may be called when the team is about to start work on a particular part of the system.

Further reading

You can return to our Agile process introduction for higher level topics.