--- sourceDocument: Australia Strategic Portfolio Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-business-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Integration between EAP and Agile Development 2.0 # Integration between EAP and Agile Development 2.0 {#ariaid-title1} Release version: Australia Updated August 25, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Integration between EAP and Agile Development 2.0 This integration enables synchronization between Enterprise Agile Planning (EAP) and Agile Development 2.0, allowing ServiceNow customers to maintain consistent planning and tracking data across both applications. By enabling theSync with Agile Developmentoption in the EAP configuration form, key tables and records such as iterations and sprints are synchronized, streamlining agile project management workflows. Show full answer Show less ## Key Features * **Table Synchronization:** * EAP's `Enterprise agile iteration [snapwadvancedeapiteration]` table syncs with Agile Development 2.0's `Sprint [rmsprint]` table. * **Sprint Creation and Updates:** * Sprints should be created primarily in EAP; this action automatically creates or updates corresponding sprints in Agile Development 2.0. * If sprint dates in EAP overlap with existing Agile Development 2.0 sprints, new sprints are not created to avoid conflicts. * Planned start and end date fields for sprints in Agile Development 2.0 become read-only and are derived from EAP's business calendar or iteration dates. * Updates or deletions of sprints in EAP are reflected in Agile Development 2.0 accordingly. * Reference fields link Agile Development 2.0 sprint records back to their parent EAP iteration and team. * **Story Creation and Updates:** * Stories scheduled for sprints within the integrated configuration are accessible and trackable in Agile Development 2.0's Agile board. * Changes to story details or progress are synchronized bidirectionally between EAP and Agile Development 2.0. * Reference fields on the Agile Development 2.0 `Story [rmstory]` table connect stories to corresponding EAP teams, iterations, configurations, and parent work items. * Story rescheduling or moving to backlog in one application updates the status in the other, ensuring consistent backlog and sprint management. * Story records for EAP are stored by default in the Agile Development 2.0 `Story [rmstory]` table. ## Benefits for ServiceNow Customers This integration provides a unified agile planning and execution experience, reducing duplication and manual updates across EAP and Agile Development 2.0. Customers gain synchronized sprint and story data, improved transparency, and streamlined agile workflows. The integration supports consistent sprint scheduling and progress tracking, enabling agile teams to work efficiently within the ServiceNow platform. While setting up a configuration in Enterprise Agile Planning, you can establish an integration with Agile Development 2.0. Learn more about the tables connected and the way you access the information. In the EAP configuration form, when you enable the Sync with Agile Development option, information of the following tables is synced between the two apps. {#sync-eap-and-agile-2__table_p3h_2qz_21c__entry__2} | EAP tables | Agile Development 2.0 tables | |-|-| | Enterprise agile iteration \[sn_apw_advanced_eap_iteration\] | Sprint \[rm_sprint\] | [ ] {#sync-eap-and-agile-2__table_p3h_2qz_21c} When this sync is established for a configuration, the following are the functionality changes: Sprint creation and updates : * Creating a Sprint is suggested to be done from EAP. * Creating a Sprint in EAP creates a related Sprint in Agile Development 2.0. If the dates of the Sprint in EAP overlap with a record in the rm_sprint table, then a new Sprint isn't created for Agile Development 2.0. You can either choose to create sprints for non-overlapping dates or delete the existing sprint from the rm_sprint table. * Fields of planned start and end dates for Sprints in Agile Development 2.0 become read-only, and are derived from the business calendar spans mapped to the iterations in EAP. If an iteration doesn't follow a calendar entry, the dates are derived from the start date and the end date on the iteration itself. * Sprints that an Agile Team creates on a configuration with a single level of iterations sync to Agile Development 2.0 even though they don't follow a planning calendar entry. For more information, see [Creating iterations for teams in EAP](https://www.servicenow.com/docs/T37_C7O_E8v0ZMalO6gIWQ "Create Planning Intervals (PIs) and Sprints directly from the Backlog by entering start and end dates, without setting up planning calendar entries first."). * Updating Sprint details in EAP updates the corresponding Sprint details in Agile Development 2.0. Changing the start date or the end date of an iteration updates the dates on the corresponding Sprint. * Deleting Sprints from EAP deletes the corresponding record from the Sprint \[rm_sprint\] table. * On the Sprint \[rm_sprint\] table, reference fields are created for parent of the EAP iteration and the EAP team this iteration belongs to. {#sync-eap-and-agile-2__ul_av2_hrc_f1c} Story creation and updates : * All Stories scheduled for any Sprints in this configuration can be accessed in Sprints of Agile Development 2.0. You can track the progress of this Sprint from the Agile board. * Any changes made to the story details or its progress are visible in both the applications. * On the Story \[rm_story\] table, reference fields are created for EAP team, iteration, configuration, and parent work item in the EAP fields related list. * If a story is rescheduled to a different sprint or moved to the Backlog on the Agile board, it's updated in EAP and vice versa. {#sync-eap-and-agile-2__ul_jw4_brc_f1c} Note: The Story records for EAP are by default saved in the Story \[rm_story\] table, which is installed with the Agile Development 2.0 plugin.