Modèle de Kano
Satisfaction
Exciters
Performance
Basics
Présence
fonctionnalité
Le processus de responsabilité
Responsibility
Obligation
Shame
Justify
Lay Blame
Denial
Quit
Source: Christophe Avery, conseiller sur le leadership responsible et le travail de groupe
Six simple KPIs
OnProduct
Index
Innovation
Rate
Strategic
Alignment
Index
Usage
Index
Product
Availability
Installed
Version
Index
Innovation Rate
Building new vs. sustaining existing
What percentage of your product is spent
on
building new functionality
vs. maintaining the existing
vs. expanding capacity?
2010 IT BUDGETS
29%
Build New
Maintain
53%
Expand
18%
Innovation Rate
Which is better ?
29%
52%
Build New
10%
Maintain
Build New
53%
Expand
Maintain
Expand
38%
18%
Strategic Alignment Index
Software to support strategic vision and IT strategy
High
Strategic Alignment Map
Highest benefits are
most likely realized
when building these
products or features
Business
Strategic
Alignment
= Product
Size of Bubble = TCO
Low
Low
IT Strategic
Alignment
High
Strategic Alignment Index
High
Strategic Alignment Map
Highest benefits are
most likely realized
when building these
products or features
Business
Strategic
Alignment
= Product
So why do these
get built ?
Size of Bubble = TCO
Low
Low
IT Strategic
Alignment
High
TCO (Total Cost of Ownership) and
alignment are some variables that can be
used in backlog ordering
On-Product Index
Making sure team can deliver
Percent of time team spends working on product stuff
(eg. Things that create value)
Generally, higher is better
Task switching destroys efficiency and quality, and can actually
make you less intelligent
100
Working time available per project
90
Loss to context switching
80
Percent
70
60
50
40
30
20
10
0
1
2
3
4
5
Number of simultaneous projects
Source: Gerald Weinberg, Quality Software Management : System Thinking
Product Availability
Customer access, usability, and support
Support
Execution
Product
Performance
Operational
Excellence
Product
Availability
Usage Index
Do people actually use the functionality you build ?
Percent of users using
100
Build things that people will
actually use.
80
60
If they aren’t, try to figure out why
and drive more usage. If you can’t,
why do you have the feature ?
40
20
0
0
5
Times used per time period
10
Higher tends to be
better
Installed Version Index
Monitoring product absorption
What percent of your customers are on your latest (n) release ?
Version 8.0
Version 7.X
3%
23%
Version 6.X
Version 5.X
45%
29%
Any KPI by itself provides very little information.
KPIs are all interconnected
Innovation
Rate
Version
Index
Strategic
Alignment
Usage
Index
On-Product
Index
Availability
Index
Using KPIs provides a high-level proxy of actual value delivered
by software products
Innovation
Rate
Strategic
Alignment
On-Product
Index
Availability
Index
Usage
Index
Version
Index
29% 50% 80% 99% 35% 70%
$0.29
$0.15
$1
$0.13
$0.13
$0.05
$0.03