lkce16 - agile portfoliomanagement at scale by jasper sonnevelt

Portfolio planning and prioritization at scale

Jasper SonneveltTwitter: @jaspersonnevelt

Lean Kanban Central Europe 2016 | @jaspersonnevelt

1

Problem 1: Autonomy, entrepreneurship, alignment

How to align Product Owners & teams to organizational goals

without telling them what to do?


2

From (department) purpose to tasks

3

Team goals (kpi’s) (quarter - year)

(multiple sprints)Epic

Feature (< sprint)

Why?

Why?

Why?

Why?

(hours)TasksUser story (days)

Team purpose (~1 year)

Goals (~1 year)

Department purpose (multiple years)



4

Department purpose



Feature (< sprint)



Goals (~1 year)

(multiple years)


The Portfolio Wall

Makes work visible for the next 3-12 monthsCreates focus on department goalsAligns teams and is used to manage dependencies


5

Portfolio wall - theoryA portfolio wall shows the work to be done, usually up to half a year ahead:

§ The X-axis shows time, for instance in sprint numbers

§ The Y-axis shows:• in Product Development: teams

o for the whole organisationo for a product, in a tribe, portfolio or business lineo or a single team/squad

• in Business: customer segments or product

Purpose of a portfolio wall:§ Visually prioritizing and planning the work ahead

§ Creating focus

§ Adjusting the plan: changes, team estimates

§ Coordination over teams or customer segments

6


Goals for nowInformation sharingTransparencyBetter discussions and decision making


7


8

Portfolio walls are a great place to share information about what we are actuallypassionate about


9

Teams


10


11

Portfolio Market PlacePortfolio wall is updatedNew work is prioritized and addedChanges are discussedAt the end of the meeting everybody knows what to focus on


12

So what does this mean for my team?

What could we swap it for?

New market development! So new work!

Topics at the portfolio market placeShould we redistribute ourcapacity?

Should we change

which teams work on

work items?

Are we deliveringfastenough?

What epics do we have prioritized toreach these goals

Do we expect theright thingsto happen?

Outcome Output Sourcing

These are thegoals we are

trying toachieve

Status of KPI’s / Goals

Do we need toadjust?


13

Problem 2: alignment on shared objectives

How to move from achieving oneteam purpose to making the whole

department succesful?


14

Setting priorities


15

Setting prioritiesLean Kanban Central Europe 2016 | @jaspersonnevelt

16

Size:S = 1 weekM = 2 weeksL = 4 weeksXL = 8 weeksXXL > 10 weeks

Valu

e

Size

Changing the portfolio wall


17


18

Department purpose



Feature (< sprint)



Goals (~1 year)

(multiple years)



19

Department purpose

Epic

Feature

TasksUser story

Team goals Team purpose

Goals



20

DepartmentPurpose

DepartmentGoal

Team Goal Team Goal Team Goal

DepartmentGoal

DepartmentGoal

PBIPBI

PBIPBI

PBIPBI

PBIPBI

PBIPBI

PBIPBI

TeamPurpose


21

Shifting the focus of the portfolio wall from a team to goals changes the conversation fromindividual contributions to collaborativewins


22

Goals

Workin

Teams


23

Problem 3: alignment on shared objectives at scale

How to sync teams acrossdepartments?


24

Aligning portfolio wallsAcross departments


25

Managing DependenciesLean Kanban Central Europe 2016 | @jaspersonnevelt

26

Results


27

Results so far …Better descisions (significantly)Responsibility lower in the organizationTransparency: greater commitment to thegoalsBusiness Agility has increasedShift: business case -> internalentrepreneurshipProduct Owners have more than onedepartment/team focus


28

Software Development Done Right

Portfolio planning and prioritization at scale

Jasper Sonnevelt


29

lkce16 - agile portfoliomanagement at scale by jasper sonnevelt

Leadership & Management