What are the out of box definition for Enhancement states? How does your company use those states versus development activities in stories?

[Charles Shiflet]

In the wiki (docs.servicenow.com), stories are well documented.  After creation of a story, the documentation provides information on the fields in the story form:
https://docs.servicenow.com/bundle/orlando-it-business-management/page/product/agile-development/tas...

Such as: 

Story form fields

Field

Description

State

State of the story. Select one of the following: Draft: In this state, the story requirements, such as the description and acceptance criteria, are still being drafted. Ready: In this state, the story is marked as ready to be picked up by the development team. Work in Progress: In this state, the development team works on the story and records their changes in the work notes field. Ready for Testing: In this state, the story is marked as ready to be taken up by a tester. Testing: In this state, the tester works on testing the story based on the requirements provided in the story. Complete: In this state, the development and testing efforts on a story are complete. Cancelled: In this state, a story has been cancelled. The default state for a new story is Draft.

However in the enhancement documentation:
https://docs.servicenow.com/bundle/orlando-it-business-management/page/product/agile-development/con...

Enhancement "state" out of box definitions or any information around the process it was designed to support is missing.  Where can I find the intent of these states, the process the module is designed to support (the detailed process), etc?  If there isn't any, how do other companies using this functionality use it today?

[sachin_namjoshi]

In our instance, we are using idea portal as starting point to collect requirements.

Users can create ideas and after submission demand will be created which will be managed by demand managers.

Demand has OOB integration with ITSM ( change) process to link all objects together.

https://docs.servicenow.com/bundle/orlando-it-business-management/page/product/innovation-management...

Regards,

Sachin

[Alessandro M_]

Hi Charles,

We customized our ENHC states to support our demand management process. We created states of draft, requested, accepted, scoped, approved, and implemented. We don't have any automation today. Personally, I would name them differently because the same state may have different meanings depending on the context.

Let us know what you decide to do, it can help us learn too.

Good luck,
Alessandro

[major li]

hi @Alessandro M_ ,

in your organization, how is the "scoped" state defined?