Assessing the business value of Agile Engineering Practices
17
Sunday, June 26, 2022 © Agile Institute 2008-2014 1 …a taste of… Essential Agile Engineering Practices Rob Myers Agile Roots 19 June 2014
-
Upload
agile-institute -
Category
Software
-
view
251 -
download
1
description
Transcript of Assessing the business value of Agile Engineering Practices
April 11, 2023 © Agile Institute 2008-2014 1
…a taste of…Essential Agile
Engineering PracticesRob Myers
Agile Roots19 June 2014
April 11, 2023 © Agile Institute 2008-2014 2
…a taste of…Essential Agile
Engineering Practices@agilecoach
#AgileRoots19 June 2014
April 11, 2023 © Agile Institute 2008-2014 3
April 11, 2023 © Agile Institute 2008-2014 4
Test-DrivenDevelopment
ContinuousIntegration
PairProgrammingCollective Code
Ownership
RelentlessRefactoring
SustainablePace
Creative Slack
CRC Cards
ATDD
Mocks
LegacyCharacterization
Tests
Spikes
Emergent Design
April 11, 2023 © Agile Institute 2008-2014 5
April 11, 2023 © Agile Institute 2008-2014 6
five focusing steps
1. Identify the constraint.
2. Exploit the constraint: Maximize efficiency at
the constraint.
3. Subordinate all else to the constraint: Allow
the constraint to set the pace.
4. Elevate the constraint: Invest (wisely) in “more,
better, faster.”
5. Repeat.
April 11, 2023 © Agile Institute 2008-2014 7
April 11, 2023 © Agile Institute 2008-2014 8
April 11, 2023 © Agile Institute 2008-2014 9
“The results of the case studies indicate
that the pre-release defect density of the
four products decreased between 40%
and 90% relative to similar projects that
did not use the TDD practice.
Subjectively, the teams experienced a
15–35% increase in initial development
time after adopting TDD.”http://research.microsoft.com/en-us/projects/esm/nagappan_tdd.pdf, Nagappan et al, ©
Springer Science + Business Media, LLC 2008
April 11, 2023 © Agile Institute 2008-2014 11
“Laurie Williams of the University of Utah
…has shown that paired programmers are
only 15% slower than two independent
individual programmers, but produce
15% fewer bugs. Since testing and
debugging are often many times more
costly than initial programming, this is an
impressive result.”"Agility counts", The Economist, 20 Sep 2001
April 11, 2023 © Agile Institute 2008-2014 12
beyond academia
• The obvious:• Fewer defects.
• Cross-training.
• The subtle:• Collaboration, courage, & creative problem-
solving.
• Self-control, self-discipline, valuable breaks, fewer interruptions.
• Readable code, less ego-centric code.
• Fewer “heroes” (a.k.a. single points of failure).
April 11, 2023 © Agile Institute 2008-2014 13
“If it’s painful,
do it often.”
-- attributed to Kent Beck, who is not a masochist.
April 11, 2023 © Agile Institute 2008-2014 14
so boring, a computer could do it
• What it provides:• Rapid, automated feedback.
• We know we’re testing/deploying a version from a stable snapshot.
• Often generates valuable metrics.
• What it helps avoid:• Dependency integration defects, merge
conflicts, lingering broken builds.
• A need for branching, & branched releases.
• Code freezes.
a short Continuous Integration recipe
1. A build server.
2. A code repository.
3. A fast suite of automated tests.
4. Build scripts.
5. A Buildmeister.
6. A CI tool (optional, but adds zest)
April 11, 2023 © Agile Institute 2008-2014 15
April 11, 2023 © Agile Institute 2008-2014 16
Test-DrivenDevelopment
ContinuousIntegration
PairProgrammingCollective Code
Ownership
RelentlessRefactoring
SustainablePace
Creative Slack
CRC Cards
ATDD
Mocks
LegacyCharacterization
Tests
Spikes
Emergent Design
April 11, 2023 © Agile Institute 2008-2014 17
http://PowersOfTwo.agileInstitute.com/
@agilecoach
