6. Agile Principles
Customer Satisfaction
Embrace and welcome change
Deliver working software frequently
Business people and developers work
together daily
Build projects around motivated individuals.
Support and trust them.
Face-to-face communication is best
7. Agile Principles (cont.)
Working software is measure of progress
Sustainable development with a consistent
pace
Attention to technical excellence
Simplicity is essential
Best designs and requirements emerge from
self-organized teams
Team reflects regularly on how to improve
8. Overview
1. Trust
2. Give Ownership
3. Teams Make
Decisions
4. Fix Processes
5. Right People
6. Integrity Matters
12. 2004-2008:
high trust companies
out perform low trust
companies by 43%
add 2009:
high trust companies
out perform low trust
companies by 126%
- Great Place to Work
13. trust companies
double performance
over S&P for 10 years
- Great Place to Work
high trust companies
out perform low trust
companies by 300%
- Watson Wyatt study
62. howcan we avoid the temptation to rescue
How
our teams?
you
Ask Questions.like
would
What would you like me to do?
to
How would you like to solve that problem?
What would you like to do?
solve it?
66. Trust/Ownership Model
Trust
& Business Process Energy &
Failure Innovation
Team Trusted
Leadership
No One Cares
Team Accountable
Leader Freed
Command &
Control Conflict
Team Does as Instructed Team Demotivated
No Ownership Mired in Bureaucracy
Leader / Process & Wasted Effort
is Bottleneck
Control
Low Team/Individual Ownership High
67. Stay Positive
How can you help
teams/people take
ownership?
87. Where do we waste time?
Cycle Time:
Average end-to-end process time
From problem detection Problem Solution
To problem solution Cycle Time
Begins and ends with customer.
Customer Request Customer Satisfied
88. Example: Customer Requests Fix
Support Dev team Dev fixes, Customer
Customer
triages triages releases in deploys
requests fix
request request fix pack fix pack
Work: 5 min 2 hrs 1 hr 2 wks 1 hr
Wait: 5 min 3 days 1 wk 2 wks
Value Added Time = 10.5 days
Cycle time = Work + Wait = 38.5 days
Value added time 10.5 days
Efficiency = Total cycle time
=
38.5 days = 27%
Where can we remove the waste?
89. Select Delivery Content
(no travel allowed!)
2 Hours 1 Hour 1 Hour
Need for 7 Days Call & Email 2 Days Call & Email 1 Day Agreement
Scope Def. With Cust With Cust Achieved
X6
Customer Request to Agreement Face to Face Meeting
Working Time = 16 hours Working Time = 8 hours
Elapsed Time = 32 days Elapsed Time = 2 days
Wasted Time = 30 days Waiting Time = 1 days
Efficiency = 6% Efficiency = 50%
Note: Comparison assumes
• 1 day travel to customer site
• 1 day face to face work
• 1 day travel home is excluded since
customer is satisfied
90. As-Is Example
As a new customer, I want to enter my Information only once
in the Small Business Portal
1 Day
Digital 2-4 Wks GOL 2 Wks
SOW Cement
(1 Day)
(2 Days)
Tech Central 2 Days System Test 2 Wks Tech Central
(5 Days) (5 Days) (1 Day)
Process Efficiency = Work / Time = 14 / 56 = 25%
91. To-Be Example
Digital
Cement
1 Day (1 Day)
GOL Work = 14 days
Requirements
(1 Day) Time = 8 days
Planning
(2 Days) Efficiency = 175%
Tech Central
(5 Days)
System Test
(5 Days)
92. Create a Value Stream Map
Select a Process that is relevant to you
Create a Value Stream Map
Calculate Process Cycle Efficiency
Value Added Time
Process Efficiency = Total Cycle Time
How can you change the process to reduce
the waste? (the To Be state)
93
93. Value Stream Maps
Customer value not changed
Reduces the delivery time to customer
94. Process summary
Fix processes not people
Use sticky notes for
improving processes
Map value streams
111. Attract and retain:
first on the basis of integrity
second, motivation
third, capacity
fourth, understanding
fifth, knowledge
last and least, experience.
- Dee Hock, CEO Emeritus VISA International
131. Purpose Based Alignment Model
High
Partner? Differentiate
Market
Differentiating
Who
Parity
cares?
Low
Low High
Mission Critical
132. Purpose Based Alignment Model
High
Do we take Innovate,
this on? Create
Market
Differentiating
Minimize Achieve and
Maintain
or
Parity, Mimic,
Low Eliminate Simplify
Low High
Mission Critical
133. How about an example?
enterprise business
intelligence
product
140. Questions to ask:
1. Who do we serve?
2. What do they want and need most?
3. What do we provide to help them?
4. What is the best way to provide this?