The Intentional PMO / In practice

AGILEPLACE · TEAM COLLABORATION · LEADERSHIP VISIBILITY

From service requests
to business value.

Shared priorities and clearer work cards helped a Planview team more than double throughput. AgilePlace made progress visible, strengthened collaboration, and gave leadership the context to act.

Follow the process from request to release
THE CHALLENGE

Bring planned improvements and everyday operational work into one trusted view of delivery.

THE APPROACH

Keep context in the cards, connect work to value, and focus leadership on decisions.

THE RESULTS

More than doubled throughput, fewer and shorter meetings, and stronger team ownership.

BEFORE & AFTER

From wish list
to planned delivery.

  1. 01 COE MANAGER

    Set the direction.

    Prioritize Features around management goals.

  2. 02 PLANVIEW PRODUCT OWNER

    Prepare the work.

    Create supporting cards, develop requirements and Definition of Done, and prepare upcoming work.

  3. 03 ADMINISTRATORS

    Build and validate.

    Design and develop solutions in sandbox, gather peer feedback, then complete UAT before deployment.

  4. 04 TEAM WORKING PRACTICE

    Keep progress visible.

    The team “lives in the cards.” Updates, comments, and @mentions keep progress, questions, and decisions visible to everyone who needs them.

Shared priorities and clear responsibilities keep delivery moving.

The team’s original board was called a “wish list.” It captured useful ideas, customer needs, and the team’s knowledge. As demand grew, the team needed a shared way to decide what came next and explain how the work would help customers.

The team built on that foundation together. The COE Manager set Feature priorities, the Product Owner prepared supporting work, and administrators brought their expertise to building and validating solutions.

The change reached beyond planning. AgilePlace became a shared operational view of planned improvements and everyday support. Keeping progress, decisions, and blockers with the work helped the team coordinate and gave leaders context for timely intervention.

Read the transformation story

Requests for enhancements, reports, and process improvements gave the team a valuable starting point. The move from wish list to product backlog made the next step more deliberate: agree on priorities, clarify what successful delivery requires, and show the connection to customer value.

The COE Manager prioritized Features. The Product Owner translated those priorities into supporting work cards and used AI to help synthesize descriptions, comments, and team input into missing acceptance criteria, definitions of done, relationships, and effort estimates. Administrators designed and developed solutions in sandbox, gathered peer feedback, and completed UAT before production deployment.

These responsibilities work together. Administrators focus on the current sprint while the Product Owner prepares upcoming work and the COE Manager shapes later priorities. The team revisits plans as new information emerges. Current updates, questions, decisions, and @mentions stay with the card, making progress understandable without a separate walkthrough.

As the team’s use of AgilePlace matured, the lanes and board features evolved with it. The board grew alongside the team’s working practices.

THE BUSINESS PROBLEM

What does the
work add up to?

WORK ITEM

Product Portfolio
reporting view

Planview Product Backlog
Parent links · across boards

EPICS, FEATURES & VALUE DELIVERED BOARD

Feature

1 parent · capability

Epic

Strategic initiative

Value Delivered

1+ parents · intended benefits

One work card.
More than one
possible outcome.

LEADERSHIP SEES

ValueTimingWork mix
Custom Power BI · Planview OData
Work connected. Strategy visible.

Leadership needed answers to three questions:

  • Value: Which priorities and intended benefits does the work support?
  • Timing: When are new and improved Features planned?
  • Balance: How much work maintains existing capabilities versus improving them?

Two custom Power BI packages use Planview OData to connect delivery management with that leadership view. The same value context helps the team understand the customer impact of its work.

Read the business context

A service backlog records requests and activity. Leadership needs to see how that work advances strategic initiatives, which value it supports, when Features are expected, and how much work sustains existing capabilities versus developing and improving them.

The approach connects two AgilePlace boards. Work cards live on the Planview Product Backlog board. Epic, Feature, and Value Delivered cards live on the Planview Epics, Features, and Value Delivered board. Parent-child links across those boards give every backlog card a direct connection to the capability it advances and the benefits it is intended to support.

