The Success Healthcheck for IT Projects: An Insider's Guide to Managing IT Investment and Business Change
Introduction: In The Beginning There Was…a project that succeeded.
Founded on Robust Research.
PART 1: PRODUCTIVITY.
Chapter 1: IT Projects Are Investments.
The Back Story on Productivity.
The Productivity Challenge and IT.
CEOs Say They Cannot Continue to Introduce Change in the Same Way.
What Is Success?
Project Failure Is the Untapped Source of Productivity Growth.
Why This Failure Rate Continues to Exist.
Improving Productivity Is a Process.
Survival of the Fittest.
Chapter 2: Measure Success.
Measuring the Cost of Project Failure.
The Functional Yield Measures of IT Project Productivity.
Simple Return on Investment.
The Functional Yield.
The Cost of a Little Under to the Business.
Improving Project Productivity.
Chapter 3: Take Action to Lift Success.
Publicly Acknowledge That Success Is Not Guaranteed.
Own Up to the NPP Ratio.
Yield and NPP Ratios.
Write-offs and Functional Shortfalls.
Value the Reduced Risk of Failure (to Achieve Business Results).
Results Risk ManagementTM.
Contingency Planning for Results Risks.
Accountability for Results Risk Management.
The Benefits of Setting Up for Success.
Address Risks to Success.
Repeated Project Failure Is a Governance Issue.
CIO Moment: Portfolio Governance and the 7 Keys to Success.
Predictable Accountable Results (PAR).
Chapter 4: Benchmark Productivity from IT Projects: Evaluating the Cost of Failure.
Elements: Collecting Your Own Data.
Funds Budgeted and Spent.
The Functional Yield in Reality—A Window into 3 IT Portfolios.
Chapter 5: Diagnosing Productivity Health.
The Results Diagnostics.
Project Health Factors.
Project Health Check.
Use of Good Practices.
Recognition of Business Experience with Projects.
Tangible Project ROI, or Hard Productivity Gains.
Project Health Diagnosis.
Get Your Data Together.
Project Health Diagnosis Summary.
Framing the Diagnostic for Decision and Action.
Acting to Lift PAR.
Lift Project Performance by Addressing the Failure Rate.
Takeaway from Productivity.
PART 2: PROBABILITY.
Chapter 6: Talent Scouting—Spotting Success Early.
100 Percent of Projects Intend to Succeed.
Past Performance Predicts Future Performance.
All Projects Have Risks.
When to Assess Probability of Success.
Results and Success Take More than Delivery.
The Foundations of the 8-Fold Path to Project Success.
The Complications of Countries.
Dangers in Overlooking the Obvious.
How to Set a Project Up for Success.
Why Start with Productivity.
Chapter 7: The 8-Fold Path to Project Success.
What Does this Look Like?
An Archetypal Project.
What are Your Real Results?
Trust and Verify.
Chapter 8: Business Results Are a Process.
Results Delivery Process.
Maturity and Results Deliver Processes.
PART 3: PROJECT.
Chapter 9: Fold 1, Intent Is Clear.
Results Are… .
Return on Investment Implies Results.
Results Are Clearly Specified.
Results from Competitive Capacity or License to Operate Requirements.
Intentions of the Project Process.
Intended Time Frame for Results.
Intended Quality of Result: Quick Fixes or Strategic Change.
Intended Impact to Stakeholders.
Intent’s Impact on the Broader Picture.
Chapter 10: Fold 2, Business Case Is Robust.
Results of Investment: What’s the Bottom Line?
What Is the Real Investment?
Quality of Business Case.
Evaluating the Business Case Financials.
Now, a Secret… .
Working Around This Secret.
Project Results Sensitivity.
Chapter 11: Fold 3, Results Delivery Process Is Reliable.
How Reliable is the Results Delivery Process?
Simplifications Undermine the Results Delivery Process.
KISS: 6 Keep It Simple Symptoms.
Chapter 12: Fold 4, Motivation Is Energized.
Risk: Accept or Reject—People Are Part of the Business Results Equation.
…the Likely Response.
Resistance—Psychology Not Taught at School.
Resistance Can Be Sensible.
Motivation Is Multifaceted.
Where Do Interest, Engagement, and Energy Go?
Conflicting Interests: Rational Dysfunctions.
People Choose to Act or to Ignore the Project.
Chapter 13: Part 3 Takeaway.
PART 4: PRESENCE.
Chapter 14: Background to Part 4.
Process: Success in the Business Context.
Business Results from IT Projects Require Continued Presence.
Present to Future Implementation Issues.
Collateral Damage Costs.
An Archetypical Business System.
Diagnosing the Business Context for Success.
Chapter 15: Fold 5, Project Aligns to Current Strategic Position.
Risks to Business Results from the Strategic Context.
Strategic Context Affects Results.
Leadership and Vision Affect Results.
Culture Affects Results.
Chapter 16: Fold 6, Operational Context Supports Project Intent.
Operational Context Reinforce.
IT Practices and Projects.
The People Thing and Projects.
Financial Policies and Project Results.
Chapter 17: Fold 7, Flow Favors Project Intent.
Previous Experiences with Change in the Business.
Quality of Local Management.
Reputation of the Project.
Chapter 18: Fold 8, Balancing Dynamics to Aid Project Intent.
Rain, Erosion, Landslides, and Growth.
Regrowth Rates and Burnout.
Bulldozers, Slash and Burn, and Other Ways to Destroy.
Short-Termism and Expediency.
Moving with Time.
Chapter 19: Lifting Performance from Failure to Success.
Diagnostic: What are the Risks to Business Results?
Are Business Results Probable?
Project Risks to Results Assessment.
Presence of Risks from Business Context Assessment.
Expected Results from the Project.
Identifying the Risks to Address.
CIO Moment: Credibility Check.
Take Action to Improve Business Results from IT Projects.
PART 5: PERFORMANCE.
Chapter 20: Where To? Success Is a Journey, Not a Destination.
Assess Risks, Take Action.
Performance Reflects Proficiency.
Experience Is More than Headlines.
Where Are You Now?
Where Do You Want to Be?
Begin with Accountability for Results.
Refine Predictability at the Project Level.
Track Risk and Results.
The Leadership Challenge.
It Is Personal.
Begin with the End in Mind.
Success and Courage.
Appendix A: Calculating the Functional Yield.
Appendix B: CIO Moment—Results Track Record.
Appendix C: The Basic Health Check: Warning Signs.
Take Action and Identify the Risks to Address.
Appendix D: The Cost of Lightweight Business Cases.
Appendix E: Requirements are not Always Words.