agile 2013 presentation, tom grant
TRANSCRIPT
Agile In The Real World: Gone Mainstream, Creating Bigger Waves, Making Course Corrections
Tom Grant, Ph.D.
Senior Analyst, Forrester Research
3© 2013 Forrester Research, Inc. Reproduction Prohibited
Agile has been a revolutionary force that definitely improves software development and delivery…
…But we may be leaving a lot of people behind.
6© 2013 Forrester Research, Inc. Reproduction Prohibited
TOP 5 reported benefits: Improved quality (56%)
More opportunities for mid-course corrections (56%)
Overall improved customer and business satisfaction (38%)
Better business-IT alignment (37%)
Improved time to market (32%)
A lot more than velocity
Less than 25%
Between 25% and 49%
Between 50% and 74%
Between 75% and 99%
100%
40%
17%
13%
12%
19%
“How many development teams in your organization have implemented Agile practices?”
(Select one)
Base: 205 IT professionals from organizations that are implementing or have implemented Agile(percentages do not total 100 because of rounding)
Source: November 2011 Global Agile Software Application Development Online Survey
Agile adoption isn’t superficial
We’ll see this pattern again.
8© 2013 Forrester Research, Inc. Reproduction Prohibited
Powerful connection to other disruptive forces
MOBILE CLOUD
OPENSOURCE
DEVOPS
DESIGN UX/CX
9© 2012 Forrester Research, Inc. Reproduction Prohibited
Agile has adopted to real-world circumstances
WATER SCRUM FALL
Resourcing
Budgeting
Justification
Definition
ComplianceGovernance
User resistance to change
Re-work
SPRINT!SPRINT!SPRINT!SPRINT!
Planning
Requirements
Additional testingRelease
StreamlineStreamline
© 2013 Forrester Research, Inc. Reproduction Prohibited
Agile is blurring boundaries between activities
© 2013 Forrester Research, Inc. Reproduction Prohibited
*Base: 3,616 business decision-makers world-wide.Source: Forrsights Business Decision-Makers Survey Q4 2012
Business’ top two priorities for IT:
1. Improve the use of data and analytics to improve business decisions and outcomes
2. Improve IT project delivery performance*
Only 30% of business users think that IT is accelerating their success*
© 2013 Forrester Research, Inc. Reproduction Prohibited
Mobile
Open source software (used as part of software developed
and/or deployed)
Pressure to deliver faster
Geographically distributed teams
Agile
0% 20% 40% 60% 80% 100%
It has made my work harder.
It has made my work easier.
It has had no ef-fect on my work.
How have the following aspects of software development and delivery affected your work?
Base: 128 software development professionals worldwide.
Source: Forrester ALM survey, Q1 2013
15© 2013 Forrester Research, Inc. Reproduction Prohibited
Uncontrollable demand is destructive
Commitments
Technical debt
Resourcing
Heroism
Learning
Planning
16© 2013 Forrester Research, Inc. Reproduction Prohibited
Complex, prescriptive SDLCs are derailing under stress
18© 2013 Forrester Research, Inc. Reproduction Prohibited
How do weaddress some ofthe immediatechallenges?
? ??
20© 2013 Forrester Research, Inc. Reproduction Prohibited
Only 24% of organizations deliver new software weeklyor faster
For the business, this is unacceptable
© 2013 Forrester Research, Inc. Reproduction Prohibited
TESTINGRealistic
AutomatedThorough
DEPLOYMENTConsistent
ManageableRecoverable
DELIVERYComplete
ConfiguredImmediate
RISKUnderstood
SharedAddressed
© 2013 Forrester Research, Inc. Reproduction Prohibited
SPRINTSPRINTSPRINTSPRINT
ACTUAL
PRELIMINARY
26
Prioritization UX
Quality
Quality
UX
ACTUAL
PRELIMINARY
Architecture
Architecture
Prioritization
Design
DesignTE
CH
NIC
AL
BU
SIN
ES
S
Value
Value
27© 2013 Forrester Research, Inc. Reproduction Prohibited
Developers have better relationships with Operations than they do with business analysts and business unit
managers.
Base: 205 IT professionals from organizations that are implementing or have implemented Agile(percentages do not total 100 because of rounding)
Source: November 2011 Global Agile Software Application Development Online Survey
28© 2013 Forrester Research, Inc. Reproduction Prohibited
The #1 and #3 reasons why software doesn’t ship on time:
“New and changing requirements”
“Unclear requirements.”
“Operational bottlenecks” are #6.
Base: 128 software development professionals.
Source: Forrester ALM survey, Q1 2013
Never
Infrequently
After significant landmarks, such as a major release or the end of a
project
At a regular interval of between 6 to 12 months
At regular intervals less than 6 months apart
Continuously, using data gathered about system usage or other
mechanisms
5%
15%
25%
8%
20%
26%
Base: 205 IT professionals from organizations that are implementing or have implemented Agile(percentages do not total 100 because of rounding)
Source: November 2011 Global Agile Software Application Development Online Survey
Here’s that curve again
“How often do you measure user/customer satisfaction with the software as delivered?”
(Select one)
31© 2013 Forrester Research, Inc. Reproduction Prohibited
Agile adoption means crossing a major chasm
© 2013 Forrester Research, Inc. Reproduction Prohibited
The organization must be ready for COMMITMENT
Experimentation
Noble failure
Measurement
Adjustment
Transparency
Self-reliance
Collaboration
33© 2013 Forrester Research, Inc. Reproduction Prohibited
Sample commitment: CONTINUOUS INTEGRATION
Check into a single branch
Check in multiple times per day
Test in a production environment
Build the entire package, not just the binaries
Unit test rigorously
Build after each commit
Only test on a clean server
Do multiple integrations per day
Be transparent to the team
© 2013 Forrester Research, Inc. Reproduction Prohibited
If you’re committed to transformation…
34
AgileCI
TDD
CD DevOps
Kanban
Etc.
CynefinEtc.Visualization
35© 2013 Forrester Research, Inc. Reproduction Prohibited
We are not planning significant changes to our methodologies or tools within the next 5 years.
We would like to make some significant changes to our methodologies or tools, but we have no current plans.
We are planning on making significant changes to our methodologies or tools within the next year.
We are in the process of making significant changes to our methodologies or tools.
0% 10% 20% 30% 40%
Which of the following statements best describes your software development and delivery organization?
Not everyone has that
commitment
Base: 128 software development professionals worldwide.
Source: Forrester ALM survey, Q1 2013
36© 2013 Forrester Research, Inc. Reproduction Prohibited
Why isn’t everyone committed?
Lack of leadership
Horizontally fragmentation
Problems of scale
Technical debt
Compliance
Poor organizational health
Under-investment
Out-moded organization
Myth of central control
Risk-averse culture
…And excessive demand
37© 2013 Forrester Research, Inc. Reproduction Prohibited
We are headed towards a deep division between two types of software
development organizations
38© 2013 Forrester Research, Inc. Reproduction Prohibited
“The curve” is really a chasm
Not committedto transformation
Committedto transformation
42© 2013 Forrester Research, Inc. Reproduction Prohibited
Accelerate the trip down the cone of
uncertainty
43© 2013 Forrester Research, Inc. Reproduction Prohibited
Hone strategies for adoption beyond the
single team
44© 2013 Forrester Research, Inc. Reproduction Prohibited
Make flow the connection between
Agile and ALM
COLLABORATION
OUTCOMES
ACCELERATORS
Methods
High valuesoftware
Tools
The business
Delivered more frequently
Delivered more reliably
Platforms
Organization
Teams
Trust
© 2013 Forrester Research, Inc. Reproduction Prohibited 47
Disruptors will compel change anyway
45% of software professionals have no plans
for changing methodologies or tools
41% are new at mobile applications, and 31% are planning on starting soon
Base: 128 software development professionals worldwide.
Source: Forrester ALM survey, Q1 2013
© 2013 Forrester Research, Inc. Reproduction Prohibited 48
MOBILEDEVELOPERS PMO
› New requirements media
› New platforms› New testing
capabilities› New
deployment options
› New expectations
› Some of the old ways made sense!
› OK, not all of them…
› So which can we change or drop?
© 2013 Forrester Research, Inc. Reproduction Prohibited
Change roles and responsibilities
Beyond the product owner
Beyond the Scrum Master
© 2013 Forrester Research, Inc. Reproduction Prohibited51
BAsDevelopers
Testers
Productowners
Scrummasters
UXdesigners
DE
FIN
ING
DE
LIV
ER
ING
Enabling
Assessing
Portfoliomanagers
Projectmanagers
Technicalarchitects
BI professionals
Operationsstaff
Executive management
Helpdeskstaff
52© 2013 Forrester Research, Inc. Reproduction Prohibited
Testers must be masters of Test Fu
TESTTECHNICIANS
Test automation
Test management
Exploratory testing
Quality assessment
Test re-use
Realistic cases
53© 2013 Forrester Research, Inc. Reproduction Prohibited
BAs must be envoys
ORDERTAKERS
Accelerate design
Define roadmaps
Negotiate
Communicatenecessity
Assess value
Represent interests
Actionable
Contextual
Descriptive
What is the
customer
asking for?
How should we
meet the
customer’s
request?
What is the customer really asking for?
55© 2013 Forrester Research, Inc. Reproduction Prohibited
Executives must be sponsors of innovation
MONDAYMORNING
QBs
Goal-setting
Room to experiment
Assessment
Top cover
Alignment
Investment
© 2013 Forrester Research, Inc. Reproduction Prohibited56
After adopting Agile, who has influence over product decisions?
Executives were the only group whose influence decreased.
56
57© 2013 Forrester Research, Inc. Reproduction Prohibited
Customers must be partners in innovation
ORDERGIVERS
Clarity
Priority
Context
Availability
Roadmap
58© 2013 Forrester Research, Inc. Reproduction Prohibited
The customer must learn something about how
development organizations work.
58