AI assists the Product Owner by synthesizing existing card descriptions, comments, and team input into clearer requirements and draft completion criteria, with support for strategic relationships and effort estimates. Two complementary Power BI report packages were custom built from Planview OData for this solution: the AgilePlace Master Dashboard supports management and performance reporting for the Planview Product Backlog Board; the Epic, Feature, and Value Delivered package connects work to strategy, intended value, delivery progress, and planned schedules.

01 / CAPTURE THE REQUEST

The card becomes
the record.

Capture the original need, develop the requirements, and agree on Definition of Done. Keep the administrator’s solution decisions, feedback gathered after sandbox development, validation, and deployment history with the same AgilePlace card.

Original request
The original need, context, and intended outcome.
Requirements and Definition of Done
Acceptance criteria capture the requirements the solution must meet. Definition of Done states when the team considers the work complete.
Solution design and decisions
The administrator’s solution approach, key assumptions, and reasons for decisions.
Peer feedback and validation
Peer feedback after sandbox development, UAT results, and sign-offs, with review and approval responsibilities recorded.
Deployment information
When the Feature reached production and what changed for users.

02 / PRIORITIZE AND CONNECT TO VALUE

One card.
Connected across boards.

The COE Manager prioritizes Features around management goals and customer needs. Each supporting work card connects to one Feature and one or more Value Delivered parents. The Feature connects to an Epic, giving the team and leadership a common view of why the work matters.

01 / AGILEPLACE BOARD · DELIVERY WORK

Planview Product Backlog

The board brings together planned delivery and operational work. Ownership, blockers, and dependencies stay visible as the work changes.

The Planview backlog in AgilePlace, showing delivery lanes and the connected Epics, Features, and Value Delivered board.

INTER-BOARD PARENT LINKS

The same work card connects directly to both parent types below.

02 / AGILEPLACE BOARD · PORTFOLIO STRUCTURE

Planview Epics, Features, and Value Delivered

Epics, Features, and Value Delivered are all cards on this board.

FEATURE 4.3

Portfolio Analytics Builder

EPIC 4

Portfolio Insight & Reporting

The Feature’s Epic parent connects the work to the broader initiative.

  • VALUE DELIVERED

    Wider access to decision-ready data

  • VALUE DELIVERED

    Clearer executive oversight

  • VALUE DELIVERED

    More informed investment choices

Each selected Value Delivered card is a direct parent of the same backlog work card, alongside its Feature parent.

Planview Product Backlog board screenshot, followed by illustrative parent-card relationships using fictional names aligned with the report examples. Select the screenshot to view it at full size. Arrows follow child-to-parent links: across boards for a work card, and within the portfolio board from Feature to Epic.
Explore the board mapping and relationships

Feature to Epic, within one board.

The Epic is a parent card of the Feature on the Planview Epics, Features, and Value Delivered board. A backlog card’s cross-board link to that Feature gives Power BI a path from work to Feature to Epic. The intake prompt uses this established mapping.

Work to value, directly across boards.

The backlog card also connects directly to one or more Value Delivered parent cards on the portfolio board. Those links describe the intended benefits of the work; confirming a realized benefit requires separate evidence and measurement.

Planview AgilePlace board with fictional Epic, Feature, and Value Delivered titles aligned with the reports, retaining the original red parent-child connection lines.
Epic, Feature, and Value Delivered mapping

The Planview Epics, Features, and Value Delivered board with card connections displayed. Features link to their Epic parents within this board.

Card titles are fictional examples aligned with the reports. Connections are preserved from the captured board.

View full-size board
Explore Feature mapping examples across eight delivery Epics
Epic parentFeature cards mapped to this Epic
EPIC 1: Connected Work Ecosystem
  • Feature 1.1: Integration Connector Framework
  • Feature 1.2: Delivery Plan Import
  • Feature 1.3: Shared Data Exchange
EPIC 2: Intake & Decision Governance
  • Feature 2.1: Decision Gate Workflows
  • Feature 2.2: Review Status Tracking
  • Feature 2.3: Agreement Approval Routing
