Migrating Agile 2.0 Epics to EAP Planning Items (epic type) in Kanban Configuration (scrum)

AngelinaGeest
Tera Contributor

3 weeks ago

We are working on understanding how our Agile 2.0 scrum teams will migrate over to EAP. It's most likely these teams will need the Kanban configuration, as we are currently structured with Themes > Epic > Story > Scrum Tasks. 

 

When I select the Kanban Structure with the Scrum Methodology I've noticed a few things that we need some direction on. 

  1. The Epic level is still considered a SAFe Portfolio, even though the methodology is scrum. 
  2. There is no migration path for Agile 2.0 outside of SAFe to EAP... we need to pull Epics from the rm_epic table over to the Planning Item table to migrate scrum teams 

 

Any direction from other teams who have migrated from Agile 2.0 for Scrum over to EAP and CWM would be so helpful! 

Labels:
0 Helpfuls
  • 1,244 Views
6 REPLIES 6

AngelinaGeest
Tera Contributor
In response to Sunil B N

3 weeks ago

do we not need to convert the scrum epics to planning items to access them in EAP? With agile 2.0 deprecation, does that mean rm_epic, etc are a thing of the past?

0 Helpfuls

Scott Townsend1
ServiceNow Employee
In response to AngelinaGeest

3 weeks ago

Yes, you do need to integrate rm_epic with sn_align_core_scrum_epic.  There is an Integrations option under All->Strategic Planning for internal connections.  Long-term, we'd like to simplify the data model (and have only 1 epic table sn_align_core_scrum_epic), but that will likely take several years (possibly longer).   

 

I hope that helps,

Scott

0 Helpfuls