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

AngelinaGeest
Tera Contributor

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! 

6 REPLIES 6

Thank you. None of these actually reference how to bring rm_epic records over as Planning items. 

juliebailey
Tera Guru

We were able to import the Agile Epics [rm_epci] table to the EAP Epic [sn_align_core_scrum_epic] table by following the instructions in the documentation for Import records to Strategic Planning Workspace, which did allow us to map many of our needed fields.  We did run into an issue with the Agile Story [rm_story] records that are child records to our Agile Epics [rm_epic] records, because there is no fields that could be mapped to accomplish this.  Does anyone have a suggestion on how we can map and move the Agile Story [rm_story] records along with their parent Agile Epic [rm_epic] so that everything can be accessed in EAP?

 
There is "parent" field referring to sn_align_core planning item(which can be scrum epic in your case)
This can be configured based on your lens hierarchy in EAP.
If you have parent-child relationshipt b/w Scrum Epic and Story - this will be possible.
And everything would be accessed in EAP.

Let me know if you have further questions.