Agile ROI: The Business Case for Agility. John Rudd, President and CFO



Similar documents
Agile Portfolio Management

Keeping a Healthy Product Backlog

Organizational agility the ability to react quickly to changing market circumstances is. Agility and Cost. Organizational Design and Key Workflows

Agile Metrics. It s Not All That Complicated

WE ARE FOCUSED ON HELPING OUR CLIENTS WORK SMARTER AND MORE EFFICIENTLY SO THAT TOGETHER, WE CAN EMPOWER PEOPLE TO DELIVER GREAT RESULTS.

Scaling Agile with the Lessons of Lean Product Development Flow Copyright 2012 Net Objectives, Inc. All Rights Reserved

Agile ETRM from Allegro

How Agile methods resolve chaos and unpredictability in software projects

Lean Metrics How to measure and improve the flow of work. Chris Hefley, CEO of LeanKit. November 5 th, 2014

Measuring ROI of Agile Transformation

John Chaimanis, Co-Founder and Managing Director, Kendall Sustainable Infrastructure (KSI)

The Manager s Guide to Avoiding 7 Project Portfolio Pitfalls

Introduction to Agile and Scrum

HP Strategic IT Advisory Services

Investor Presentation Q1 2014

Agile and lean methods for managing application development process

Agile Project Management

Agile Notetaker & Scrum Reference. Designed by Axosoft, the creators of OnTime the #1 selling scrum software.

Consultants: Stop Giving Away This High-Value Service to Clients for Free!

Brent Atkins, Cris Hadjez An Agile BI Approach: Mead Johnson Uses Better Data to Push Boundaries and Increase Customer Value Session # 3544

Ten Critical Steps. for Successful Project Portfolio Management. RG Perspective

Measuring for Results: Metrics and Myths

Deep Agile Blending Scrum and Extreme Programming. Jeff Sutherland Ron Jeffries

Sometimes: 16 % Often: 13 % Always: 7 %

PMBOK? You Can Have Both! June 10, Presented by:

shutterstock.com Interim Management and Strategic Transactions for International Life Science Companies TCG: experienced, connected, proven success

CFO s Perspective on Fast Data. Ralph Balestriere, EVP & CFO Red Wing Shoe Company

Gaining Competitive Advantage through Reducing Project Lead Times Duncan Patrick, CMS Montera Inc. Jack Warchalowski, CMS Montera Inc.

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into

Project, Portfolio Management (PPM) for the Enterprise Whose System is it Anyway?

White paper: Scrum-ban for Project Management

Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc.

4 Keys to Driving Results from Project Governance

Agile In a Nutshell. Note - all images removed to fit 2MB limit Actual presentation has much more content. Jonathan Rasmusson

Establishing and Maintaining Top to Bottom Transparency Using the Meta-Scrum

Executive Guide to SAFe 24 July An Executive s Guide to the Scaled Agile Framework.

PROFITABLE PURCHASING NEGOTIATION

BETTER RELATIONSHIP SELLING

Increase Revenues with Channel Sales Management

Tech-Clarity Insight: Top 5 Misconceptions about Innovation Management Software

A Capability Maturity Model (CMM)

Implementing Portfolio Management: Integrating Process, People and Tools

Agile Governance. Charlie Rudd SollutionsIQ. Copyright 2011 SolutionsIQ. All rights reserved.

The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. July Developed and sustained by Ken Schwaber and Jeff Sutherland

Choosing KPI s Relevant to your Business Objectives

Five barriers to innovation: Key questions and answers

Merger & Acquisition, Integration and Divestiture

Scrum, User Stories, and More! CSCI 5828: Foundations of Software Engineering Lecture 22 11/06/2014

If your company had an extra $41 million, what would you do with it? For every $1 billion in revenue,

INNOTAS EBOOK The Transformational CIO

Information Technology Governance: Key Success Factors

Getting Started with Agile Project Management Methods for Elearning

The key to success: Enterprise social collaboration fuels innovative sales & operations planning

BIG DATA THE NEW OPPORTUNITY

Process-Centric Back Office Transformation

PPM and Agile: Realizing the Best of Both Worlds

Scrum includes a social agreement to be empirical as a Team. What do you think an empirical agreement is?

Agile Contracts. NK Shrivastava, PMP, RMP, ACP, CSM, SPC CEO/Consultant - RefineM. Agenda

