--- title: Create a scrum task for Agile Development 2.0 stories description: Create scrum tasks in Agile Development 2.0 to break down a story into manageable pieces for your team to work on. You can create one scrum task at a time or multiple scrum tasks at once. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-business-management/agile-development/create-a-scrum-task.html release: australia product: Agile Development classification: agile-development topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Managing your product development using Agile Development 2.0, Agile Development 2.0, Agile Development, Strategic Portfolio Management] --- # Create a scrum task for Agile Development 2.0 stories Create scrum tasks in Agile Development 2.0 to break down a story into manageable pieces for your team to work on. You can create one scrum task at a time or multiple scrum tasks at once. ## Before you begin Role required: scrum\_story\_creator, scrum\_admin ## About this task Team members volunteer for tasks based on their skills and track the hours remaining daily. If the task is not complete within the planned hours, it can be further split into additional tasks. A story is not complete until all its tasks are complete. This task explains how to create one scrum task at a time. To save time, you can create multiple scrum tasks at once. See [Create multiple scrum tasks for stories in Agile Development 2.0](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/agile-development/create-multiple-scrum-tasks.md). ## Procedure 1. Navigate to **All** > **Agile Development** > **Stories** 2. Open a story that you want to create tasks for. 3. From the Scrum tasks related list, select **New**. Alternatively, you can create a scrum task using the Task board view of the Sprint tracking tab, on the Agile board. 4. On the form, fill the fields.
| Field | Description |
|---|---|
| Number | System-generated number for the story. |
| Story | Displays the story associated with the scrum task. |
| Priority | Priority for the task. |
| Planned hours | Estimated number of hours to complete the task. A typical scrum task should take between 4 and 12 hours. If the task requires more than 12 hours, consider breaking it down into multiple tasks. |
| Remaining hours | Estimated number of hours remaining to complete the scrum task. The assigned group member updates this value as work is progressing on the task. |
| Actual hours | After the task is complete, enter the number of hours the task actually took. |
| Type | Type of work involved. |
| State | Current state of the scrum task. The default for a new task is **Draft**. |
| Assignment group | Group that would work on this task. This field is automatically populated from the **Assignment group** of the story from which the task is created. |
| Assigned to | User working on the scrum task. This field is set to the story owner by default. |
| Blocked | Indicator to show that there are issues that prevent the scrum task from progressing. |
| Short description | Brief description of the scrum task. |
| Description | Detailed summary of the scrum task. |
| Work notes | Notes to indicate progress on the scrum task or issues blocking it. |