The data combo helping teams understand sprint health and manage risks

[#1]

When you view your Backlog in Jira, how easy is it to understand which issues are off track and at risk of missing deadlines? How do you know just how ‘in progress’ an In Progress issue is? Can you quickly scan to see if there’s real activity on it?

Imagine if sprint and issue data was presented in a way that made it easy to spot risks and make adjustments.

With the new Backlog view in Team Insights for Jira, it's ridiculously easy.

Team Insights for Jira was built to help you understand the true status of an issue beyond, well, Status. It gives you a timeline activity view that combines user activity from Jira with development activity from Git repositories to paint a much clearer picture. And the Backlog view presents your project timeline organized by sprints, which you can expand to see the finer details of included issues.

Understand the progress of a sprint (and how you got there)

Daily activity summaries on the Sprint level show adjustments to the sprint on that day – e.g. if an issue was added or removed. This is helpful for tracking how well you planned ahead, and seeing if you needed to adjust what’s included in a current or upcoming sprint.

 

As a planner, you are relied on to continually stay on top of your team’s project status, and stay ahead of any potential problems. Team Insights for Jira makes quick status checks easy and obvious. And it provides you with warnings about risks, such as if a sprint isn’t started on time or if issues aren’t being completed fast enough to satisfy the current sprint end date. 

 

Know what’s impacting a sprint, based on activity

Your sprint is at risk? Time to follow up with your team. But first, let’s see what’s causing it. 

Expand the sprint, and see a timeline activity view of its associated issues. The boxes on the timeline indicate an update was made to the issue on that day. It could correspond to comments, status changes, or development work like commits and pull requests. 

But it’s easy and obvious to spot issues like:

• An issue that’s In Progress but has no activity for 4 days 
• Multiple pull requests still open on a sprint that ends in 2 days. 

Hovering over an activity box will give you a summary of what changed on that day. And links out to the issue and associated Git hosting providers are easily accessible (to see the full details of a pull request, for example). If the day included pull request activity, you can see how long its been open or how long it took to move from open->close.

These insights are free! Give them a try.

If your team works in sprints, and you’re happy with the status info and warnings you’re getting today. That’s awesome. Congrats. Keep on rocking! 

But if understanding real status and seeing risks isn’t as easy as you’d like it to be, why not give a new free tool a look.

By the way, the Backlog view in Team Insights for Jira isn’t just great for reacting to sprint info - it’s also your key to being more proactive.

Planners are using it to: 

• Drive their team standups and proactively look at the day or week ahead. How? They sort by Assignee, see what’s on their plate, and see everything they’re actively working on (or not).
• Run more impactful retrospectives. How? They look back and get insights on what went to plan, what didn’t, and, most importantly, why. 

By bridging the gap between Jira and Git - and displaying it in a way that’s easy to understand - Team Insights for Jira is an invaluable tool for planners and team leads. 

Install Team Insights for Jira - for free - and help your teams work more closely together; while avoiding ad-hoc updates and unnecessary meetings. That's a win-win for everyone.