EPIC 3: Trusted Portfolio Data
  • Feature 3.1: Portfolio Data Standards
  • Feature 3.2: Configurable Work Forms
  • Feature 3.3: Role-Based Access Model
EPIC 4: Portfolio Insight & Reporting
  • Feature 4.1: Leadership Insight Dashboard
  • Feature 4.2: Delivery Operations Views
  • Feature 4.3: Portfolio Analytics Builder
EPIC 5: User Enablement & Adoption
  • Feature 5.1: Role-Based Learning Hub
  • Feature 5.2: Guided User Workspaces
  • Feature 5.3: Targeted Update Notifications
EPIC 6: Strategy & Investment Alignment
  • Feature 6.1: Outcome Target Tracking
  • Feature 6.2: Investment Roadmap Planning
  • Feature 6.3: Initiative Alignment Mapping
EPIC 7: Platform Stewardship
  • Feature 7.1: Subscription Oversight
  • Feature 7.2: Platform Health Management
  • Feature 7.3: Platform Support Services
EPIC 8: Intelligent Delivery Enablement
  • Feature 8.1: AI Workflow Assistance
  • Feature 8.2: Structured Activity Capture
  • Feature 8.3: Planning Scenario Workbench

03 / PREPARE THE CARD WITH AI ASSISTANCE

Build the context
into the work.

The weekly prompt helps the Product Owner prepare new cards in three steps. Existing information is preserved, and missing content is drafted from the available input.

  1. 01 / CONNECT

    Associate the work.

    Add missing links to one Feature and the relevant Value Delivered parent cards.

    Preserve existing parent links. The selected Feature provides the path to its Epic.

  2. 02 / CLARIFY

    Clarify requirements.

    Use descriptions, comments, and team input to draft missing requirements (Acceptance Criteria) and Definition of Done.

    If both sections exist, leave them unchanged. Do not invent requirements.

  3. 03 / ESTIMATE

    Size the effort.

    If Card Size is blank, estimate the administrator effort in hours.

    Keep an existing Card Size. The new value is an effort estimate, not actual hours worked.

Read the three-step prompt

Public adaptation of the backlog preparation prompt, using the board names with internal identifiers omitted.

  1. Connect new cards to Feature and Value Delivered parents.

    Review the Planview Product Backlog board in AgilePlace and identify cards created in the last week. For each new card, review its title and description and determine the single Feature and one or more relevant Value Delivered cards on the Planview Epics, Features, and Value Delivered board. If the work card has no Feature parent, add the selected Feature card as a parent. If it has no Value Delivered parents, add the relevant Value Delivered cards as parents. Create these parent-child links across the two boards. Preserve existing parent links and avoid duplicates.

  2. Synthesize input into missing Acceptance Criteria and Definition of Done.

    Review each new card’s description, comments, and recorded team input. If both sections already exist in the description, proceed to Step 3. Otherwise, preserve all existing description content and synthesize the available information into the missing sections. Draft relevant bullets only where the source information supports them, for review by the Product Owner and administrators. Do not invent requirements.

  3. Populate a missing effort estimate.

    If Card Size already has a value, take no action. If it is blank, estimate the administrator effort in hours needed to carry out the card’s requirements and enter that estimate in Card Size.

Ready for planning and reporting.

Relationships establish purpose. Completion criteria support delivery. Effort estimates help the Product Owner organize upcoming work.

04 / PLAN THE SPRINT

Ready for the
next sprint.

A complete view of planned work and operational support helps the team set realistic commitments. Priorities can be discussed against available capacity, while upcoming work is prepared as delivery continues.

  1. CURRENT SPRINT

    Administrators deliver.

    Focus on the agreed work while keeping progress and questions visible in the cards.

  2. NEXT SPRINT

    The Product Owner prepares.

    Develop requirements and Definition of Done, and prepare the supporting work cards.

  3. FURTHER AHEAD

    The COE Manager prioritizes.

    Shape upcoming Features and resolve the decisions that help the team keep moving.

Visibility helps the team focus on finishing work before taking on more. Planning ahead also creates time for Coming Soon notices and training preparation.

