A colleague at a different client asked about what out-of-the-box JIRA reports we use and how they benefited our team.
Whatever you think about physical card walls versus electronic tools, the fact remains that some teams use them and JIRA is a common one.
Like many good charts, many conclusions can be drawn from the reports below. I have explained one or two specific benefits that my teams have reaped from them:
Sprint Report: We used it to look at what work was added/removed from the current sprint, and what cards were finished. It worked because it enabled us to detect that developers were pulling work ahead while there were still incomplete cards in the sprint. This gave us an opportunity to have a conversation about swarming to get cards over the finish line and breaking down silos.
Velocity Chart: We used it to to compare committed/completed of current sprint verses past sprints. It worked because we detected a trend of increasing overcommitment and the team was able to adjust sprint commentments so that PMs had better projections and the team reversed the growing feelings that they were failures.
Version Report: We use it to project when our project will be finished. It worked because the PM learned that the team was not going to deliver all the scope by the needed date. The PM and the business were able to agree on reduced scope and the version report projected a good delivery date.
Post a Comment