Q Earnings Conference Call. July 30, 2015

Best Practices in Release and Deployment Management

Voice solutions for e-business. Speech recognition delivers ROI to contact centers. Here s how you can prove it

IT Governance. What is it and how to audit it. 21 April 2009

Why Agile Works: Economics, Psychology, and #PrDC16

Redefining Agile to Realize Continuous Business Value

Introduction to Integrated Marketing: Lead Scoring

6 Oct Agile: Creating a Culture of Quality, Value and Feedback. Agile. Creating a Culture of Quality, Value and Feedback.

IT Portfolio Management BADM 559/458 Enterprise IT Governance. Sanju Varghese

Prosci Canada Change Management Certification Program

A MATTER MANAGEMENT/e-BILLING BUYING GUIDE

Agile Scrum Workshop

CREATIVE SOLUTIONS FOR REVERSE LOGISTICS NON-PROFIT ORGANIZATIONS AND RETURNS MANAGEMENT UTILIZING

Talent & Organization. Change Management. Driving successful change and creating a more agile organization

Scrum. SE Presentation. Anurag Dodeja Spring 2010

Enterprise IT Portfolio Governance and Management Model

Improving Project Governance Using Agile and Metrics. Kevin Aguanno PMP, IPMA-B, MAPM, Cert.APM

Transcription:

Agile ROI: The Business Case for Agility John Rudd, President and CFO

John Rudd President and CFO of SolutionsIQ Formerly a partner in a boutique financial consulting & investment banking firm Led the firm s financial practice specializing in advisory services, mergers & acquisitions, and interim management. Filled multiple interim executive roles including CEO, president, CFO, and chief restructuring officer. Worked as CFO of a West Coast oil company and a commodity lender for ING. Received his B.S. in Economics from the University of Minnesota and his MBA from the University of Southern California.

A financial guy s intro to Agile Unsuccessful IT projects First impressions of Agile Positive results with Agile Is there a better way?

As financial professionals we seek to improve project and portfolio return by focusing on fundamental elements WIP + Risk + Project Investment = Project & Portfolio Return

As financial professionals, we have taken a rational response to under performing IT projects Fixed Scope Fixed Schedule Fixed Budget Monitoring

After years of perfecting process 30-40% of systems projects fail prior to completion 1 Half of all systems projects overrun their budgets and schedules by 200% or more 1 64% of features are rarely or never used 2 1 B.P. Lientz and K.P. Rea, Breakthrough Technology Project Management 2 Standish Group Study Report, 2002

So, why isn t our traditional approach working? Reduced performance Locked in waste Increased time to market Decreased likelihood of meeting the business or market needs Abdicated real project control And, minimized options

In fact, through the use of traditional project control methods we have WIP + Risk + Project Investment = Project & Portfolio Return

Why Agile? Squeeze cash out of work-in-process Drive risk out of the project Increase project and portfolio return

What is work-in-process? Work-in-process or in-process inventory consists of the unfinished products in a production process.

Traditional methods lockup capital

Large WIP - Ties up cash Allocation upfront Harder to get acceptable ROI on dollars invested Hampers organizational liquidity

Typical IT project 100 50 0-50 -100-150 Quarterly Cash Flow Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8 Q9 Q10 Q11 Q12 Q13 Q14 Q15 Q16 200 Cumulative Cash Flow 100 0-100 Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8 Q9 Q10 Q11 Q12 Q13 Q14 Q15 Q16-200 -300-400 -500-600 -700

Large WIP - Creates waste Early stages require unproven assumptions and unneeded features Large cycle times leads to process waste Buffering

Much of the total spend is on waste 64% of features are rarely or never used Wasted Features Valued Features and Planning Value Waste Excess Planning & & Process Buffer 20% of features provide 80% of the value Standish Report, 2002

How feature chunks resolves this

Outcomes: Squeezing cash out of process Free up cash Invest capital elsewhere Reduce waste Lower Costs

Why Agile? Squeeze cash out of work-in-process Drive risk out of the project Increase project and portfolio return

Cost & Schedule Risks Examples: Lack of information Inaccurate estimates and schedules Unplanned change Project off target leading to total Loss/write-off

Benefit Realization Risks Examples: Market changes Changes in overall economy Features used Today Competitive response

