Hello!
As many scrum teams, we use story point estimations for our tasks. As the scrum master, I want to make sure story points are evenly distributed among the team at the beginning of the sprint.
Is there an easy way to check how many story points are assigned to each person before initiating the sprint? It would be annoying to have to manually scroll through each tickets and add up the total...
Community moderators have prevented the ability to post new answers.
>As the scrum master, I want to make sure story points are evenly distributed among the team at the beginning of the sprint.
Er, actually, no. As a scrum master, you want to make sure that the team knows what they need to achieve during the sprint and you are there to enable them to do it. Story points are not a factor to consider when the team is selecting which item to do next, or who within the team is going to deal with it.
So, no, there's no reporting on "Story Points per person" because Jira Software's Scrum boards are a Scrum tool, and that's not scrum.
The best you can do is a simple search for "sprint = x", and as you say, scroll through the issues and add up the story points.
Story points are not a factor to consider when the team is selecting which item to do next, or who within the team is going to deal with it.
This may be true in your utopian view of scrum, but let's not pretend that story points aren't an indicator of personal performance or helpful measure of productivity, and that having a view of story points assigned/completed per person would be helpful to certain people.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, no. If you're using them as a measure of performance or productivity, then you're a) not using them correctly and b) micromanaging
You should stop doing that immediately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- do you have any suggestion for individual performance reporting other than that within jira or is this something that you think its irrelevant?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Murilo Zilli - I can only recommend that you do not try to do it. Micromanagement is a huge problem in so many places, it does not work.
If you have a problem with a team member not performing, the rest of the team should recognise that, they don't need reports or blame, they will see it. And hopefully simply help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- not talking about micromanaging anyone, just tracking individual performance. Usually a leader would want and need data to understand performance other than just a feeling. You'd also expect different levels of productivity based on how senior someone is within a team, it's hard to measure those things if you don't have any data to support other than a feeling. Even harder as your team grows bigger, very easy to lose track.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, and...I suggest taking a look at Kent Beck's new writings as he develops his book, Software Design: Tidy First, particularly the impacts of using agile delivery measures to assess people performance, team and individual.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Murilo Zilli - measuring individual performance against estimates absolutely is micromanagement. The team should be working together, not having someone dictate what each individual is doing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
On the planning view (where you have the backlog on the bottom and the new sprint at the top), there are three dots next to the list participants icons. Click the three dots and it shows the number of issues and the number of story points per participants. Very useful!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't see the users assigned to the sprint in the backlog view. I can see three dots, but the only options I have are sprint editing and sprint deleting. Any idea why? Could you help me with that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Users are not assigned to sprints directly. You have to infer who is executing the sprint from the information that they are in the team that the board is owned by.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wanted to say that I can't see the Backlog view, as it is shown on the screenshot from Paul, so that I can't see the number of story points per participants.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, ok. Why can't you see the backlog? Do you not have permissions to use the board?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, those quick filters are automatically created on certain types of board. I would guess that you are using a different type of board where you can create your own and are not limited to just assignee filters.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How do I check how many story points were completed in each sprint by each user?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please read the other answer given above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.