I am presenting my first pass at using FogBugz to track a project with two scrum groups working on the same sprint schedule.
So I created a project with 3 milestones:
- Sprint 1: Group A (work that scrum group A should do in the first sprint)
- Sprint 1: Group B (work that scrum group B should do in the first sprint)
- Project Backlog (work that happens after sprint 1)
The start and completion dates of the 'Sprint 1' milestones are the same.
I set all the Sprint 1: Group A tasks to that milestone and assign those tasks to the five folks in Group A (we don't flag these five people as in Group A in the system at all). I do that same for Sprint 1: Group B tasks. All other tasks remain assigned to the Project Backlog milestone, assigned to people and with estimates.
When I open the status report page for my project, I can see per group burn down charts with the "Burn Down Chart (This Milestone Only)". I can also see the Per-User Timelines, but the "everything this sprint or above" milestone selector means that if I want to see the Per-User Timelines for only Group B folks, I also have to see the Per-User Timelines for Group A folks. And they are sorted alphabetically, not according to which Group they are in. The holds true for Per-User Completion Dates. This problem would only get worse the more scrum groups we have.
I realize that I can break the scrum groups into separate projects whose schedules share the same calendar dates, but then I can no longer see Status Reports for the entire project.
Is there a smarter way to setup two groups on the same sprint schedule that still allows me to get scheduling Status Reports for the whole project?
