Modèle de KanoExciters

Performance

Basics

Satisfaction

Présence fonctionnalité

ResponsibilityObligation

ShameJustify

Lay BlameDenial

Le processus de responsabilité

Source: Christophe Avery, conseiller sur le leadership responsible et le travail de groupe

Quit

Innovation Rate

Strategic Alignment

Index

On-Product

Index

Product Availability

Usage Index

Installed Version Index

Six simple KPIs

Innovation Rate

18%

53%

29%

2010 IT Budgets

Build New

Maintain

Expand

What percentage of your product is spent on building new functionality vs. maintaining the existing vs. expanding capacity?

Building new vs. sustaining existing

Which is better ?

Innovation Rate

18%

53%

29%

Build New

Maintain

Expand

38%

10%

52%

Build New

Maintain

Expand

Strategic Alignment Map

Strategic Alignment Index

High

Low

Low High

Business Strategic

Alignment

IT Strategic Alignment

= Product

Size of Bubble = TCO

Software to support strategic vision and IT strategy

Highest benefits are most likely realized

when building these products or features

Strategic Alignment Map

Strategic Alignment Index

High

Low

Low High

Business Strategic

Alignment

IT Strategic Alignment

= Product

Size of Bubble = TCO

Highest benefits are most likely realized

when building these products or features

So why do these get built ?

TCO (Total Cost of Ownership) and alignment are some variables that can be used in backlog ordering

Percent of time team spends working on product stuff(eg. Things that create value)

On-Product IndexMaking sure team can deliver

Generally, higher is better

1 2 3 4 50

10

20

30

40

50

60

70

80

90

100 Working time available per projectLoss to context switching

Number of simultaneous projects

Perc

ent

Task switching destroys efficiency and quality, and can actually make you less intelligent

Source: Gerald Weinberg, Quality Software Management : System Thinking

Product Availability

Product Performanc

e

Support Execution

Operational Excellence

Product AvailabilityCustomer access, usability, and support

0 5 100

20

40

60

80

100

Times used per time period

Perc

ent o

f use

rs u

sing

Usage IndexDo people actually use the functionality you build ?

Build things that people will actually use.

If they aren’t, try to figure out why and drive more usage. If you can’t, why do you have the feature ?

Higher tends to be better

Version 5.X

Version 6.X

Version 7.X

Version 8.0

29%

45%

23%

3%

Installed Version IndexMonitoring product absorption

What percent of your customers are on your latest (n) release ?

Innovation Rate

Strategic Alignment

On-Product

Index

Availability Index

Usage Index

Version Index

Any KPI by itself provides very little information.KPIs are all interconnected

Innovation Rate

Strategic Alignment

On-Product Index

Availability Index

Usage Index

Version Index

Using KPIs provides a high-level proxy of actual value delivered by software products

29% 50% 80% 99% 35% 70%

$0.29

$0.15 $0.13 $0.13

$0.05 $0.03$1