The Tip of the Month, brought to you by Atlassian University, is a monthly series to help master Atlassian tools.  Products are more fun to use when you know all the tricks.

“How do you know what to do, if you don’t know what you’ve done?”

This quote is drilled into my head every time I work out. I meticulously track my workouts, so I can see my progress. While tracking the work we do on our bodies is important, tracking the work we do on our bodies of code is more important.  At the end of every sprint, my team finds it important and useful to take a retrospective look at what we’ve accomplished in the past week’s sprint.  We are then better able to plan work for the upcoming sprint.

The Sprint Report includes the Burndown Chart and a list of completed issues.

To view the sprint report:

  • Click the Agile link’s down-arrow in the top navigation bar, then select your preferred board from the resulting drop downmenu.
  • Click Report, then select Sprint Report from the drop-down at left.
  • Select the relevant sprint from the sprint dropdown.

Next step? Start asking questions – what did we deliver? What did we fail to deliver? Why?

Start your retrospectives the right way. Start them on the Sprint Report in GreenHopper.

Tune in next month

We’ll be delivering you tips and tricks every month, so make sure to keep you eyes peeled next month for another handy GreenHopper tip. If you found this helpful, please visit Atlassian University – interactive tutorials and videos with tons of tips just like this one.

GreenHopper Tip of the Month: Sprint Retrospective...