05 / BUILD AND VALIDATE

Build together.
Validate before release.

Requirements and Definition of Done guide the work. The administrator designs and develops the solution in sandbox, then gathers peer feedback before UAT and deployment.

DEVELOPMENT

Design and develop in sandbox.

The administrator designs and develops a solution to meet the requirements, keeping key assumptions and decisions with the card.

PEER REVIEW

Gather peer feedback.

After developing the solution in sandbox, the administrator gathers feedback from peers and uses it to refine the solution.

USER ACCEPTANCE TESTING

Confirm it meets the need.

Complete UAT and record the sign-offs. Keeping clear records of who built, reviewed, tested, and approved supports separation of duties.

06 / RELEASE AND COMMUNICATE

Ready for release.
Ready for users.

Communication begins while delivery is planned. When the team deploys a validated change, users have the context and training materials to understand what is new.

  1. AHEAD OF DEPLOYMENT

    Coming Soon

    Alert users to planned Features and prepare training materials while the team completes the work.

  2. AT DEPLOYMENT

    What’s New

    Move the validated change into production and tell users what changed and how to use it.

  3. WITH THE RELEASE

    Keep the record complete.

    Record the deployment information in AgilePlace so the request, decisions, validation, and release remain connected.

07 / REVIEW DELIVERY AND FOCUS ATTENTION

Manage the backlog.
See where to act.

Management views keep progress visible throughout delivery and support the review of completed work. Status, priority, and blockers focus attention on decisions or intervention, while value mapping explains the customer impact behind the work.

02 / DELIVERY MANAGEMENT

Delivery Flow

How is work distributed?

Start with the work that needs attention. Use the card context to decide how to help.

Delivery Flow

Start with priority. Follow through to the work.

The selected view shows 14 High or Critical cards. Focus the discussion on where a decision or intervention will help delivery.

AgilePlace Master Dashboard Delivery Flow report showing 45 Active, 36 In Progress, 9 Completed, and 14 High or Critical, with work distribution, estimated hours, and a cropped work-detail table. Fictional work item titles. The sprint-history column is omitted.
AgilePlace Master Dashboard · Delivery Flow

Status and priority focus management attention. The detail rows connect the discussion to the work.

Static report image · Lane group: Active · Multiple assignees selected. Lane and Priority: All. Work item titles are fictional examples. Detail view omits the sprint-history column.

View full-size report
Explore the other management views
01 / MANAGEMENT OVERVIEW

Board | Command Center

What needs management attention?

Work-item counts, priority indicators, lane distribution, Card Size totals by lane, and delivery detail bring the backlog into one management view.

Use it to review the mix of work and identify where to focus the discussion.

03 / DEMAND MANAGEMENT

Demand & Product Value

What demand is the team managing?

Demand counts, priority, work type, requestor distribution, and intake detail support a view of the requests competing for attention.

Use it to examine the demand mix and prepare prioritization conversations.

04 / DELIVERY FOLLOW-UP

Flow Risk & Blockers

Where is intervention needed?

Blocker events, open and high-priority blockers, recorded blocked duration, event history, and last-activity detail help managers investigate delivery friction.

Use it to focus follow-up on blockers and work that may need attention.

Next, move from managing individual work to seeing its portfolio context.

08 / REVIEW VALUE AND PLANNED TIMING

See the value.
Understand the priorities.

Value mapping gives leaders and the team a shared context for decisions. Compare the work supporting each Feature, see which priorities need attention, and look ahead at the planned schedule.

Portfolio Overview

125 delivered. 39 active. 114 in backlog.

Start with the delivery picture, then examine which strategic initiatives the work supports.

Power BI Portfolio Overview showing 125 delivered, 39 active, and 114 backlog work items, with stacked bar charts using fictional Epic and Value Delivered titles.
Portfolio Overview

Distinct work counts show the delivery picture. Epic and value views explain where that work is directed.

Static report image · Refreshed September 23, 2026 at 14:54 UTC. Epic and Value Delivered titles are fictional examples.

