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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.