We have a customer which we are going to work for at April 10th. We have multiple release streams and we have created a new one for this customer. This way we can plan project in parallel.
This is where we hit a problem. Our sprints starts at April 6th because of another release stream we have. Because of this no issues are planned during the period from 6 to 20 April.
How do I enable issues to be planned during this period? Or how do I change the sprint start dates across multiple release streams?
Hi Mathyn, sprints are always bound to the team, and can't be configured independently. As the goal of a sprint is to have the scope fixed by the beginning of the iteration, Portfolio rather looks at a sprint as a complete "time box", and does not schedule individual days within a sprint. Only of course the total capacity within the sprint duration is matched against the estimates. In order to give a good recommendation I'd have to know a bit more about the setup: If this is one team that works on multiple customer projects in parallel, but remains "stable" as a team, it might be best to just move the start date of the second stream to April 6 as well.
If very granular planning to the level of individual start dates within sprints is required, then it could even make sense to switch the teams to Kanban mode and work an a day-to-day schedule?
If the team actually in practice splits into customer-specific project teams, it might also make sense to split up into multiple teams and model that some people are available in the project-specific team starting from April 10. This might still require to set the start date of the stream to April 6 right now as the sprint cycles get synced, but at least available capacity would be considered only from April 10.
Hi Martin, thank you for your response. As for our setup, at the moment we have two teams: Core and Interns. The Core team can work on multiple projects for multiple customers in parallel. However not every member is involved with every customer. For example: the project starting April 10 will only have one member of the Core team working on it. Say I would split the Core team up into multiple teams (one for each customer for example) would I then be able to select different sprint start dates for each team?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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