Sprint Goal - New Navigation

Hi there,

I changed the layout to the new navigation and I can't find the sprint goals on the active sprint page anymore (in the old navigation, it was shown below the sprint name). I couldn't find any hint in the documentation. Can I turn them on somewhere or are they gone?

Thank you in advance!

PS: I know I can still edit them in "edit sprint", I want them to be shown on the active sprint page

4 answers

1 accepted

3 votes

Answer accepted

HI @Laura Fromm

In the backlog view it's displayed below the Sprint Name. In the Active Sprint view it's not displayed. You have to click on the Sprint icon next to Complete Sprint button. It will displayed, Sprint Name, Dates and Goal.

Regards

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Seems strange to remove these from the active sprint view. Don't we want all of our teams to keep the sprint goal in mind?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • like this

@Florian Bonniec Couldn't agree more with @Dwight Holman . Having the sprint goal front of mind is very important and so having to navigate away from the board to view the goal seems very unusual.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • like this

A sprint without a visible sprint goal is not worth the issues within a sprint board. Without it, we are forced to live the Feature Factory life, to exaggerate a bit :) @Florian Bonniec

If I can make a wish, please make it even better visible than in the old design. For my taste, the backlog view can stay like in grey and small font. But on the board view, it should be at least as big and bold as the sprint name. The sprint name is just a short representation of the whole the sprint goal IMO which leads to such a hierarchy:

1. In sprint XYZ, we aim to achieve ABC. --> headline

2. For this we plan to task 1,2,3,... --> task board and it's tickets

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • like this

I agree, and I'm very disappointed with the fact that the goal is hidden.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • like this

Where do we make a formal feature request for an adjustment? This small omission by Atlassian made your whole platform much less powerful for building effective teams.

Lack of visibility of sprint goals turns the scrum approach in Jira into Kanban. New demands on my teams' time come up all the time. The way we achieve focus, and from that agility in delivery of value, is by a religious attention to the goals. Our goals identify the value we're trying to deliver. The issues committed in the sprint presume to achieve the goals and thereby deliver the value. If a new opportunity or emergency arises, we check our progress on the goals, and the relative value of the opportunity against the value we had hoped to deliver. When the opportunity is both urgent and higher value, we pivot. That means we also decommit on our lowest-priority goal. Sometimes we even use this relative value assessment to push back on the perceived urgency of an "emergency." After all, every choice of what to work on comes at some opportunity cost. Lack of visibility of the goals makes that rhythm far harder to discipline.

I accept that the goals are still available. 2-3 extra clicks is onerous enough to make it ineffective, especially for workers who are first learning how to participate in a highly Agile team.