Maintaining separate point velocities for FE and BE teams

[shalini_kulkarni]

Our team has a good idea of how to break down Epics, stories, tasks and sub-tasks, however I have a question re: displaying the estimates.

Our team is made up of front end and backend developers, and has recently started estimating story points. Since we are all working from the same project and same sprint, even if we break up the tickets into FE and BE tickets, I wanted to ask if there is a way to maintain/show two team velocities to help with sprint planning, as the resources and effort differ between the teams per ticket (e.g. one ticket may be 3 points for FE but 8 for BE, and we need to take into account when planning the sprint so neither team is under/overloaded) ? Or is there a suggested workaround to address this?

[Bill Sheboy]

Hi @shalini_kulkarni  -- Welcome to the Atlassian Community!

I do not believe you can do that with out-of-the-box JIRA cloud.  There are probably some marketplace add-ons that can do it, if you want to buy them.  If you have any dashboard gadget add-ons, you could probably build filters to show separate velocities.

As a work-around, you could always export the data and use a spreadsheet to build more accurate velocity charts than JIRA would provide you.

There is one more path, as you have noted the team just started sizing work with story points:

• As the team gains experience splitting down work, the pieces often become similarly sized
• At that point, it is no longer necessary to size; you just count pieces instead
• When you do that, you can use the built-in dashboard charts to show velocity over time as counts of things, splitting by different filters
• Eventually leading the team to see counting by skill made visible WIP and knowledge silo issues.  Perhaps working on those issues reduces the need to measure by skill areas.

Best regards,

Bill