--- 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 --- # Connect EAP and CWM # Connecting EAP with Collaborative Work Management {#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 Connecting EAP with Collaborative Work Management The integration between Enterprise Agile Planning (EAP) and Collaborative Work Management (CWM) enhances visibility and streamlines planning for Agile teams by connecting strategic program planning with team-level execution within a single system. This connection eliminates silos and improves delivery predictability by allowing program managers and release train engineers to define Program Increment (PI) objectives, align Epics, Features, and Stories, create sprints, and manage cross-team dependencies in EAP. Teams can then plan and execute sprints, manage Agile stories alongside operational tasks, and track progress in CWM, all while maintaining alignment to enterprise priorities. Show full answer Show less ## Key Features * **End-to-End Transparency:** Leadership can track progress against PI goals through EAP, while teams adapt to changing priorities within CWM. * **Integrated Workspaces:** Linking EAP teams to CWM automatically creates a new Space and Board in CWM, bringing over existing work items for seamless sprint planning and execution. * **Sprint Synchronization:** Existing sprints and their scheduled work sync automatically from EAP to CWM, including sprint name, state, capacity, and dates---even for non-calendar-based iterations. * **Work Status Updates:** Teams update work progress directly from the CWM Board; sprint completion and management of incomplete items (moving to backlog or next sprint) are handled within CWM. * **Controlled Sprint Creation:** New sprints are created in EAP through Planning Intervals (PIs) defined for the parent Agile Release Train (ART) and then sync to CWM for team scheduling. ## Practical Workflow for ServiceNow Customers * EAP administrators connect EAP teams to CWM, which automatically sets up corresponding Spaces and Boards in CWM. * Existing work items assigned to the EAP team are filtered and displayed on the CWM Board, streamlining sprint planning and execution. * Team members must have appropriate CWM access and the CWM user role (\[sncwm.cwmuser\]) to collaborate effectively. * Teams manage current work, create new work, and update progress directly within CWM, with status reflected back in EAP dashboards. * Sprint management is centralized in EAP for consistency, while execution and daily updates occur in CWM. ## Benefits for ServiceNow Customers * Improved alignment between strategic planning and team execution reduces context switching and ensures all work---planned or unplanned---is accounted for. * Enhanced delivery predictability through clear traceability of priorities from enterprise level to team tasks. * Consolidated Agile and operational task management within CWM supports efficient sprint execution and retrospectives. * Leadership gains real-time visibility into progress against PI goals, enabling better decision-making and planning. Enhance visibility and streamline planning for your Agile teams by connecting Enterprise Agile Planning (EAP) with Collaborative Work Management (CWM). ## Overview of EAP-CWM connection {#cwm-integration-with-eap__section_qls_mtr_3hc} The EAP-CWM integration enables organizations to connect strategic program planning with team-level execution in a single system, eliminating silos and improving delivery predictability. Using EAP, program managers and release train engineers can define Program Increment (PI) objectives, align Epics, Features, and Stories, create sprints for teams, and manage cross-team dependencies. After completing a PI, they can conduct PI retrospectives and update roadmaps for the next cycle. These capabilities ensure that enterprise priorities are clearly structured and traceable across all levels. By linking EAP to CWM, product owners and team members can plan and execute sprints, manage agile stories alongside operational tasks such as incidents. They can also track progress and hold team-level retrospectives, all within the same workspace. This connection between the applications reduces context switching and ensures that both planned and unplanned work is accounted for, without losing alignment to strategic goals. The result is end-to-end transparency where leadership can track progress against PI goals through EAP, while teams maintain flexibility to adapt to changing priorities. ## Workflow of EAP-CWM integration {#cwm-integration-with-eap__section_wgj_ntr_3hc} 1. EAP admin connects an EAP team to CWM. See [Connect an EAP team with CWM](https://www.servicenow.com/docs/NkM1cZBLHrQiZtM22Z8MPw "Establish a connection to CWM by setting your EAP team's Agile tool to Collaborative Work Management."). 2. A new Space and Board are created for this EAP team in the CWM workspace. 3. Existing work items assigned to this EAP team are brought over to the newly created CWM Board through Connected Work filters. 4. Sprint planning view is enabled for this CWM Board where the existing work items and sprints are automatically shown. 5. Check team's access to CWM and provide the CWM user \[sn_cwm.cwm_user\] to all team members. 6. EAP team can start creating more work, manage current work, and update progress directly from the CWM Board. See [Sprint planning in CWM](https://www.servicenow.com/docs/H6gzUkviq3mx8JiXdvcYKQ "Plan, track, and manage work for your teams in the Agile methodology using Sprint planning in Collaborative Work Management."). 7. The team's progress and work status is reflected back on the Team dashboard in the EAP workspace. See [EAP Agile Team dashboard](https://www.servicenow.com/docs/Fw6wCrSSYp_OhOxdYu26PA "The Agile Team dashboard provides you with sprint progress and team performance details for an Agile team in the Enterprise Agile Planning (EAP) workspace.") {#cwm-integration-with-eap__ol_xtz_lvr_3hc} ## Creating or managing sprints for EAP teams in CWM {#cwm-integration-with-eap__section_sdx_yzg_jhc} For EAP teams integrated with CWM, existing sprints and their scheduled work automatically sync to CWM. These details are displayed in the Sprint Planning view on the CWM Board. Sprint name, state, capacity, and dates all sync automatically from EAP to CWM, including for Agile teams that use non-calendar-based iterations. As the team progresses through assigned work, they can update the work status directly in the Sprints section. The sprint can be marked Complete from this view and any incomplete work items can be moved either to the backlog or the next sprint, if it exists. New sprints for the team must be created in EAP. After creating new sprints in EAP, they will sync to CWM, allowing the team to schedule work into these sprints from CWM. Note: Sprints for EAP teams are not created directly at the Agile team level. Sprints are created automatically when a Planning Interval (PI) is defined for the parent Agile Release Train (ART) in EAP and sync to CWM automatically.