Apologies for this longer thread contribution.....
Another Use Case for cascading/roll-up views that I don't believe is possible via native Rally views is Big Room (Program Increment) Planning. It would be nice if the Team Planning view could reflect all User Stories from child projects when scoped to a higher level project to provide a comprehensive view across all teams for each sprint.
We have our teams sequence their User Stories and work through a preliminary sprint planning exercise during BRPing and then present their team level program increment plan (quarter duration) to the extended program via the Team Planning view. It would be nice if we could scope to program level in the project hierarchy and see our comprehensive program level program increment plan.
It would also be nice if the Iteration Status view could be configurable to show either a flat (current project level) or tiered/hierarchical (current level + child projects) view of all User Stories for the selected sprint.
Going back to Team Planning, the primary use case for that view is interactive sprint planning versus after-the-fact viewing of sprints though the latter is important as well. Velocity is typically set at team not program level so the use case I am referring to is not really for interactive sprint planning but more so for a comprehensive view of sprints in a given program increment across several teams. If all teams are/were considered equal from a skills, knowledge, and experience perspective, then there might be a use case for interactive sprint planning across multiple teams in a single a Team Planning view but I suspect this is rare.
------------------------------
IT Program Manager
Unum
------------------------------
Original Message:
Sent: 05-15-2020 06:17 AM
From: Jack Tomkinson
Subject: User Stories from child projects in team board not rolling up to parent team board
Hi Amy,
Yes I agree this would be a good use case to have the team board as a train board. The current administration and customisation is not ideal.
Thanks for your comments
Jack
Original Message:
Sent: 05-14-2020 10:58 AM
From: Amy Meyers
Subject: User Stories from child projects in team board not rolling up to parent team board
The challenge w the concept of a team board is for a single team does not address the needs of an Agile Release Train that wants to use consistent states. To accomodate that you have to go back to custom fields and custom apps.
The beauty of the work views is that you do not need to do all that administration. It would be nice to be able to have the option to cascade a team board as a 'train' board for this common use case.
Best,
Amy
Amy K Meyers | Senior Product Manager
GLOBAL RISK, FINANCE TECHNOLOGY & TRANSFORMATION
American Express
American Express made the following annotations
"This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you."
American Express a ajouté le commentaire suivant
Ce courrier et toute pièce jointe qu'il contient sont réservés au seul destinataire indiqué et peuvent contenir des renseignements confidentiels et privilégiés. Si vous n'êtes pas le destinataire prévu, toute divulgation, duplication, utilisation ou distribution du courrier ou de toute pièce jointe est interdite. Si vous avez reçu cette communication par erreur, veuillez nous en aviser par courrier et détruire immédiatement le courrier et les pièces jointes. Merci.
Original Message------
Hello @Jack Tomkinson,
I echo @Nik Antonelli comments and want to add some more context, and ideas to help.
The Team Board is for a single team, and the best practice (from a design/architecture/functional perspective) is that the lowest node in the Project hierarchy represents a single team. So, the lowest node in the Project hierarchy is to represent a team. You can find more tips/guidelines in the Rally Online Help or in our Blogs too.
I think you could achieve what is needed by just having your 'Parent' Project node as the lowest level in the Project hierarchy, and using Swimlanes (on Owner). You then automatically take advantage of the CFD/Cycle-Time/Throughput reports on the Team Board, without extra effort to create a custom report. Note: Smart CFD, the use of advanced analytics and ML is upcoming on the CFD report.
Then as Nik mentioned, the metrics will be viewed through the lens of the whole team. If individual capacity/WIP is important then there are ways to generate reports on that, and we can help with further questions around that. Information that would be helpful for this type of conversation are: Are these teams 'permanent'? Are they Kanban teams, and do they manage work via Tasks or just at the User Story level?
I hope this adds more insights into the best ways to use Rally and helps solve what you are trying to achieve.
Cheers,
Christopher