--- sourceDocument: Brazil Strategic Portfolio Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-business-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Scrum tasks for stories # Scrum tasks for stories in CWM {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Scrum tasks for stories in CWM In Collaborative Work Management (CWM), scrum tasks provide a detailed breakdown of user stories to help agile teams estimate effort, allocate work, and monitor daily sprint progress. Scrum tasks represent individual work units tied to a parent user story, which captures features or requirements from the user perspective. These tasks enable team members to independently pick up and complete increments of work during a sprint, enhancing workflow granularity. Show full answer Show less ## Creating and Managing Scrum Tasks Scrum tasks can be created either manually or generated automatically using ServiceNow Otto: * **Manual creation:** After saving a story, a Scrum Tasks tab appears on the story form where tasks can be added with titles and details. Tasks can also be created inline in List and Sprint planning views. * **AI-generated tasks:** ServiceNow Otto analyzes the story's description and suggests scrum tasks. Users can review, regenerate, and edit these AI-generated tasks before insertion. On the Kanban board, stories with scrum tasks display an indicator icon. Clicking this icon opens a side panel with detailed scrum task information, allowing easy task review without leaving the board. Multiple quick filters help teams focus on specific sprints or task states during daily stand-ups and sprint execution. ## Key Considerations and Limitations * Scrum tasks always belong to a parent story and cannot exist independently or be moved/copied outside that story. * When a story moves between sprints, all its scrum tasks move with it automatically and inherit the parent story's sprint assignment. * Scrum tasks are reorderable only within their parent story but cannot be dragged or copied elsewhere on the board. * Percent complete is tracked only at the task level and not rolled up to the parent story. * Scrum tasks are included when importing stories via Connected Work but cannot be imported independently. * Scrum tasks do not appear in the Backlog section of Sprint planning, only within the active sprint area. * Deleting a scrum task in CWM only removes it from view; the underlying record remains. * Scrum tasks require the scrum task work type to be enabled in your ServiceNow instance, and users need sufficient access beyond Viewer role to add tasks. * Upgrading to version 9.0.0 may cause duplicate scrum tasks if previously imported via Connected Work; this can be resolved by adjusting Connected Work configurations. ## Practical Benefits for ServiceNow Customers Using scrum tasks in CWM allows your agile teams to: * Break down complex user stories into manageable work units for better workload distribution. * Track progress at a granular level within sprints, improving visibility and control. * Leverage AI assistance from ServiceNow Otto to quickly generate task breakdowns, saving time on manual entry. * Maintain alignment between stories and their tasks across sprint changes, ensuring consistency in reporting and execution. * Use Kanban board features to efficiently navigate and filter tasks during sprint activities. Extend your agile workflow in CWM by breaking user stories into scrum tasks. This gives your team the granularity needed to estimate effort, distribute work, and track daily progress through a sprint. In CWM, scrum tasks represent the individual units of work that make up a user story. While stories capture a feature or requirement from the user's perspective. Scrum tasks break that story into steps that team members can pick up and complete independently during a sprint. Scrum tasks are always associated with a parent story and aren't a standalone work items on the board. ## Creating scrum tasks {#managing-scrum-tasks-for-stories-cwm__section_creating_scrum_tasks} You can create scrum tasks manually or use ServiceNow Otto to generate them based on the story content. Manual creation : After a story is saved, a Scrum Tasks tab is available on the story form. From this tab, you can add tasks by entering a title and any relevant details directly on the story. You can also create scrum tasks for stories inline from the List and Sprint planning views. For more information, see [Add scrum tasks to a story in CWM](https://www.servicenow.com/docs/JgR6HX0EgUEf7FTGsgJJUQ "Break down a user story into scrum tasks in Collaborative Work Management (CWM) to distribute work across team members and track daily progress during a sprint."). AI-generated scrum tasks : ServiceNow Otto can analyze the story description and context to suggest a set of scrum tasks. The Create with ServiceNow Otto button on the story form and the inline sparkle button on the Scrum tasks tab both trigger generation. You can review the suggestions, regenerate if the results don't fit the story, and then insert the tasks. AI-generated tasks serve as a starting point and can be edited after they're created. For more information, see [Generate scrum tasks for a story with ServiceNow Otto](https://www.servicenow.com/docs/p60_9ibjKnXIjemWu7BGNA "Use ServiceNow Otto to automatically generate scrum tasks for a story in Collaborative Work Management (CWM) based on the story's description and context, saving time on manual task breakdown."). ## Scrum tasks on the Kanban board {#managing-scrum-tasks-for-stories-cwm__section_scrum_tasks_kanban} When a story has one or more scrum tasks, a scrum task indicator icon appears on the story's Kanban card. Selecting the icon opens a side panel that shows the scrum tasks for that story, so team members can view task details without leaving the board. Quick filters on the Kanban board let teams focus on specific sprints, states, or other columns. Multiple filters can be active at the same time, and a counter at the top of the board shows how many filters are currently applied. This makes it easier to track sprint-specific work during daily stand-ups and sprint execution. ## Scrum task considerations and limitations {#managing-scrum-tasks-for-stories-cwm__section_scrum_tasks_considerations} * Scrum tasks belong to a parent story and can't exist independently as standalone work items on the board. * When a story is moved from one sprint to another, the child scrum tasks also move to the new sprint. * You can reorder scrum tasks only within its parent story. * Scrum tasks can't be moved (drag and drop) or copied outside its parent story. {#managing-scrum-tasks-for-stories-cwm__ul_ikm_mh1_n3c} * Percent complete isn't rolled up from scrum tasks to the parent story. Percent complete is tracked only for CWM tasks. * When a story is imported through Connected work, its associated scrum tasks are brought in automatically along with it. Scrum tasks can't be imported directly through Connected work. * Scrum tasks can't be assigned to a sprint independently. They inherit the sprint of their parent story. When you change the sprint for a story, all associated scrum tasks move to the new sprint automatically. * Scrum tasks aren't displayed in the Backlog section of the Sprint planning view. They're shown only in the sprint section. * Sprint information can't be edited on a scrum task record. * Deleting a scrum task in CWM doesn't delete the underlying record. It's only removed from viewing in CWM. * You can't add scrum tasks if the scrum task work type is disabled in your ServiceNow instance. * You can't add scrum tasks if you have just the Viewer access to the CWM Board. * If scrum tasks were previously imported through Connected work before upgrading to v9.0.0. If stories are then imported through Connected work after the upgrade, duplicate scrum tasks may appear on the board. To resolve this, remove the existing configuration for scrum tasks in Connected work for your Board. {#managing-scrum-tasks-for-stories-cwm__ul_ivv_l4j_m3c} * **[Add scrum tasks to a story in CWM](https://www.servicenow.com/docs/JgR6HX0EgUEf7FTGsgJJUQ)** Break down a user story into scrum tasks in Collaborative Work Management (CWM) to distribute work across team members and track daily progress during a sprint. * **[Generate scrum tasks for a story with ServiceNow Otto](https://www.servicenow.com/docs/p60_9ibjKnXIjemWu7BGNA)** Use ServiceNow Otto to automatically generate scrum tasks for a story in Collaborative Work Management (CWM) based on the story's description and context, saving time on manual task breakdown. **Related concepts** * [Agile work management in CWM](https://www.servicenow.com/docs/wHOwHZJfQKIzWYAZJE1ghg "Run your agile workflow in Collaborative Work Management (CWM), from building and refining a backlog to planning sprints, executing work as stories and scrum tasks, and collaborating with your team.") * [Task dependencies and relationships in CWM](https://www.servicenow.com/docs/xZM7~~sacmtwBv9aaXm9jg "Increase visibility into how work is connected by linking work items directly in Collaborative Work Management (CWM), eliminating the need to track dependencies in spreadsheets or notes fields.")