View full-size report

Feature Coverage

Compare progress at the capability level.

Decision Gate Workflows shows 7 delivered, 6 active, and 16 backlog work items in this snapshot.

Power BI Feature Coverage report with a table and stacked bar chart showing delivered, active, and backlog work using consistent fictional Feature titles.
Feature Coverage

Compare delivered, active, and backlog work by Feature to discuss the next priority.

Static report image · Refreshed September 23, 2026 at 14:54 UTC. Visible actual finish date filter: February 10–September 21, 2026. Feature titles are fictional examples.

View full-size report

Upcoming Feature Gantt

See upcoming Features
and their timing.

Eleven Features have dates within October–December 2026. Planned timing supports coordination, advance user notices, and training preparation.

Power BI Planned Schedule showing 11 not-started Features with fictional titles, planned start and finish dates across October through December 2026, and zero cards with date issues.
Upcoming Feature Gantt

Eleven Features are planned across October–December 2026. Overlapping bars make concurrent work visible.

Static report image · Refreshed September 23, 2026 at 14:54 UTC. Board: Planview Epics, Features, and Value Delivered. Lane Class: Not Started. Card Type and Parent / Epic: All. Feature titles are fictional examples.

View full-size report
Explore all seven report views and their filters

Follow one request through the package.

Start in Work Item Detail to see the card and its associations. Feature Coverage groups the work supporting that capability; Epic Coverage brings it into the broader initiative. Value Delivered shows the intended benefits it supports. Overview and weekly completions put progress in context, while the Gantt adds the planned timeline.

01 / OVERVIEW

Portfolio Overview

What is delivered, active, and waiting?

Headline counts and comparisons by Epic and Value Delivered bring the mix of work into one opening view.

02 / DELIVERY

Completed by Week

How is completion activity changing?

Weekly completion counts and date filters support discussion of delivery patterns over the selected period.

03 / EPICS

Epic Coverage

How is work advancing strategic initiatives?

Delivered, active, and backlog work roll up through Features to their Epic, giving leadership a view of progress against strategy.

04 / FEATURES

Feature Coverage

How much work sustains capabilities or advances new ones?

Compare work counts across run-and-maintain Features and Features for improvements and development, with delivered, active, and backlog status visible.

05 / VALUE

Value Delivered

Which benefit categories does the work support?

Work is grouped by its value associations and lifecycle status, giving delivery conversations a business-benefit context.

06 / WORK ITEMS

Work Item Detail

What sits behind the summary?

Review the work’s hierarchy, value associations, status, priority, assignments, dates, effort, and mapping quality. A missing-links indicator highlights classification gaps.

07 / PLANNED SCHEDULE

Quarterly Gantt

When should leadership expect upcoming Features?

Planned start and finish dates show expected delivery against a fixed quarterly timeline. Board, Lane Class, Card Type, and Parent / Epic controls support different planning views. Missing or inconsistent dates are listed as schedule exceptions.

The current example covers October 1–December 31, 2026. Lane Class starts at Not Started and remains editable.

REPORTING WITH INTENTION

Make the numbers
mean what they say.

Clear reporting definitions explain what the numbers represent and what a reader can reasonably conclude.

Know what each count represents.

Use distinct work counts. A card can support several value categories.

Separate delivery from realized benefits.

Completion records delivery. Benefit realization requires evidence and measurement.

Expose missing information.

Flag missing links and invalid dates so gaps remain visible.

Make the reporting scope explicit.

Read each view with its filters, definitions, and snapshot date in mind.

Reporting definitions and scope

Know what each count represents.

The Epic, Feature, and Value Delivered package uses distinct work-card counts. Value categories can overlap, so their rows should not be added together as a portfolio total. The management dashboard’s blocker history counts events; one card can have several blocker events.

Keep delivery and benefit realization distinct.

A completed card records delivery activity. A value association identifies the benefit it supports. Neither establishes a financial return or confirms that the intended benefit has been realized.

Expose missing information.

Missing hierarchy or value links are flagged for review. The Gantt lists missing or invalid dates separately, so unscheduled work is not given an invented timeline.

