Planview AgilePlace: Enterprise Kanban Implementation

Full Content

Quick Response (Featured Snippet):
Planview AgilePlace is a native enterprise Kanban platform integrated with portfolio (Portfolios) and execution (AdaptiveWork). It offers: customizable swimlanes, WIP limits with automatic enforcement, CFD (Cumulative Flow Diagram), lead time tracking, integration with Jira/Azure/ServiceNow. Typical implementation: 8-12 weeks.

TL;DR (5 bullets):
– Native Kanban: visual boards, WIP limits, built-in service classes
– Multiple views: swimlanes (by squad, product, epic), filters, grouping
– Planview integration: portfolio → agileplace → financial, single source of truth
– Automatic metrics: CFD, lead time distribution, throughput, SLA
– Enterprise ready: scalability, security, auditing, compliance

Full Article

Why AgilePlace vs. Jira or Azure DevOps

Quick comparison:

When to choose AgilePlace:
– Integrated portfolio is important (you don't want 2-3 tools)
– You need strict WIP limits (manufacturing mindset)
– Value stream at scale (multiple squads, dependencies)
– Robust metrics (CFD, lead time, predictability)
– Enterprise compliance & security

Key Features

1. Visual Boards & Swimlanes

Create a board on AgilePlace:

Name: "Product Delivery — Q1 2026"
Columns: Backlog | Refinement | Ready | Development | Review | Testing | Deploy | Live
Swimlanes: by Squad (Backend, Frontend, QA), by Priority, by Type
WIP Limits: Ready (15), Dev (12), Testing (5), Deploy (2)
Card Fields: Title, Type, Assignee, Due Date, Est. Size, Value, Priority
Filters: (default) Show all except "Done" from last week

Result: clear visualization, drag-and-drop between columns, colors by priority.

2. WIP Limit Enforcement

AgilePlace does not let you violate WIP limits:

Dev column WIP limit: 12
Current WIP: 12 items

🚫 You try to drag item from "Ready" to "Dev"
❌ Error: "Dev column is at WIP limit (12/12)"
✅ You must complete or move an item from "Dev" first

→ Força disciplina, previne overload

3. Service Classes

Different types of work have different tracks:

Class 1: Strategic Initiatives
- SLA: 60 days to start, 120 days to done
- Priority: Highest
- Color: Red

Class 2: Feature Delivery
- SLA: 30 days to start, 45 days to done
- Priority: High
- Color: Yellow

Class 3: Bug Fixes
- SLA: 5 days to start, 10 days to done
- Priority: Medium
- Color: Green

Class 4: Tech Debt
- SLA: 60 days (flexible)
- Priority: Low
- Color: Blue

AgilePlace tracks SLAs by class, alerting you if they are violated.

4. CFD (Cumulative Flow Diagram)

Graph shows item flow:

Y-axis: # de items
X-axis: time (days)

Each column (Backlog, Dev, Testing, Done) é uma banda

Example:
- Backlog grows: demand > capacity
- Dev stays flat: team is at WIP limit
- Testing grows: QA is bottleneck
- Done grows slowly: lead time is long

→ Visualização clara onde está o problema

5. Lead Time & Cycle Time

AgilePlace automatically calculates:

Item "Feature X":
- Entered board: Jan 1 (Backlog)
- Started work: Jan 5 (moved to Dev)
- Completed: Jan 12 (moved to Done)

Lead Time: Jan 1 → Jan 12 = 11 dias
Cycle Time: Jan 5 → Jan 12 = 7 dias
Waiting time: 11 - 7 = 4 dias (em Backlog, antes de Dev)

Report:
- Median lead time: 8 dias
- 95th percentile: 15 dias
- Trend: lead time growing (bad signal)

6. Integration with Planview Portfolios

Items flow from portfolio to agileplace:

Planview Portfolios
(Strategic level: "Feature X approved, Q1 2026")
        ↓
Planview AgilePlace
(Execution level: "Feature X is in Dev, on track")
        ↓
Back to Portfolios:
(Status: "90% complete, delivered in 8 days vs 10 planned")

Result: portfolio managers can view the actual execution status without logging into AgilePlace.

7. Integration with Jira / Azure DevOps

Via Planview Hub (model-based integration):

Jira issues (dev work)
    ↓ (sync via Hub)
AgilePlace board (feature tracking)
    ↓ (aggregated status)
Planview Portfolios (portfolio status)
    ↓
Executive dashboard (real-time status)

Implementation: 90 Days to Value

Phase 1: Planning (Weeks 1-2)

• Workshops: what is the structure (swimlanes, columns, classes)?
• Migration: how many items, history?
• Integration: Portfolios, Jira, ServiceNow, ERP?
• Training: plan sessions for each role

Phase 2: Configuration (Weeks 3-6)

• AgilePlace setup: boards, swimlanes, WIP limits, fields
• Integration: connectors with Portfolios, Jira, Hub
• Data migration: load historical items
• Customization: rules (automation), dashboards, reports

Phase 3: Pilot (Weeks 7–10)

• Select 1-2 squads to pilot
• Go-live with real data (live backlog, items moving)
• Gathering feedback: What is missing? What is confusing?
• Adjustments: customizations, training, processes

Phase 4: Go-Live (Weeks 11-12+)

• Full rollout (all squads)
• All-hands training
• Support (helpdesk available)
• Communication: “AgilePlace is a new tool, not a process change”

Real Use Cases

Case 1: Brazilian Bank — Digital Transformation

Challenge: 30 squads, slow delivery (average 3-month feature), lack of visibility.

Solution:
– AgilePlace with swimlanes per squad
– WIP limits: 15 features per squad max
– CFD showing bottleneck in Testing (2 QAs for 30 devs)

Result:
– Lead time: 3 months → 6 weeks (2x improvement)
– QA hiring: 2 → 5 QAs (resolved bottleneck)
– Visibility: C-suite sees real status on AgilePlace dashboard

For Technicians:

Common customizations in AgilePlace:

Custom Fields:
- Customer Segment (dropdown: Enterprise, SMB, Startup)
- Revenue Impact (estimated $$)
- Dependency (link to other items)
- SLA Class (Strategic, Feature, Bug, TechDebt)
- Deployment window (time box to release)

Automation Rules:
- When item moves to "Ready": notify squad lead
- When SLA expires: escalate to manager
- When completed: update Jira issue + Portfolios
- When testing failed: move back to Dev + notify author

Dashboards:
- Exec: Portfolio health (classes, lead time, SLA compliance)
- PM: Squad board (current items, WIP, blockers)
- Tech Lead: Dev board (who's doing what, cycle time, quality)

Integration APIs:

GET /api/boards/{id}/items → lista de items em board
POST /api/items/{id}/move → mover item para coluna
GET /api/metrics/lead-time → métricas de lead time
POST /api/items/{id}/dependency → vincular dependências

Checklist: Implementing AgilePlace

• [ ] Governance: define board structure, swimlanes, classes
• [ ] Planning: number of items, history, integration
• [ ] Configuration: setup in staging (backup environment)
• [ ] Data migration: upload data (Jira, AdaptiveWork, Excel)
• [ ] Integration: test Portfolios, Jira, Hub, notifications
• [ ] Pilot: run with 1-2 squads for 4 weeks
• [ ] Training: sessions for each role (PM, dev, QA, exec)
• [ ] Go-live: cutover all squads (date to be determined)
• [ ] Support: helpdesk setup, FAQs, wiki

If You Only Do 3 Things...

1. Define swimlanes and WIP limits before configuring: Do not start customizing without understanding the structure.

2. Implement integration with Portfolios: AgilePlace alone is just Jira rebranded. Integrated with Portfolios, it changes the game.

3. Measure lead time and CFD from day one: Tools are good, but metrics prove value.

Frequently Asked Questions

Q: Is AgilePlace just Jira with a different look?
A: No. Jira is dev-centric, AgilePlace is delivery/PMO-centric. CFD, WIP limits, service classes, portfolio integration are much better.

Q: Can I use it without Portfolios integration?
A: Yes, but you lose 50% of the value. AgilePlace + integrated Portfolios is where it shines.

Q: What is the learning curve?
A: Users familiar with Kanban: 2-3 days. New to Kanban: 1-2 weeks.

Q: How much does it cost?
A: Licenses (R$500K-R$1M/year) + implementation (R$150K-500K). Payback: 12-18 months.

Reading & References

• Planview AgilePlace documentation (official)
• Case studies: banking, tech, manufacturing
• Kanban best practices (David Anderson)

Final CTA:

Ready to implement Enterprise Kanban with AgilePlace? TWRT is a Planview specialist. 90 days to value, integrated with Portfolios from day one. Request an implementation proposal.

Related Reading

• Planview Portfolios
• WIP Limits Kanban
• Enterprise Kanban
• Kanban Metrics

Eduardo Salerno

Eduardo Salerno is a specialist in IT portfolio and project management, with extensive experience in Planview implementations and digital transformation. At TWRT, he leads initiatives that connect business strategy with technological execution.

See Full Bio