MIgration guide for team level agile from Agile Development 2.0 to CWM

[alekhyanema]

Migration Guide

Agile Development 2.0 → CWM

Team-Level Agile Execution · A step-by-step guide for transitioning to Collaborative Work Management (CWM)

Contents

1. Overview
2. Phase 1: Before You Begin
3. Phase 2: Set Up Your CWM Space
4. Phase 3: Create Your Sprint Board
5. Phase 4: Connect Your Work Items
6. Phase 5: Recreate Custom Fields & Columns
7. Phase 6: Set Up Sprint Planning
8. Phase 7: Day-to-Day Execution with Kanban
9. Phase 8: Migration Gaps & Known Limitations

 

Overview

This guide walks Agile Development 2.0 customers through every step needed to migrate team-level agile execution — including sprints, backlogs, stories, and scrum tasks — into CWM. If your team does scaled agile, use Enterprise Agile Planning (EAP) alongside CWM to meet your agile needs. Follow the phases below for a smooth transition.

Phase 1 Before You Begin

 

1.1 Understand What Changes Between Agile Development 2.0 and CWM

Review the key differences at the team level before migrating.

Feature	Agile Development 2.0	CWM
Sprint board	Sprint planning board with native sprints	Board + Sprint Planning view
Backlog	Built-in backlog within sprint board	Backlog section within Sprint Planning view
Work items	Stories and scrum tasks	Stories/scrum tasks connected via 'Connect Work'. Also supports other record types on the task table (e.g. incidents, problems, changes)
Importing other work items	Unified backlog	Connect work
Kanban / tracking	Sprint tracking board	Kanban view in CWM
Epic backlog	Built-in epic backlog	Requires EAP integration (not in CWM alone)
Sprint data history	Stored in Agile Development 2.0 sprint table	New sprint table in CWM
Release Management	Field in Story form	Add the fields in the Story form under CWM view

⚠ Important

Sprint data in Agile Development 2.0 and CWM use different sprint tables. We strongly recommend starting your CWM adoption from a new sprint rather than attempting to import historical sprint data.

 

1.2 Identify Prerequisites

Before starting, confirm the following are in place:

• You have a CWM license (or SPM license) and access to your organization's CWM environment.
• Your team members have been provisioned with CWM roles.
• You have identified all Stories and Scrum Tasks currently active in Agile Development 2.0 that need to move to CWM.
• You have noted any custom fields or columns on Story/Scrum Task forms that need to be recreated in CWM.
• You have agreed on a cutover sprint boundary with your team (a clean sprint start is strongly recommended).

Helpful Links Configuring CWM

 

Phase 2 Set Up Your CWM Space

 

2.1 Create a CWM Space for Your Team

A Space in CWM is the container for your team's boards and docs. Each agile team should have its own Space.

1. Navigate to CWM and click + Create in the left sidebar.
2. Select Space and give it a clear name that identifies your team (e.g., Team Phoenix).
3. Add a description so team members understand the Space's purpose.
4. Click Create to confirm.

Helpful Links Collaborate with Spaces

 

2.2 Share the Space with Your Team

Once the Space is created, invite your agile team and any stakeholders who need visibility using the Share button at the top right of the Space.

1. Open the Space and click Share (top right).
2. Search for the agile user group to share with the entire team, or search for individual team members by name or email.
3. Set the Access level: Editor for team members doing work, Viewer for stakeholders.
4. Click Done to save.

✅ Tip

Use group-based sharing if your organization has Agile user groups set up — this is faster than adding individuals one by one.

 

Phase 3 Create Your Sprint Board

 

3.1 Create a Board

The Sprint Planning Board in Agile Development 2.0 is replicated in CWM by creating a Board inside your Space.

1. Inside your Space, click Create (top right) and select Board.
2. Enter a Board name (e.g., DC Team 1 Sprint Board).
3. Confirm the Space is set to your team's Space.
4. Click Use templates to start from a pre-built layout, or Create to start from scratch.
5. Your new board will open and is ready to configure.

Helpful Links Sprint Planning in CWM

 

Phase 4 Connect Your Work Items

 

4.1 Bring Stories into the CWM Board

CWM uses a Connected work feature to pull existing stories and work items from across ServiceNow into your board. This is the primary way to bring your Agile Development 2.0 stories into CWM without recreating them from scratch.

1. Open your board and click the ⋮ (more options) icon in the board toolbar.
2. Select Connected work from the Connections section of the menu.
3. In the Manage connected work dialog, click + Add new to define a connection rule.
4. Select Story as the work item type, then set conditions to filter by your team's Assignment group or other relevant criteria.
5. Toggle the connection On and click Save.
6. Repeat for any other work item types your team uses (e.g., Tasks, Incidents if applicable).