Make the reporting scope explicit.

The management dashboard has its own board, lane, and visual filters. The Epic, Feature, and Value Delivered guide explains that package’s analytical exclusions, while the Gantt has a separate planning scope. Compare views with their filters and definitions in mind.

Compare the original and current operating model
How the team’s operating model evolved
AreaStarting point Wish listEvolved practice Planview Product Backlog
Request preparationRequests captured valuable customer ideas and the team’s knowledge.The Product Owner prepares supporting work, with AI assistance for missing context, relationships, acceptance criteria, and effort estimates. Administrators focus on building and validating solutions.
Shared prioritiesWork selection relied on individual conversations and judgment.The COE Manager prioritizes Features. Work cards connect to those Features and intended value, giving the team a clear customer and strategy context.
Leadership attentionLeaders understood progress through guided reviews of individual cards.Current card updates and focused management views help leaders act on decisions, priorities, and blockers. Value mapping explains why their intervention matters.
Planning and communicationThe wish list recorded demand as requests arrived.Rolling sprint preparation makes upcoming work visible. Coming Soon notices create time for training, and What’s New communications accompany deployment.
Team collaborationWork often progressed within individual areas of responsibility.Shared updates, clear requirements, Definition of Done, and peer feedback increase collaboration and ownership. The board’s lanes and features evolve with the team.

HOW THE TEAM GREW

From compartmentalization
to collaboration.

Shared visibility changed how the team worked together. Keeping the context in AgilePlace cards reduced time spent reconstructing updates and created more time to solve customer problems.

SHARED INFORMATION

Transparency builds trust.

When people could see what was happening, they became more willing to share updates, ask questions, and help one another. More sharing made the next conversation easier.

CUSTOMER IMPACT

Purpose increases ownership.

Value mapping shows why the work matters and how it affects customers. That visibility strengthened ownership and gave the team a clearer sense of accomplishment.

SHARED EXPERTISE

Quality becomes a team effort.

Requirements and Definition of Done give the team a shared understanding of completion. Peer feedback helps the administrator refine the solution, while lessons from delivery inform future improvements.

Collaboration and faster management decisions helped the team more than double throughput.

RESULTS / THE TEAM’S EXPERIENCE

More delivery.
Stronger collaboration.

Capturing the work and its context in AgilePlace changed how the team and leadership work together.

More than 2×throughput

More work delivered.

Shared priorities, prepared cards, and faster management decisions helped the team more than double throughput.

Fewer.
Shorter.meetings

More time for solutions.

Progress and decisions stay in the cards. Meetings become less frequent and shorter, with discussion focused on what needs attention.

Shared
ownership.across the team

Clearer purpose and impact.

The team sees why its work matters to customers. Transparency builds trust, strengthens collaboration, and gives people a clearer sense of accomplishment.

The record lasts. Requests, requirements, Definition of Done, solution decisions, peer feedback, validation, deployment history, and reasons for rejecting ideas remain available in AgilePlace.

The next delivery is prepared. Rolling planning supports Coming Soon notices, training materials, and What’s New communications at deployment.

Team results reported by the COE Manager. The report images illustrate the working model and show separate snapshots.

DOING THE WORK THAT MATTERS

See it. Own it.
Solve it. Do it.

The board makes work and value visible. That shared understanding helps people take ownership, contribute their expertise, and deliver work that matters to customers.

See it.

Stakeholders see the work, progress, and intended value in a common view.

Own it.

The team understands why the work matters and how it affects customers.

Solve it.

Shared context and peer review improve solutions. Lessons from delivery help shape the next improvement.

Do it.

Prepared work and timely decisions help the team keep delivering.

Platform ambassadors lead by example. By managing its own work in AgilePlace, the platform team demonstrates the adoption it asks of others. Colleagues can see a practical example of how the platform supports day-to-day delivery.

DISCUSSION

Can your team see
why the work matters?

Make the work visible, connect it to customer value, and give the team and leaders the context to act. See it. Own it. Solve it. Do it.

Full-size report