Skip to main content
Language Selector

  1. Other Languages

    (machine translation)

Planview Customer Success Center

Connected AgilePlace process flows

  1. Last updated
  2. Save as PDF

Overview

This guide explains how AgilePlace integrates with Planview Portfolios to streamline agile team delivery, enabling teams to plan, execute, and track work seamlessly across platforms. From board setup and project creation to backlog prioritization and real-time progress tracking, this process ensures your teams stay aligned and focused. By syncing cards and tasks between tools, you gain visibility into delivery, reduce manual updates, and support continuous improvement across your Agile work lifecycle.

New to using Portfolios and AgilePlace for agile team delivery? Explore the infographic and table below to learn how the agile team delivery capability works from end to end with the integration enabled.

Process Flow_Agile Team Delivery Connected .jpg

Process step Description
Create AgilePlace board and make available for integration

After creating your board in AgilePlace using a template or a custom setup, set the board to be available for integration with supported Planview products so real-time information about work progress can sync between AgilePlace and Portfolios.

To create new work tasks in a project’s work breakdown structure (WBS) from new cards created on the AgilePlace board, define the card type and the lanes where this work will appear in Portfolios.

For more information:
Create project/epic in Portfolios and flag for sync to AgilePlace When creating a work epic or project in Portfolios, initiate the link between Portfolios and AgilePlace to begin syncing work across platforms. You will also select the default AgilePlace board for the sync.
Set the appropriate tasks in the work breakdown structure (WBS) to sync to AgilePlace

In the Portfolios WBS, designate which tasks to sync to the AgilePlace board. Set the Sync with the AgilePlace flag to create the synced card in AgilePlace. Each task will sync to the defined default board but can be changed to a different board.

Here you can select the option to import AgilePlace child cards, which will automatically create synchronized tasks for child cards of the connected AgilePlace parent card. 
Card is created on assigned AgilePlace board When tasks in the Portfolios WBS are synced to AgilePlace, cards are added to the default drop lane of the selected AgilePlace board. In AgilePlace, add card details and create parent-child connections to cards if needed.
User story created and marked to sync to Portfolios Once you have synced Portfolios to AgilePlace, new cards created in AgilePlace can sync to projects in Portfolios. This creates a new task in the project’s WBS. 
New task created in WBS When you create a new card in AgilePlace and set it to sync to an available Portfolios project in the Parent Card drop-down, the card creates a task in the assigned project’s WBS, complete with card details, start date, end date, and more.
Maintain plan; update milestone/activity status as work is completed  Maintain the project plan by reviewing and updating milestones and activity status in the WBS.
Monitor project progress In Portfolios, review progress using data synced from cards in AgilePlace. This information is used to monitor the project progress and can be viewed within the WBS, work portfolio column sets, and Power BI dashboards. This provides the ability to assess and make real-time decisions with all available information.
Parent/child connectors automatically updated With synced tasks, you can change parent/child card relationships in AgilePlace and the connector will automatically update the parent/child task relationships in Portfolios.
Describe and categorize stories via users, start/finish dates, etc. Clearly define goals for each user story that team members can work toward. Categorize card types to reflect the kind of work in process and set start and end dates to keep track of planned deadlines. Descriptions and categorizations on AgilePlace cards will update task information in Portfolios.
Prioritize backlog Rank stories in the AgilePlace backlog to determine which stories should be worked on first. Use AgilePlace Card Scoring to prioritize work. 
Assign stories to appropriate timeboxes Schedule story cards across timeboxes or sprints, and set work in progress (WIP) limits to avoid overloading team members with work. Use the Agile Planning Series view to visualize how planned stories and delivery dates align to higher-level planning increments, such as program increments (PIs). After planning, teams begin work toward their defined goals.
Time reporting Users enter time via time reporting in Portfolios, or if Planview's Agile Costing solution has been enabled, the connector will automatically populate timesheet data into Portfolios using data derived from cards in AgilePlace.

Team backlog management

Process steps

AP Team Backlog Management Process Flow.png

Process step Description
Create stories Break features down into discrete user stories for the team to work on.
Describe and categorize stories Clearly define a goal for each user story that team members can work toward.
Estimate story sizes Realistically assess the scope of the work that will be required to complete each user story.
Prioritize story backlog

Rank the stories in the backlog to determine which stories should be worked on first. Use metrics in Card Scoring to determine what work should be prioritized.

