validating delivery performance: benchmarking experiences ... · business value –business...
TRANSCRIPT
-
© 2011 IBM Corporation
Validating Delivery Performance: Benchmarking Experiences at IBM
Wai F. Hom Program Manager, Worldwide Benchmarking and Competitive Analysis IBM Corporation 2300 Dulles Station Boulevard Herndon, Virginia 20171 [email protected]
-
© 2011 IBM Corporation 2
HA
HA
By Wai F. Hom Corporate Lingo Explained
Nice one, son!
I think it means how fast UPS delivers
your eBay packages.
What is Delivery Performance?
-
© 2011 IBM Corporation 3
Agenda
The Problem
Getting Organized
Industry Data
Personnel
Process and Methods
Tools
Going Operational
Adapting to Market Conditions
Business Impact and Results
Lessons Learned Summary
-
© 2011 IBM Corporation 4
The complexity of your organization’s metrics depends on factors such as management commitment, process maturity, and market competitiveness.
JULY
-
© 2011 IBM Corporation 5
Support of complex organizational metrics requires a team to follow a documented metrics lifecycle.
-
© 2011 IBM Corporation 6
Here’s an example of a common metrics lifecycle that many organizations follow. Having a metrics lifecycle does not guarantee success. What is missing, which is a major reason why metrics programs fail to grow?
Monitoring Implementation Definition Requirements
/ Feasibility
- Obtain and review business needs
- Determine feasibility
- Make go/no-go decision
- Prioritize
- Define data primitives
- Define relationships with other metrics
- Define business rules
- Define physical storage requirements
- Define security requirements
- Add metric to metrics repository
- Add metric to data collection mechanism and reports
- Prepare deployment materials
- Review metric reporting volumes
- Review incident reports for problems
-
© 2011 IBM Corporation 7
Metrics
Program
When Finance asks organizations how costs can be reduced, the Metrics program is often suggested, since many people do not see any value.
-
© 2011 IBM Corporation 8
While organizational productivity may show an increasing trend over time, how do you know how good you really are?
1Q04 2Q04 3Q04 4Q04 1Q05 2Q05 3Q05 4Q05 1Q06 2Q06 3Q06 4Q06
Pro
du
ctiv
ity
-
© 2011 IBM Corporation 9
Reviewing your organizational metrics after application baselines are created, will determine if there are performance issues.
1Q04 2Q04 3Q04 4Q04 1Q05 2Q05 3Q05 4Q05 1Q06 2Q06 3Q06 4Q06
Pro
du
ctivity
Account Industry Worst in Class Industy Average
Better
Worse
-
© 2011 IBM Corporation 10
Benchmarking must be added to the Metrics lifecycle in order to drive fact-based decision making within a company and eliminate emotion-based decisions and actions.
Monitoring Implementation Definition Requirements
/ Feasibility
- Obtain and review business needs
- Determine feasibility
- Make go/no-go decision
- Prioritize
- Define data primitives
- Define relationships with other metrics
- Define business rules
- Define physical storage requirements
- Define security requirements
- Add metric to metrics repository
- Add metric to data collection mechanism and reports
- Prepare deployment materials
- Review metric reporting volumes
- Review incident reports for problems
Benchmarking
- Compare metric against industry benchmark
- Conduct deep dive analysis
-
© 2011 IBM Corporation 11
Agenda
The Problem
Getting Organized
Industry Data
Personnel
Process and Methods
Tools
Going Operational
Adapting to Market Conditions
Business Impact and Results
Lessons Learned Summary
-
© 2011 IBM Corporation 12
Getting Organized
9 years ago, a proposal was sent to IBM management to fund an internal application
development benchmarking program to look at the delivery performance (Productivity,
Quality, Cost Estimating Ratio and Schedule Estimating Ratio) of IBM programmers who
support operational systems (for example, Order Entry, Billing, and Financial Systems).
Funding was used for
– Staffing
– Acquisition of industry data
– Acquisition of a statistical package/tool
– Tool training
– Benchmarking Process development and documentation
– Benchmarking Process and Tool integration
-
© 2011 IBM Corporation 13
Data Requirements for Benchmarking
Multi-dimensional view
Worldwide
Cross industry
IFPUG Counting rules used
Large dataset of at least 1000 projects
Ability to aggregate and subset (slice and dice) the data
-
© 2011 IBM Corporation 14
Lessons Learned: Data
Build relationships with your Benchmarking vendors to foster trust and promote mutual understanding of organizational objectives
Acquire data from reputable companies who analyze, normalize, and filter the data that they collect
Avoid vendors who promise they can benchmark ANY metric
Ensure that the benchmarking data is consistent with your data standards (For example, IFPUG Counting Rules, Defect Severity Classification, Warranty Period, etc)
Understand normalization rules used by the benchmarking data source
Use integrated benchmarking data for multi-dimensional analysis to speed up the adoption of the Benchmarking program
-
© 2011 IBM Corporation 15
Lessons Learned: Resources
Establish and maintain a stable team
Staff your team with the correct resources to build your “dream team” in order to establish credibility
Ideal characteristics of a team member:
• Application Development/Maintenance background
• Metrics background
• Basic theoretical statistics background
• Ability to separate theory/text book definitions from real life
• Good written/verbal communication skills
• Ability to think logically
• Ability to work independently with minimal directions
• Attention to deal / fit and finish
-
© 2011 IBM Corporation 16
Lessons Learned: Process
Processes and automation can only get you so far. Team member skills and aptitude will carry you forward
Don’t be afraid to revisit, revise, and revamp processes
Embrace change!
Demonstrate/communicate program value/return on investment
Focus on creating new Program services/offerings (GROWTH) while implementing continuous improvement to existing services/offerings (INNOVATE and IMPROVE)
-
© 2011 IBM Corporation 17
Sample Tool Requirements
Basic statistical calculations
Mean
Median
Standard Deviation
Minimum/Maximum
Quantiles
Data Analysis
Correlation Analysis
Regression Analysis
Non-parametric tests
Data File Manipulation
Concatenate
Subset
Join / Update
Scripting Language
-
© 2011 IBM Corporation 18
Lessons Learned: Tools
Review/evaluate/select tools against your functional requirements
Invest in adequate tools training
Remote, web-based training, while the most cost-effective, may not be appropriate for everyone. Everyone learns differently.
Invest in advanced tool training to take advantage of automation that might be supported in the tools
-
© 2011 IBM Corporation 19
Agenda
The Problem
Getting Organized
Industry Data
Personnel
Process and Methods
Tools
Going Operational
Adapting to Market Conditions
Business Impact and Results
Lessons Learned Summary
-
© 2011 IBM Corporation 20
Although we received approval of our benchmarking deliverables fairly quickly, we spent a lot of time investigating data anomalies. Often, short term trending gave a distorted picture of actual performance.
0
1
2
3
4
5
6
7
8
9
10
1Q09 2Q09 3Q09 4Q09 1Q10 2Q10 3Q10
Pro
du
ctivity
-
© 2011 IBM Corporation 21
Longer term trending data will give you a better view of actual delivery performance
0
1
2
3
4
5
6
7
8
9
10
1Q07
2Q07
3Q07
4Q07
1Q08
2Q08
3Q08
4Q08
1Q09
2Q09
3Q09
4Q09
1Q10
2Q10
3Q10
Pro
du
ctivity
-
© 2011 IBM Corporation 22
Business Analytics: Mining data to formulate information and knowledge about your organization, and using that knowledge to your competitive advantage
0.8
0.85
0.9
0.95
1
1.05
1.1
1.15
1.2
Q1 2
001
Q2 2
001
Q3 2
001
Q4 2
001
Q1 2
002
Q2 2
002
Q3 2
002
Q4 2
002
Q1 2
003
Q2 2
003
Q3 2
003
Q4 2
003
Q1 2
004
Q2 2
004
Q3 2
004
Q4 2
004
Q1 2
005
Q2 2
005
Q3 2
005
Q4 2
005
Q1 2
006
Cost Performance UCL Avg LCL
CMM 3 CMM 5 CMMI-5
1.2
0.8
0.9
1.0
1.1
Cost P
erf
orm
ance Index
Time
-
© 2011 IBM Corporation 23
Lessons Learned: Going Operational
Identify a management advocate/champion
Validate that data elements and normalization are consistent across data sources
Reconcile all metrics calculations performed by the statistical tools package
Statistical Package (Average of Averages)
Average (Organization Standard)
Projects
1
Projects
1
Hourst Developmen
PointsFunction
ii
ii
Projects of #
Projects
1 Hourst DevelopmenPointsFunction
ii
i
-
© 2011 IBM Corporation 24
Agenda
The Problem
Getting Organized
Industry Data
Personnel
Process and Methods
Tools
Going Operational
Adapting to Market Conditions
Business Impact and Results
Lessons Learned Summary
-
© 2011 IBM Corporation 25
Lessons Learned: Adapting to Market Conditions
Do not live on yesterday’s successes. Past performance is not an indication of future performance
Proactively work with teams to assess and mitigate risks
Do not be afraid to retool. Today’s Business Intelligence tools are more powerful and may be able to simplify or eliminate current steps required to produce your deliverables
-
© 2011 IBM Corporation 26
Agenda
The Problem
Getting Organized
Industry Data
Personnel
Process and Methods
Tools
Going Operational
Adapting to Market Conditions
Business Impact and Results
Lessons Learned Summary
-
© 2011 IBM Corporation 27
Business Impact and Results
Organizational Metrics
– Delivery Performance charts embedded into customer proposal
– Worldwide performance goals based on Benchmarking Reports
Business Value
– Business Analytics to drive business decisions in annual budgeting/funding process
Fact-based, not Emotion-based discussions
– Data analysis used to refute claims/perceptions
– Statistical Analysis for fact finding
Drive new business
– Using empirical evidence about IBM performance to win new business
Sustain/enhance existing business relationships
– Using business analytics to find hidden value information to strengthen business
relationships between customers and IBM account teams
-
© 2011 IBM Corporation 28
Business Impact and Results
Reducing financial risks on new/renegotiated contracts
– A trusted advisor to the IBM Legal team
– Identified hundreds of millions of dollars of financial risk to IBM by identifying biased or
unenforceable benchmarking clause language
Business Intelligence Analytics
– Data analysis for IBM Delivery teams to identify delivery excellence and performance
issues in support of
• Contract Benchmarking
• Customer concerns
• New business opportunities
– Competitive pricing analysis has enabled new business opportunities and have allowed
IBM teams to avoid costly and unsubstantiated adjustments
-
© 2011 IBM Corporation 29
Agenda
The Problem
Getting Organized
Industry Data
Personnel
Process and Methods
Tools
Going Operational
Adapting to Market Conditions
Business Impact and Results
Lessons Learned Summary
-
© 2011 IBM Corporation 30
Lessons Learned Summary
Acquire a Management Advocate
Assemble a stable team with the right skills
Fund the development and integration of the Benchmarking processes and tools
Educate the team properly
Innovate, improve, and refresh the program services and capabilities
Demonstrate and communicate the value of the Benchmarking program
-
© 2011 IBM Corporation 31
HA
HA
By Wai F. Hom Corporate Lingo Explained
At least someone was paying attention.
I think it means how fast UPS delivers
your eBay packages.
Are we clear what Delivery Performance
means?