How to Integrate Agile Development with Resource Management for Sprint Planning in ServiceNow?

[AndreiaR]

Good morning,

I'm currently setting up Agile Development in ServiceNow to manage our sprint planning, and so far, the Agile configuration is working as expected.

Now, I’m trying to achieve the following:
• When a Scrum task  is assigned to a user, the estimated hours should be allocated against that user’s available capacity.
• The user’s work schedule and availability (e.g., working hours, holidays, and time off) should be taken into account.
• I’d like to display a visual board or report that shows the tasks assigned to each user during a sprint. Ideally, the system should automatically highlight or flag when a user’s capacity is exceeded, based on their actual availability.
• The two-week sprint duration should be considered when calculating each user's available hours.

I understand that ServiceNow Resource Management is well-suited for Project Portfolio Management (PPM). However, my goal is to apply similar capacity planning within Agile Development.

My Questions:
1. Is there a way to integrate Resource Management with Agile Development to achieve this type of sprint-based capacity tracking?
2. Does ServiceNow provide any out-of-the-box integration or dashboards for this use case?
3. If not, what would be the recommended approach for configuration or customization?

Any guidance, best practices, or documentation references would be greatly appreciated!

Thank you!

[phil_bool_unifi]

If the agile work is being done in fulfilment of Demands or Projects, keeping those records open and using them to track the resource is the simplest approach. 

However, resource Assignments can be aligned to any task-based activity.  That means you could, in theory, align a resource assignment directly to Story records by displaying the 'Resource Assignment -> Task' related list. 

However, this approach may be very granular, and require a significant amount of management to accurately reflect the work.  Also, this would be very reactive rather than proactive.  You wouldn't be so much planning resource, as just accounting for effort.  Timecards would provide a better experience for this.

A better approach might be aligning Resource Assignment to epics.  That way, as the work gets planned, you'd be able to see the resource assignments in the Resource Management Workspace, and be able to see the different workloads for the teams.   Using Enterprise Agile Planning, you could also call out dependencies.  Similarly, the resource capacity would be captured in the Strategic Planning Workspace's Capacity view, and you can display epics as planning items to take this workload into account when planning your entire strategic journey.