- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2023 01:18 PM
I am familiar using agile components of Epics, Features, Stories and Tasks which allow me to segment my work from large efforts down to individual tasks. In ServiceNow, I have to go from Epics right to User Stories. I would like to segment work at the Feature level. Is this something we need to customize?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2023 01:33 PM
Feature is a superclass of Stories, Enhancements and Defects (and Story a superclass of Epics). I'm not sure about the original intent of that inheritance structure, but I think it's so different aspects of Agile work can roll up to the Feature concept depending on your role as requester, manager or developer.
The way I think about how these are used is:
Epic--scrum master's map of a large body of long-term work
Enhancement--a customer-generated request for a specific feature addition or improvement
Defect--a customer-generated request for a specific fix
Story--the developer's implementation record for either an Enhancement, a Defect, or part of an Epic
Scrum task--individual breakdown of parts of a story
We've had internal discussions on how to deal with the topology, since planners want a top-down hierarchy of records but ServiceNow doesn't relate them that way--enhancements, defects and epics can all be parents of a single story, and a list lookup of rm_feature will show them all in parallel. Generally I think Agile teams should break work down by Epic and Story while customers primarily interact with Enhancements and Defects.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2023 01:33 PM
Feature is a superclass of Stories, Enhancements and Defects (and Story a superclass of Epics). I'm not sure about the original intent of that inheritance structure, but I think it's so different aspects of Agile work can roll up to the Feature concept depending on your role as requester, manager or developer.
The way I think about how these are used is:
Epic--scrum master's map of a large body of long-term work
Enhancement--a customer-generated request for a specific feature addition or improvement
Defect--a customer-generated request for a specific fix
Story--the developer's implementation record for either an Enhancement, a Defect, or part of an Epic
Scrum task--individual breakdown of parts of a story
We've had internal discussions on how to deal with the topology, since planners want a top-down hierarchy of records but ServiceNow doesn't relate them that way--enhancements, defects and epics can all be parents of a single story, and a list lookup of rm_feature will show them all in parallel. Generally I think Agile teams should break work down by Epic and Story while customers primarily interact with Enhancements and Defects.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2023 09:20 AM
Hi, av8rr,
Features are a part of the Scaled Agile Framework solution on the platform. I'd be happy to walk you through both solutions, if you would like more information.
Thank you!
Janeen Osselborn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-13-2023 09:15 AM
I use Child Epics to represent Features, and start all the Feature Names with "FTR:". It works very well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2025 11:28 PM
How ? Can you just elaborate how i can do this .