Problems with Traditional Mitigation Mitigation Fixed Scope Fixed Schedule Fixed Budget Monitoring Problems Upfront comprehensive requirements Cost of change is high Limited flexibility Require hard dates for phases Buffering for unknowns High capital allocation Budget allocation up front Locks in waste Reports % not value

Traditional mitigation Big and Long Less accurate Less flexible Wasteful Increased probability of failure

Loss of Management Control What happened to monitoring? Information is suspect Measuring progress not value Mid-stream changes difficult When things go wrong Spend more, or Kill the project

Evaluate project more frequently Every 2-4 weeks Meaningful evaluation Measure delivered value Examine working product Prioritize actively Clean breaks Make the right decisions

Inject Market and Customer Feedback

This allows us to manage investment Fail fast or stop early Succeed early and double down Invest money from one and move to another

Expand Options Maintain scope Expand/Accelerate scope Reduce scope Reprioritize Shut project down

Feature chunks - Measure return Transparency to Manage on value Market and customer feedback Management Influence

Outcomes: Drive risk out of the project Enable rapid course correction Fail fast and stop early Succeed early and double down Real management control created options Management influence

Why Agile? Squeeze cash out of work-in-process Drive risk out of the project Increase project and portfolio return

We have made progress toward our fundamental goals WIP + Risk + Project Investment = Project and Portfolio Return

Portfolio Implications Characteristics Results Problems Larger projects Longer projects Serial approach Fewer projects Span annual budget cycles Value only at end of project Less diversification Reduced portfolio options Few real options or ability to change

The traditional portfolio approach Fewer Investments Limited control within period Can t offset costs with returns Can t measure portfolio return

An Agile portfolio approach Feature Chunks Quicker to Market Reallocate investment Increase/Delay/Stop

Maximize portfolio return through Increased diversification Ability to monitor and manage performance within the budget cycle Ability to redirect funds from losers to winners Optimize portfolio within the budget cycle

Reallocate funds to strong performers let s change the game

Actively Manage Portfolio Reevaluate priorities constantly Reshuffle portfolio continuously Start/Stop projects Recognize increments of value

Outcomes: Increase project and portfolio return Increase portfolio diversification which helps reduce risk Continually redirect from losers to winners Reclaim control of the portfolio management

Why Agile? Squeeze cash out of work-in-process Drive risk out of the project Increase project and portfolio return

Traditional vs. Agile Approach Big and Long Less Accurate Less Flexible Increases risk of failure Less management control Wasteful Small and short More predictable Iterate every 2-4 weeks Increases probability of success Active management control and influence Eliminate overhead and unnecessary features

Agile Benefits Free up capital Reduce unnecessary cost Recognize return earlier Zero in on current market and customer needs Increase project and portfolio return

How is this done? Break big projects into smaller chunks Evaluate projects more frequently Inject market and customer feedback Actively reprioritize project portfolio Reallocate funds to strong performers

Not unchartered territory Agile practices are not new since mid 90 s Collection of proven practices proven Scrum Extreme Programming (XP) No longer a grassroots movement: Wider adoption among Fortune 1000 companies 75-80% of IT organizations have some Agile practices* 15-25% have established a repeatable Agile process* Current State of Agile Methods Adoption, Gartner, December 2008

Why Now? Reduce risk inherent in large IT investments Improve organizational liquidity Get more from shrinking capital budgets Maintain flexibility to quickly take advantage of emerging market opportunities Provide a game changing impact to your organization during troubling times

Founded: 1979 Employees: 250+ Headquarters: Redmond, WA Full range of services from training and consulting to software development and talent acquisition Leading provider of Scrum Certification Training

Agile Services at Every Stage

Enterprise Agile Adoption Program

Question & Answer

Upcoming SolutionsIQ Webinars from VersionOne Apr 29 Building your Business Case for Agile Methods for calculating the value of implementing Agile within your organization May 13 Soon Soon Tracking Agile Progress: Is it working? Agile Portfolio Metrics: A Dashboard for Executives Strategies for Maximizing Agile Portfolio Value

Thank You Following this presentation, participants will receive an email with links to a recording and copies of today s slides For more on SolutionsIQ: www.solutionsiq.com info@solutionsiq.com +1(800)235-4091