--- sourceDocument: Brazil Strategic Portfolio Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-business-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil 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: Brazil Updated September 10, 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 within your ServiceNow environment. By enabling the "Sync with Agile Development" option in the EAP configuration form, key data tables and records related to iterations and sprints are kept consistent across both applications, enhancing visibility and coordination for agile teams. Show full answer Show less ## Key Features * **Table Synchronization:** The integration synchronizes the *Enterprise agile iteration \[snapwadvancedeapiteration\]* table in EAP with the *Sprint \[rmsprint\]* table in Agile Development 2.0. * **Sprint Creation and Updates:** * Sprints should be created primarily in EAP; creating a sprint in EAP automatically creates a corresponding sprint in Agile Development 2.0 unless sprint dates overlap with existing records. * Planned start and end dates for sprints in Agile Development 2.0 become read-only and derive from EAP's business calendar or the iteration's own dates. * Sprints created by Agile Teams on configurations with single-level iterations will sync even if not following a planning calendar. * Updating or deleting sprints in EAP automatically updates or deletes the corresponding sprint records in Agile Development 2.0. * Reference fields link sprints in Agile Development 2.0 back to their EAP iteration parent and team. * **Story Creation and Updates:** * Stories scheduled for sprints in EAP are accessible and trackable in Agile Development 2.0's Agile board. * Changes to story details or progress sync bidirectionally between the two applications. * Reference fields on the Story \[rmstory\] table link stories to their EAP team, iteration, configuration, and parent work item. * Rescheduling stories between sprints or moving them to the backlog on the Agile board updates the records in EAP accordingly, and vice versa. * Story records for EAP are stored in the Story \[rmstory\] table installed with the Agile Development 2.0 plugin. ## What You Can Expect By enabling this integration, ServiceNow customers benefit from a seamless synchronization of agile planning data, ensuring that sprint and story information is consistent and up-to-date across Enterprise Agile Planning and Agile Development 2.0. This integration streamlines sprint management, enhances visibility of progress on Agile boards, and reduces manual data duplication between the two applications, resulting in more efficient agile delivery workflows. 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/ciNL2RPJkhqfwrZmVJwJJA "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.