Is anyone using Agile Boards and what will you be replacing it with once Agile Development 2.0 goes?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Is anyone using Agile Boards and what will you be replacing it with once Agile Development 2.0 goes?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
53m ago
Hey aislingo,
We're navigating this transition right now. With Agile Development 2.0 officially on the deprecation path (starting with the Australia release), ServiceNow's recommended replacement is Collaborative Work Management (CWM) for team-level execution. If your organization handles scaled agile (like SAFe or multiple Agile Release Trains), you'll want to look at Enterprise Agile Planning (EAP) alongside it.
For my own development team of five, we are actively shifting our day-to-day sprint tracking and backlog management over to CWM. It replaces the legacy Agile Boards with its own dedicated Board, Sprint Planning, and Kanban views.
A few architectural and governance tips as you map out your replacement strategy:
Start with a Clean Cutover: CWM uses entirely different sprint tables than Agile 2.0. Instead of trying to migrate historical sprint data, the safest play is to keep Agile 2.0 read-only for historical reference and start a brand-new sprint in CWM.
Recreating Views & Customizations: If you've customized your rm_story or scrum task forms, you'll need to recreate those in the new CWM views. To maintain a clean upgrade path, I always enforce strict governance—like using our DOTS- prefix for custom configurations and keeping Out-of-the-Box records deactivated rather than deleted. I highly recommend applying that same discipline here so your new CWM workspace doesn't become technical debt.
Connected Work: You don't have to rip the band-aid off all at once. CWM has a "Connected Work" feature that lets you surface existing, active Agile 2.0 stories in the new interface while you transition.
Just double-check your current licensing, as CWM is either a standalone license or included under the SPM (Strategic Portfolio Management) umbrella.
Hope this helps make the migration a bit smoother! Please mark as helpful.
Yogesh
