--- sourceDocument: Zurich Strategic Portfolio Management sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-business-management Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich 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: Zurich 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 coordinate agile iterations and sprints seamlessly across both applications. By enabling the "Sync with Agile Development" option in the EAP configuration form, key tables and records are synchronized to maintain consistency and improve agile planning and tracking. Show full answer Show less ## Key Features * **Table Synchronization:** The Enterprise Agile Iteration table in EAP synchronizes with the Sprint table in Agile Development 2.0, ensuring aligned iteration and sprint data. * **Sprint Management:** It is recommended to create and update sprints from EAP. Creating a sprint in EAP automatically creates a related sprint in Agile Development 2.0 unless date overlaps occur. * **Date Handling:** Sprint start and end dates in Agile Development 2.0 become read-only and are derived from the business calendar spans mapped to EAP iterations or directly from iteration dates if no calendar is used. * **Sprint Updates and Deletion:** Any updates or deletions to sprints in EAP synchronously reflect in Agile Development 2.0. * **Reference Fields:** Agile Development 2.0 sprint records include references to the parent EAP iteration and team, facilitating traceability. * **Story Synchronization:** Stories scheduled in EAP sprints are accessible and trackable in Agile Development 2.0. Changes to story details or progress synchronize bidirectionally. * **Story Metadata:** Stories in Agile Development 2.0 include references to EAP team, iteration, configuration, and parent work item, ensuring context is maintained across the two apps. * **Backlog and Rescheduling:** Moving stories between sprints or to the backlog in Agile Development 2.0 updates the corresponding records in EAP, and vice versa. ## Practical Benefits for ServiceNow Customers * Enables unified agile planning and execution by synchronizing sprint and story data between EAP and Agile Development 2.0. * Reduces manual effort and errors by automating sprint creation, updates, and deletions across both applications. * Ensures consistent sprint scheduling based on business calendars and iteration configurations, improving planning accuracy. * Provides comprehensive tracking of story progress and scheduling changes through integrated boards and records. * Maintains referential integrity and traceability by linking sprint and story records across EAP and Agile Development 2.0. 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/hI_5msbzwq8GkX_~bmLwGQ "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.