Skip to content

Sprints

Devin Walker edited this page Mar 7, 2018 · 5 revisions

During a sprint, the task board is at the center of everything you'll do.

  1. Make sure to bookmark the sprint milestone with the appropriate filters in place for easy access.
  2. Make use of labels and pipelines, and drag and drop issues into correct places as you progress.

It's important that everyone involved with the project uses the board actively.

Sprint Kickoffs

Before a sprint begins we will met to discuss the sprint goal and what issues are contained within.

Daily Standups

Daily standups take place on Slack within the #development-standups channel. The stand up should be created when you begin your day.

The standup should contain:

  1. What you did yesterday
  2. What you're doing today
  3. Any blockers or difficulties

Posting your individual standup in the morning helps set the stage for the day and allows the project managers to review any potential holdups to the overall success of the sprint.

Things to keep in mind for standups:

  • Don't spend too much time talking about work already done
  • Talk more about difficulties or blockers preventing you from moving forward

Sprint Retrospectives

When the sprint finishes, we discuss whether the sprint matched our definition of success and discuss what we can do to make the next sprint even more successful. Restrospectives last 30-45 minute and the goal of these retrospectives is to:

Start, stop, or continue

  1. Be honest

We close our retrospectives by verbally repeating what our action items. A lot can come up during a retrospective, so this final step helps cut through the clutter and ensures everyone understands who is responsible for what.

Leftover work

O team may not close every issue attached to your Milestone – that’s just life. Are they open because your team didn’t have enough time, or are they open because they’re no longer relevant?

Clone this wiki locally