The Evolution of Agile Portfolio Management for Scaled Agile Success

GoToWebinar Housekeeping

Check your email tomorrow for recording and slides.

If you are having technical problems,

please contact GoToWebinar:

Toll-Free: (855) 202-7959

Long Distance: (805) 617.7049*United States Numbers

Submit your questions

throughout the

presentation here

Trevor Bruner

Product Manager, Tasktop

Meet the presenters

Jasper Sonnevelt

Executive Consultant, LeanKit

Poll

Agile Portfolio Management

Problem: autonomy, entrepreneurship, alignment

How do you align Product Owners & teams to

organizational goals without telling them what

to do?

A solution should enable

• Information sharing

• Transparency

• Better discussions and decision making

The Portfolio Wall

• Provides visibility of work for the

next 3-12 months

• Creates transparency and focus on

department goals

• Aligns teams and is used to

manage dependencies

A breakdown from long term to frequent

Department purpose (multiple years)Long Term

Frequent

Goals (approx. 1 year)

Team purpose (approx. 1 year)

Team goals - KPIs (quarter to 1 year)

Epic (multiple sprints)

Feature (< sprint)

User story (days)

Tasks (hours) Why?

Why?

Why?

Why?

A breakdown from long term to frequent

Department purpose (multiple years)

Predictability

filters up

Goals (approx. 1 year)

Team purpose (approx. 1 year)

Team goals - KPIs (quarter to 1 year)

Epic (multiple sprints)

Feature (< sprint)

User story (days)

Tasks (hours)

Control

funnels down

Completed portfolio

wall shows even

distribution of tasks

over time

Teams or

Organizational

Goals

Time

Topics at the Portfolio Marketplace

Should we change

which teams work on

work items?

Outcome Output Sourcing

Status of KPI’s / Goals

Do we need to adjust?

These are the

goals we are

trying to achieve

What epics do we

have prioritized to

reach these goals

Do we

expect the

right things

to happen? Are we

delivering

fast

enough?

Should we

redistribute

our capacity?

Stickies are nice but....

What about when you’re not co-located?

How can you quickly report on tasks and goals?

Do you have the most accurate view of WIP? etc..

Portfolio Management in LeanKit

Gathering data is automated

Digital boards show real-time status of portfolio

Portfolio level

Program level

Team level

Poll

Let’s re-address the ‘why’ of LeanKit

Information Sharing

Transparency

Better discussions & decision making

What happens when your scale grows?

Not just scale in size, but scale in scope?

Different teams in multiple departments with different needs?

Why not build a single tool to rule them all?

https://xkcd.com/927/

tools tools

There’s no “One Tool to Rule Them All”

Different departments have different needs...and different solutions

So what does this look like?

Use the right tool for the right job...and use something else to tie it all together

Here’s an example...

Imagine a company using:

● CA PPM for high level Portfolio Management

● ServiceNow for ITSM tickets

● LeanKit for prioritization & feature definition & execution

● HPE ALM for test management

How can they achieve:

● Information sharing

● Transparency

● Better discussions & decisions

Communication

It all hinges on communication…

That’s why we had to evolve from sticky notes to LeanKit

But what needs to be communicated?

Same same but different

● Status

● Description

● Summary

● Cross-tool traceability

– Location (i.e. URL in other tool)

– Identifier in other tool

● Filtering

● Routing

● Comments / Attachments

How does this work in real life?

How does this work in real life?

Each integration has it’s own set of rules...

How does this work in real life?

Let’s drill into this integration...

Pssst- don’t tell anyone...

Cross-team communication (and tool integration)

depends more on team dynamics than tooling

Start slow, get team buy-in on process.

You can win many battles by surrounding hold-outs

Can we see some other scenarios?

Can we see some other scenarios?

Can we see some other scenarios?

Can we see some other scenarios?

Scaling agile success

The key to scaling agile is communication…● Between people

● Between teams

● Between departments

Questions?

www.leankit.com

©2017 LeanKit Inc.

www.leankit.com