Capacity and Resource Planning for EAP

[Adam Geil]

How should teams handle capacity and resource planning in SPM when the same resources are shared across Project and Agile teams? We're using EAP, so Epics/Capabilities/Features are created as Planning Items, which don't extend the task table, so we cant create Resource Assignments for them.

[Adam Geil]

Our teams use a hybrid model. For us, that means that a percentage of their time is dedicated to projects, another percentage is dedicated to "Agile" work for smaller enhancements that usually get tracked as one or more stories, and then a final percentage of KTLO work. We can track Project and KTLO work, but I'm having a hard time determining how the Agile work would get tracked via Capacity Planning/Resource Management.

[alexankaras]

Planning Items are supported in resource planning assignments for many SPW releases now. For Epics/Capabilities/Features, configure their related lists on all the EAP related form views and you'll be able to create resource assignments for those records.

Should you choose this path, doing a Lens structure in portfolio that brings Epics, capabilities or features under a portfolio plan will be practical. Planned/Approved dates of the EAP records should be maintained to follow the PI/Sprint dates - that would allow using the Capacity panel to manage agile team's capacity more effectively.

Alternatively - an operational resource assignment for these teams can be created to account for the total % of capacity they'll be allocated on their sprints. The sprint capacity in points should be updated accordingly and stories/items sized & planned in sprints via points.

Keep in mind that time cards will not work on planning items - at least as of now.