For more information:
Schedule stories into appropriate timebox Schedule story cards across timeboxes or sprints, and set work in progress (WIP) limits to avoid overloading team members with work. Use the Agile Planning Series view to visualize how planned stories and delivery dates align to higher-level planning increments, such as program increments (PIs). After planning, teams begin work toward their defined goals.

Reports

How are we able to understand what is in the backlog and can be planned within WIP limits?

All Planning Series Report Analytic Report This AgilePlace report allows you to view all the cards that have been assigned to planning increments.

Team execution

Process steps

AP Team Execution Process Flow.png

Process step Description
Assign stories to relevant team members Spread story assignments across the available team members based on available team members' abilities, workloads, and schedules.
Deliver stories Iterate on the work required to complete each user story.
Collaborate on designs and plans using whiteboard The Whiteboard is a tool that you use to create designs and plans while collaborating or brainstorming, similar to an actual whiteboard. You can use elements such as shapes as you brainstorm, and if desired convert text within elements to cards on a specified board. 
Update card status As work is accomplished on each user story, assigned team members can update cards by moving them toward review or completion.

Reports

How are we able to view key metrics based on team execution?

Burndown Chart

Analytic Report

This burndown chart helps teams visualize progress on work that needs to be completed during a specific time period and gauge whether they’re on track to complete their planned work by the deadline. It also highlights how many cards or card sizes may be at risk of missing the deadline. This chart is helpful for team retrospectives to understand past performance and historical trends.

Flow Report

Analytic Report

This chart displays the relative amount of work in progress for each lane or section of a board over time. Variations in the width of the colored bands indicate how smoothly work is flowing, and serve as a visual indicator of potential bottlenecks or workflow constraints. Key takeaways at the top of the chart display the rate teams are adding, starting, and moving cards on the board during a specified date range.

Efficiency Report

Analytic Report

This report displays the amount of in-process work that was active or inactive over a given time period. You can select specific lanes to understand which areas of your board may be inefficient and determine where and how to implement lane WIP limits.

Planned Percent Complete

Analytic Report

This chart compares cards' planned finish dates to their actual finish dates to determine whether each item due on a particular date was finished early, on time, late, or remains unfinished. The ability to toggle between original and current planned finish dates to get a better understanding of how you are performing against your original plan is also supported.

Speed

Analytic Report

This report is used to calculate the amount of time work items take from the time they enter work in progress until they are complete. It consists of a bar chart that displays the number of cards completed in a time period, and a jitter plot that plots cycle time, or how many days it took to complete the work.

Team integration

Process steps

AP Team Integration Process Flow.png

Process step Description
Deliver work using connected agile tools

Teams use their preferred agile team tools to complete work and user stories, with status information visible in Planview AgilePlace. This is supported by Planview's agile integration capabilities which allow organizations to connect one or more agile team tools, as well as multiple federated instances of a given team tool, into Planview AgilePlace.

For more information:

Best practices

Center on continuous improvement

One of the main benefits of agile methodology is the understanding that incremental steps in the right direction will lead to vast improvement over time through an iterative, emergent process. Change can be challenging, and results won’t happen overnight—but committing to continuous improvement will pay off in the long run.

Aim for Minimum Viable Product (MVP

The first iteration isn’t meant to be perfect. Starting with an MVP helps teams gather feedback and experience quickly, setting the stage for future improvements and more impactful results over time.

Use what works

Different teams have different needs—and that’s okay. Let teams choose the methods and timeboxes that suit them best, whether it’s Scrum, Kanban, Scrumban, or something else. The goal is to empower teams to work effectively.

Integrate tools

Give your teams the tools they need to work their way—while ensuring leadership has visibility. Integrated systems, dashboards, and onboard reporting create a single source of truth that’s easy to use and understand across the organization.

Create cross-functional teams

Break down silos by forming teams based on shared goals rather than similar roles. Cross-functional teams help eliminate delays and foster collaboration around creating specific value for the organization.

Limit Work-in-Progress (WIP)

Agile isn’t about being fast—it’s about staying focused. Keep WIP limits in place to help teams concentrate on delivering small, manageable tasks without being overwhelmed.

Visualize work and blockers

Use tools like Kanban boards to make it easy to see what’s in progress, what’s blocked, and where bottlenecks are forming. Clear visualization supports faster problem-solving and better team alignment.

Measure delivery time

Track metrics like flow, throughput, and cycle time to understand how long work takes from start to finish. These insights help identify inefficiencies and support better planning and faster delivery.