CTASKS and Stories

[b__SravanS]

In terms of complexity, development and implementation, what are key differences and similarities b/w CTASK and STRY? 

From this, we want to understand why CTASKS cannot be estimated like we do for Stories

[Dr Atul G- LNG]

Hi @b__SravanS 

SCTASK and Story are indeed two distinct modules in ServiceNow, serving entirely different purposes:

1. SCTASK (Service Catalog Task):

   • It is used within the Service Catalog/Request Management process.
   • Tasks can be created and assigned to different teams to fulfill specific catalog items or requests.
   • It focuses on operational work related to service delivery and support.

2. Story:

   • Part of Agile 2.0, used to capture user requirements in an agile development process.
   • Stories allow you to estimate effort, define acceptance criteria, and track the time required for development.
   • It focuses on planning and executing development work within sprints.

[Dr Atul G- LNG]

Sorry my bad, I read it SCtask instead of Ctask. I echo with @Brian Bouchard on ctask. 

[Brian Bouchard]

To add on to what was already said here, a CTASK is a implementation task (Change Task). It is linked to a parent change record and typically has a start and end time that falls within the planned start and end time of the parent change, so in a sense, there is an estimation there.

[Mark Manders]

Stories are part of agile development (small pieces of requirements that will be delivered within a sprint/release), while change tasks are part of Change Management. It's two different processes. You can do estimation on any task, but a change task is there to help in completing the Change Request.