use case:
We have multiple tiger teams 2-3 engineers with a single backlog, and a single board.
We could create separate boards, but that adds an overhead to SM to change the baord during the stand up and devs tracking the boards.
If we have a single board the SM can switch the view and walk through the agenda, asking each tiger team, on track or not and then switching to assignee status
Hello @Neil Wills
Only a person who is an Administrator for the board can switch the setting for Swimlanes. It can't be changed by an end user.
Hi @Neil Wills
Yes, and...to Trudy's answer:
Would you please describe the flow of your teams' use of the boards and the "standup"? And, how do epics fit into this for the different tiger teams?
I ask because I wonder if quick filters (by tiger team) would be sufficient for the standup part you describe.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We currently have 3 tiger teams, a single sprint period.
Each 3 person tiger team has a given focus for a 2 week sprint.
I could add quick filter for each tiger team, but the convenience of change board swimlanes configuration made me ask the question I did, I knew that it was unlikely there was am end user way of overriding the board configuration.
Epics happened for our current use case is a good theme on stories \ dev tasks in the sprint to see who is assigned to the work.
I should call out that our user stories are current dev tasks and this is why organize under epics is useful, I can see if we were doing things as per scrum that swimlanes organized by User stories would have been useful and see the dev task under Epics or User stories.
We are using advanced roadmaps but engineering dev team members are not as yet using those during the sprint.
as an acting SM, I used the view to show here is our progress on the dev work during the sprint for each tiger team since they basically working against epics.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information. Based on what you described, perhaps try:
With those configurations, anyone who can see the board can change the view without project admin (e.g., scrum master) support.
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.