ℹ Note

• Scrum tasks that are children of a Story will automatically come in with the Story when it is connected. You do not need to connect scrum tasks individually.
• Each connected work condition has a first-time import limit of 100 tasks. You can edit the limit in sys_properties_list.do. Be mindful of the performance impact large conditions have.

Helpful Links Connect Work documentation  ·  Connect Work FAQ

 

4.2 Validate Work Items on the Board

After connecting work items, your board should show all stories and tasks your team is actively working on. Switch to the List view to review everything is correct.

• Confirm that all active stories from Agile Development 2.0 are visible on the CWM board.
• Check that scrum tasks appear nested under their parent stories (expand the arrow next to a Story row).
• Verify that work item statuses look correct.
• Decide whether Closed or Done items from Agile Development 2.0 need to appear in CWM or should remain in Agile Development 2.0 for historical reference only.

🚩 Note

Stories that are already Closed in Agile Development 2.0 may still appear in CWM if they match your connection conditions. Review your connection filters and narrow the conditions (e.g. Active = true) to keep the board focused on current work.

Helpful Links Board Preferences to filter work

 

Phase 5 Recreate Custom Fields & Columns

 

5.1 Add Custom Columns to Your CWM View

There are two ways to create custom fields:

Option A — Org-wide custom fields (e.g., Release, Product, team-specific attributes): Add these at the rm_story table level to the CWM view.

1. Navigate to the rm_story list view and click Edit views.
2. Select CWM view.
3. Click + Add column and select from available fields such as Release, Product, or any custom attribute.
4. Save the view.

Option B — Space or board-specific custom columns: Custom columns added this way are local to the space they're created in.

1. Navigate to Workspaces > Collaborative Work Management.
2. From a Space, select the Board you want to add columns to.
3. In the List view of the Board, select Add column from the column header and select a data type.
4. Enter the Field name and fill in other details as prompted:
   • Label / Dropdown: Enter the options for this field.
   • People: Select the user type and whether to allow single or multiple users.
   • Reference: Select the table to reference.
5. Select Add column.

✅ Tip

Before this step, document all columns your team used in Agile Development 2.0 as a checklist. Work through it systematically to ensure nothing is missed.

 

Phase 6 Set Up Sprint Planning

 

6.1 Switch to Sprint Planning View and Create Your First Sprint

CWM has a dedicated Sprint Planning view that replaces the sprint planning experience in Agile Development 2.0. Use this view to create new sprints and move items from the backlog into a sprint.

1. On your board, click the Sprint planning tab in the view selector.
2. Your connected work items will appear in the Backlog column on the left.
3. Click + (Add sprint) next to an existing sprint, or use the Create Sprint button, to create your first CWM sprint.
4. Set the sprint name, start date, and end date.
5. Drag and drop work items from the Backlog into the sprint to assign them.
6. When ready to begin execution, click Start on the sprint.

⚠ Important

Do not migrate historical sprint data from Agile Development 2.0 into CWM. The sprint table structures are different and are not compatible. Begin CWM sprint planning fresh from your agreed cutover sprint date.

Phase 7 Day-to-Day Execution with Kanban

 

7.1 Use the Kanban View for Sprint Tracking

If your team used the Sprint Tracking Board in Agile Development 2.0 for daily progress tracking, CWM's Kanban view provides equivalent functionality with swimlane and filter support.

1. On your board, click the Kanban tab in the view selector.
2. Use the Filters dropdown to focus on CWM Tasks or the current sprint only.
3. Team members drag cards between columns to update status in real time.
4. Click the gear icon on the right to change the vertical and horizontal lanes.

✅ Tip

Project the Kanban view during your daily standup — team members can update card status live during the meeting, keeping the board accurate without extra effort.

 

Phase 8 Migration Gaps & Known Limitations

The following gaps were identified between Agile Development 2.0 and CWM. Review these with your team before go-live to ensure expectations are aligned.

Gap	Impact	Recommended Action
Epic Backlog	No native Epic backlog in CWM. Epic visibility requires EAP integration.	Set up CWM + EAP integration if epic-level planning is required.
Historical Sprint Data	Sprint tables are incompatible between Agile Development 2.0 and CWM.	Keep Agile Development 2.0 read-only for historical reference. Start CWM from a clean sprint.
Sprint Velocity / Burndown	CWM may not have equivalent velocity or burndown reporting.	Evaluate CWM reporting before go-live. Agree on a workaround with the team.
Sprint Goals	No sprint goals available in CWM out of the box.	Confirm if your team uses Sprint Goals. Add as a custom field in CWM if needed.

Helpful Links EAP and CWM connection