I want to use JIRA Agile Scrum configuration to aggregate sprint status of the overall project.
Let me give an example to clarify:
There is a Project A and Project B.
Within Project A there are two sprints:
Within Project B there are three sprints:
Let me preface by saying I am new to using JIRA for Agile Scrum.
Are we going down the wrong path here? Is it better to have a global sprint that spans across projects and blocks? The general thinking is the team wants to have control of their own sprint.
How do I generate a aggregate report of all sprints?
Any way to make a combined burn down chart based on dates?
Hi Michael and Michael,
out of the box there isn't a way to aggregate activities tracked under different projects/teams/sprints. This falls under the definition of a Program. Cycle Control add-on is designed exactly with that use case in mind - you can define your initiative as a aggregation of different Agile Boards or Projects on top of that you can see the progress and any custom metrics on a timeline.
Let us know if you are interested in a quick demo at firstname.lastname@example.org.
I'm facing into this same issue - I'd love to hear a definitive answer.
I understand you can create a new board with a custom filter that includes all of the Issues from each of the 'child' Projects - then, in theory, you can use the sprint burndown chart for that 'aggregate' board. BUT, if each project has their own Sprint defined (perhaps even with different names) then the Sprint Burndown report won't work across the whole programme - it will only display one of the Sprints at a time.
I believe the solution (although I'm unable to test it yet) is to have all child projects use the same Sprint - which can only occur if at least one issue (that is assigned to that sprint) appears on each project board. Which is probably not desirable because you don't want issues appearing on multiple boards.
Not sure what the total solution is, but would love to hear from folks doing this.
Hi Michael, you listed quite accurate the challenges if you don't have additional budget and want an Agile board to aggregate the deliverables from multiple boards, you can use one sprint across many boards and projects.
This solution is quite clumsy and each time you need to make changes the filter needs to be adjusted and if one of the Child projects somehow change than the aggregate board won't show the aggregated information.
Then if this is still acceptable, you cannot see all the information in one place, you need to constantly jump between boards. The reports are limited and fixed - you can't customize them.
I hope this helps.
This thread is old, but I just stumbled on it looking for the same answer. Since JIRA does not allow a burndown of burndowns (ala scrum of scrums)... I have found a solution outside of JIRA: Excel.
1) From your Scrum Board > Reports > Burndown Report > select current sprint. Copy the table below the burndown graph and paste it into Excel. Repeat for each additional team/sprint, appending below the previous team's table data.
2) Cleanup formatting. Un-merge cells, remove headers, etc. I use text to columns to strip the timestamp from date. My end state "raw data" looks like this:
3) Insert pivot: rows = Date, Values = "Sum of Increase", "Sum of Decrease".
4) Build a table with the following columns: Sprint Dates, Completed Units (we use Story Points), Work Remaining, Work Forecast. In the Completed Units column I use the following formula: =IFERROR(VLOOKUP(<date>,$Pivot$Range,<row num for "Sum of Dec.">,FALSE),0). In column Work Remaining I start with the Sum of Inc. value, then subtract current day Completed Unit value from previous day's Work Remaining value. In column Work Forecast I take the Sum of Inc. value divided by count of Sprint Dates to get daily velocity, then iterate down until the last day in Sprint has "0" units.
5) Insert Line graph with series "Work Remaining" and "Work Forecast", Horizontal axis is "Sprint Dates". I also adjust for non working days. The final result looks like this:
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs