I have a project schedule which I'm attempting to forecast with the help of Portfolio. However, I'm running into a slight roadblock while using the tool. I have up to three different scenario w/in one project plan to find the team's balance between scope bloat, resource capacity and item estimate/weight.
Initially, all three scenarios had the same total developer(s), total items, total item estimates and release parameters (dynamic scheduling) - which resulted in Portfolio generating the same release date for all three scenarios. However, once modifying the resources by scaling their 40hr weekly capacities down to 30, 20 and eventually 0. Portfolio holds to the initial date it had dynamically scheduled. And when adding to the original estimates per item within the stack, Portfolio begins flagging random items and notes them as "cannot be scheduled".
Shouldn't Portfolio instead tell me that additional sprints are required within my schedule based on limited resource capacity and bloated time estimates?
My goal is to baseline my ideal target release date then layer in a 'buffer zone' of scope creep by increasing time estimates to account for bugs typically reported during our sprint verification process.
Any advice?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.