Enhancement-type Work and Capacity Planning

JBrians
Tera Contributor

a month ago

I’m curious how other organizations are handling Enhancement-type work in ServiceNow.

 

We currently use Demand Management and convert items to Enhancements based on internal criteria. Management is wanting to include Enhancements in Capacity Planning along with Project work, however, we only use Resource Assignments for Projects, not Enhancements.

 

We’re trying to figure out a few things:

  • How do you define what counts as an Enhancement vs project work?
  • Do you have formal intake/approval process?
  • Do you actually plan capacity for Enhancements, or just work them into team bandwidth?
  • Are you keeping this lightweight (assignment + estimates), or tying into SPM resource management (resource plans/assignments)?
  • How are Enhancements tracked, reported, governed?

It seems like a lot of this is custom by customer, so I’d love to hear how others are approaching it—especially what’s worked vs. what didn’t feel worth the effort.

 

Appreciate any insights or examples!

0 Helpfuls
  • 332 Views
1 REPLY 1

Mariam_Ahmed
Tera Guru

3 weeks ago

Hi @JBrians,
A streamlined breakdown of how we balance, track, and govern Enhancements vs. Project Tasks in one of our ServiceNow projects.

 

The primary differences between the two are outlined below:

 

                                           Enhancement                                                                       Project Task
ScopeSmall-scale feature request or modification to an existing application.An isolated step (like coding or testing) contributing to a broader goal.
Effort & SizeTypically requires fewer than 120--160 IT hours.Can be of varying sizes, but sits nested within a major project plan.
HierarchyOften tied to an Agile Epic, Story, or stand-alone.Must always sit under a parent Project record.
Tracking ToolsManaged via the Agile board or backlog.Tracked using comprehensive features like Gantt charts, RIDAC logs, and specific phase milestones.
LifecycleCan be iterative; usually promoted from an approved Demand .Has a strict start and end date dictated by a dependency chain.


2. Intake & Approval

  • Enhancements go through a simplified, fast-track triage directly with the Product/Platform Owner or Scrum Master.

  • Projects are routed through the standard, rigorous Demand Management workflow for PMO and steering committee approvals.

3. Capacity & Bandwidth

  • We use a "bucket" allocation model. Our platform teams dedicate a steady 20% of their sprint capacity to operational maintenance and enhancements, leaving the remaining 80% for planned project stories. This workflow keeps platform enhancements moving without derailing strategic projects.

4. Lightweight Tracking vs. Heavy Resource Plans

  • Keep it lightweight:Tying small enhancements directly to formal SPM Resource Plans generates massive administrative bloat.

  • Instead, we estimate enhancements using Scrum story points and track them on Agile Boards. We only use SPM Resource Plans for major Projects and Demands.

5. Reporting & Governance

  • Tracking: We use the native rm_enhancement table, which is naturally integrated with Agile Development (converting them directly to Stories as needed).

  • Governance: We run bi-weekly grooming sessions with business stakeholders to prioritize the enhancement backlog.

  • Reporting: We use a simple operational dashboard tracking Active Enhancement Backlog, Delivery Volume by Department etc.

 

If you found this response useful, please mark it as Helpful and accept it as the Solution to help others with similar questions.


Best regards,

Mariam Ahmed.