Professional Documents
Culture Documents
Agile Leadership Requires A Different Kind of Business Case
Agile Leadership Requires A Different Kind of Business Case
Agile Leadership
Requires A Different
Kind Of Business
Case
September 4, 2020
By Margo Visitacion with Chris Gardner, Jeffrey Hammond, Andrew Dobak, Kara Hartig
Summary
Business leaders want the speed of Agile to meet pressing requirements for new
software. But they are reluctant to transition from the false comfort of traditional, written
business cases to iterative funding and value measurement. To scale Agile to the
enterprise, business cases must evolve from making investment bets to consistently
measuring feedback and gauging future investments. This report shows how application
development and delivery (AD&D) pros can work with finance and other executives to
build effective methods for assessing and prioritizing software investments. This is an
update to a previously published report.
• Leaders prioritize improvements and new products but lack a way to measure
them. Companies' current technology and products aren't adequate for supporting
digital strategies. Forty-three percent of global purchase influencers recognize that
they need to improve current IT systems to support digital channels; 38% state they
need to improve their IT organization's ability to rapidly deliver digital solutions; 27%
say that creating more smart connected products or services is a priority; and while
investments are the top priority, concrete measures for demonstrating value and
success follow at 25%.
• Leaders face planning and technology issues as they try to transform. In meeting
those priorities, business and software leaders face significant challenges: 33% of
global software decision makers cite budget and 30% cite security as the leading
challenges in forming software strategies. And 24% state that the inflexibility of
existing applications blocks them from orchestrating their strategy.
be difficult. And while setting budgets and timelines using a model of estimated
activities and output may be familiar, it doesn't provide insight into the impact that
managing change may have on a final outcome. It also doesn't cover all of the
benefits that are important to digital transformation — like improved customer
engagement or digital product adoption.
• Build a culture of empowerment from the top down — and the bottom up. Making
the leap to Agile at scale requires a combination of direction from established
practices and adaptation. While constructs like the scaled Agile framework (SAFe)
may help, AD&D teams must adapt them to fit their corporate culture. At the same
time, they need to demonstrate the value of such initiatives to maintain executive buy-
in. Samsung, for example, embedded product designers on its software teams who
introduced persona-based development and testing, which the developers adopted.
In parallel, it maintained executive support by communicating continuous
improvements in strategy, process, and measurement.
"Agile makes people nervous, but we know if we don't do this Agile journey, we'll die
out. SAFe gives us a framework that allows us to talk to the business. Features on the
backlog have to contain compliance changes. The train concept allows the business
to see how features are bundled, and our design team can make these changes
become intuitive customer-oriented features." (Design manager at a North American
insurance company)
• Create networks that break down traditional command-and-control models. It's rare
to see huge firms that have successfully scaled Agile across the enterprise, shifting
from giving teams top-down guidance to empowering them to make delivery
decisions. But companies like Qantas Airways are scaling by adapting techniques
from the Spotify model to manage dependencies, create skilled communities, and
• Use fast feedback in Agile delivery to provide iterative validation in business cases.
Organizations that don't prioritize delivery best practices in process and culture are
far less successful than peers that do. Innovator organizations waste just 8.5% of their
project investments, compared with the 16.3% wasted by those that lag behind them.
Clear methods for communicating performance, such as OKRs, put everyone on the
same page when identifying measurable outcomes. For instance, a continuous
cadence of demos and releases of working software helped give Samsung's
transformation the buy-in it needed.
only applicable to new development efforts. Insight from data about how legacy
applications are performing is essential for helping teams better understand what to
modernize — and where moving apps to the cloud and employing Agile techniques
will have the most benefit.
"We see a lot of companies struggling to get the facts to decide on rebuilding versus
[scrapping and building new]. These companies need to know whether to keep
investing or recognize that they're throwing good money away and are missing
opportunities to deliver newer flexible solutions faster." (Lev Lesokhin, executive VP,
software intelligence, CAST)
RECOMMENDATIONS
Build Agile Business Cases Through Communication And Validation
Traditional ROI-focused business cases don't account for the hard and soft benefits that
Agile at scale offers. To demonstrate the benefits of organizational, cultural, and
process changes, AD&D pros building a business case for the Agile enterprise must:
outcome to work toward. Everyone knows their part in making the transformation
work and what they're accountable for.
• Establish a standard cadence for business case feedback. Traditional best practices
for project funding start measuring value realized only after deployment. But for some
projects, that could take years. Identifying measurable outcomes for each release
iteration helps teams build trust with their business partners.
• Set priorities based on CX and value chains. Using CX as the basis for prioritization
sets the stage for alignment. Using value chains provides end-to-end insight into the
total cost of investment and helps reduce waste in the prioritization process.
SUPPLEMENTAL MATERIAL
Survey Methodology
The Forrester Analytics Business Technographics® Priorities And Journey Survey,
2020, was fielded between December 2019 and January 2020. This online survey
included 19,739 respondents in Australia, Canada, China, France, Germany, India, the
UK, and the US from companies with two or more employees.
The Forrester Analytics Global Business Technographics Software Survey, 2019, was
fielded between August and October 2019. This online survey included 3,598
respondents in Australia, Canada, China, France, Germany, India, the UK, and the US
from companies with two or more employees.
Forrester Analytics' Business Technographics ensures that the final survey population
contains only those with significant involvement in the planning, funding, and
purchasing of business and technology products and services. Dynata fielded these
surveys on behalf of Forrester. Survey respondent incentives include points
redeemable for gift certificates.
Please note that the brand questions included in these surveys should not be used to
measure market share. The purpose of Forrester Analytics' Business Technographics
brand questions is to show usage of a brand by a specific target audience at one point
in time.
Companies Interviewed For This Report
We would like to thank the individuals from the following companies who generously
gave their time during the research for this report.
• CAST
• Hyland Software
• Scaled Agile
• WorkBoard
Endnotes
1. Businesses must be able to calculate the ROI of digital investments. But achieving
precision at the group level is nearly impossible. Developing a framework for ROI
calculations based on usage scenarios can help leaders effectively construct
measurable business cases. See the Forrester report "Build The Business Case For
Your Digital Investments."
2. Shifts to Agile development practices are forcing organizations to adopt more flexible
budgeting and funding practices. See the Forrester report "Digital Business Requires
Agile Financial Planning."
3. Source: Ben Linders, "Samsung's Agile & Lean UX Journey," InfoQ, April 11, 2019
(https://www.infoq.com/news/2019/04/samsung-agile-lean-ux).
5. Experimentation platforms allow AD&D teams to stop guessing what their clients want
and get direct feedback that delivers better CX. See the Forrester report "AD&D Pros:
Stop Guessing And Start Experimenting."
6. Agile delivery practices are now mainstream, but real business differentiation is
driving companies to make fundamental organizational and process shifts to embrace
Agile techniques at the enterprise level. See the Forrester report "The Agile
Enterprise Emphasizes Practice Over Process."
7. Agile frameworks like the Spotify model can help mainstream companies manage
interdependencies and facilitate collaboration at speed. See the Forrester report
"Scaling Agile: What The Spotify Approach Can Do For You."
9. See the Forrester report "Build The Business Case For Your Digital Investments."
10. The Project Management Institute (PMI) defines innovators as companies that place a
high priority on digital skills and knowledge and couple that with a commitment to a
strong project management culture. Source: "PMI's Pulse Of The Profession: Research
Highlights by Region and Industry," PMI, 2020 (https://www.pmi.org/-
/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pulse_all-
comparison-reports_final.pdf).
FOLLOW FORRESTER
Contact Us
Contact Forrester at www.forrester.com/contactus. For information on hard-copy or electronic
reprints, please contact your Account Team or reprints@forrester.com. We offer quantity
discounts and special pricing for academic and nonprofit institutions.
Forrester Research, Inc., 60 Acorn Park Drive, Cambridge, MA 02140 USA
Tel: +1 617-613-6000 | Fax: +1 617-613-5000 | forrester.com