OOP 2015 Technical Excellence - Key

Technical Excellence
James W Grenning
wingman-sw.com
@jwgrenning
1
Copyright 2008-2014 James W. Grenning
Technical Excellence www.wingman-sw.com 2
All Rights Reserved @jwgrenning. OOP, Munich 2015 Oop@wingman-sw.com
I Tried to Avoid
Computers

People will pay me
to do this?!!

May 7 11:21:17: --- last message repeated 1 time ---
May 7 11:21:17 Cowboy kernel[0]: IOSurface: buffer allocation size is zero
May 7 11:42:14: --- last message repeated 4 times ---
May 7 11:51:45 Cowboy kernel[0]: nspace-handler-set-snapshot-time: 1336409506
May 7 12:08:58 Cowboy kernel[0]: hibernate image path: /var/vm/sleepimage
May 7 12:08:58 Cowboy kernel[0]: sizeof(IOHibernateImageHeader) == 512
May 7 12:08:58 Cowboy kernel[0]: Opened file /var/vm/sleepimage, size 8589934592, partition base 0x0, maxio 400000 ssd 1
The seri
May 7 12:08:58 Cowboy kernel[0]: hibernate image major 14, minor 0, blocksize 512, pollers 5
May 7 12:08:58 Cowboy kernel[0]: hibernate_alloc_pages flags 00000000, gobbling 0 pages
al outpu
May 7 12:08:58 Cowboy kernel[0]: hibernate_setup(0) took 0 ms
May 7 12:09:01 Cowboy kernel[0]: en1: BSSID changed to 00:40:96:a1:33:c9
May 7 12:09:01 Cowboy kernel[0]: wlEvent: en1 en1 Link DOWN
t
May 7 12:09:01 Cowboy kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
p o r
May 7 12:09:01 Cowboy kernel[0]:
t was no
May 7 12:09:37 Cowboy kernel[0]: hibernate_page_list_setall start 0xffffff80d4cff000, 0xffffff80d4f98000
availabl
May 7 12:09:37 Cowboy kernel[0]: hibernate_page_list_setall time: 415 ms
t
May 7 12:09:37 Cowboy kernel[0]: pages 2040801, wire 338507, act 950045, inact 182445, spec 36, zf 113125, throt 0, could discard act 169869 inact 207719
e for deb
purgeable 38826 spec 40229
May 7 12:09:37 Cowboy kernel[0]: hibernate_page_list_setall found pageCount 1584158
May 7 12:09:37 Cowboy kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0
ug!
May 7 12:09:37 Cowboy kernel[0]: IOHibernatePollerOpen(0)
May 7 12:09:37 Cowboy kernel[0]: writing 1583874 pages
May 7 12:09:37 Cowboy kernel[0]: encryptStart 4f820
May 7 12:09:37 Cowboy kernel[0]: encryptEnd 108b02c0
May 7 12:09:37 Cowboy kernel[0]: image1Size 474682880, encryptStart1 4f820, End1 108b02c0
May 7 12:09:37 Cowboy kernel[0]: encryptStart 1c4b1600
May 7 12:09:37 Cowboy kernel[0]: encryptEnd b7957b30
May 7 12:09:37 Cowboy kernel[0]: PMStats: Hibernate write took 35189 ms
May 7 12:09:37 Cowboy kernel[0]: all time: 35189 ms, comp bytes: 6487916544 time: 6366 ms 971 Mb/s, crypt bytes: 2882564048 time: 4618 ms 595 Mb/s,
May 7 12:09:37 Cowboy kernel[0]: image 3080027136, uncompressed 6487916544 (535388), compressed 3068648576 (47%), sum1 ec64ffd2, sum2 571d97a2
May 7 12:09:37 Cowboy kernel[0]: wired_pages_encrypted 224499, wired_pages_clear 113814, dirty_pages_encrypted 1245651
May 7 12:09:37 Cowboy kernel[0]: hibernate_write_image done(0)
May 7 12:09:37 Cowboy kernel[0]: sleep
May 7 14:06:05 Cowboy kernel[0]: Wake reason: EC.LidOpen (User)
May 7 14:06:05 Cowboy kernel[0]: en1: 802.11d country code set to 'X0'.
May 7 14:06:05 Cowboy kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153
157 161 165
May 7 14:06:06 Cowboy kernel[0]: Sound assertion "0 == fAudioEngineArray" failed in AppleHDADriver at line 3163 goto Exit
May 7 14:06:08 Cowboy kernel[0]: Previous Sleep Cause: 5
May 7 14:06:08 Cowboy kernel[0]: MacAuthEvent en1 Auth result for: 00:40:96:a0:63:95 MAC AUTH succeeded
May 7 14:06:08 Cowboy kernel[0]: wlEvent: en1 en1 Link UP
May 7 14:06:08 Cowboy kernel[0]: AirPort: Link Up on en1
May 7 14:06:08 Cowboy kernel[0]: en1: BSSID changed to 00:40:96:a0:63:95

Source
level deb
your so ug was ther
urce wa e, if
s ASM

My Roots in Agile

Kent Beck Ron Jeffries
Ward Cunningham Martin Fowler

Lets Have a Meeting
Robert Martin Alistair Cockburn

How Did I Find Myself at Agile
Manifesto Meeting?
Skiing!
James, do
you want to
go to the
Lightweight
Methods
Summit in
Snowbird? Sure Bob,
Ill go.

Before the
Agile Manifesto

FlashDriver
+ Program(addr, data)
FlashDriverTest + ProtectBlock(block)
+ EraseBlock(block)
//etc
<<interface>>
IO
+ Read(addr) : data
+ Write(addr, data)
<<implements>>
MockIO
<<implementation>>
+ Expect_Read(addr, data) <<hardware>>
IO
+ Expect_Write(addr, data)
<<interface>>
OurCode OurServiceRequests
+ doSomething()
Big Framework
<<implements>>
Big Framework
Client
Messaging
+ send() BFw Adaptor
+receive
MessageProcessor SerialDriver SemaphoreFake
WaitForMessage(buffer, length)
WaitForString(buffer, length, semophore)
Pend(semaphore)
Message
Interrupt is Processor is
collecting blocked,
characters waiting for
its
characters
Post(semaphore)
return
Copyright James W. Grenning

20
That may not have been
Watts intention, but it was the
message that industry was
hearing

Did that work?
i n d u s t r y
Most the
f r o m d e f e c t s ,
suffere d
d f r u st r a t i on .
delays a n

The first and foremost
statement stresses people

People and Values were Central
to Forming Agile

d e v e l o p m e n t i s
Softwa r e
a l l y a b o u t t h e
not cen t r
n d d o c u m e n t s
proces s a

static void checkEvent(ScheduledLightEvent* lightEvent)
{
if (randomEventAlreadyHappenedToday(lightEvent))
return;
http://www.freestockphotos.biz/license.php?id=9749
!
if (!TimeService_MatchesNow(lightEvent->day, lightEvent->minute +
lightEvent->randomMinutes))
return;
!
operateLight(lightEvent);
!
ScheduledLightEvent_Randomize(lightEvent);
preventAnotherRandomLightOperation(lightEvent);
}
!
void LightScheduler_Wakeup(void)
thanks: lumaxart
{
int i;
!
for (i = 0; i < MAX_EVENTS; i++)
Its about col

{
if (eventList[i].id != UNUSED)
laboration,
checkEvent(&eventList[i]);
}
}
customer, co
de, and prod
uct!

The Public First Scrum Class
(May 2003)

Certified Scrum Masters
400000
300000
200000
100000
0
2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014
Year
Certified Scrum Students
400,000
Certified Scrum Developers Certified Scrum Masters

300,000
200,000
100,000
0
2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014
Year
32
http://www.deviantart.com/art/Micro-manage-134602454
What is Scrum?
Scrum exposes every inadequacy or

dysfunction within an organizations
product and system development
practices. The intention of Scrum is to
make them transparent so the
organization can fix them.
Ken Schwaber
From an interview with Ken Schwaber on agilecollab - http://www.agilecollab.com/interview-with-ken-schwaber

Like in the 80s! Short Cycle
Improvement

Except without the Difficult
Improvement Part
ACT

36
37
Not long after graduating
college, I joined an office product
company and started selling
copiers. I loved what i did.
James Murphy
I had no flight
experience, but I was
going to fly jets.
James Murphy
Just two years after signing up, I was not only
flying, I was flying the supersonic F-15 Eagle

t r ef le ct i o n
Hone s
an al y s i s
an d
Pilots w er e
a t u r a t e d
Task S

The Debrief outcome, gives the
refuel job to the boom operator, and

All Rights Reserved @jwgrenning.
a rest for the pilot.
OOP, Munich 2015
www.wingman-sw.com
Oop@wingman-sw.com
45
What are We Supposed to Do?
The intention of Scrum is to make

them [your problems] transparent
so the organization can fix them.
Ken Schwaber

How are we doing?

Many think theyre doing great
In Company A 32% of the engineers said

they were in the top 5% of skill and quality
of work in the company. That seemed
outrageous until you go to Company B,
where 42% said they were in the top 5%.
So much for being lonely at the top.
Everybody tends to think that they are at
the top much more than they really are.
From David Dunning via Smart Planet
bit.ly/we-think-we-are-smart
40% think theyre in the
top 5%
!
87.5% of them are wrong!

10 Year Agile Celebration

t d o w e , a s
Wh a
be r o f t h e
m e m
agile
u n i t y
comm
to f i x ?
need
We believe the agile
community must:
#1 Demand technical excellence

#2 Promote Individual [Change] and
Lead Organizational Change

Technical Excellence www.wingman-sw.com
Remember what Ken Said?
"The intention of Scrum is to make

them [the problems] transparent so the
organization can fix them."
Ken Schwaber
Unfortunately, many organizations
change Scrum to accommodate the
inadequacies or dysfunctions instead
of solving them.

Everything is Going Smoothly
Iteration 1 Iteration 2 Iteration 3 Iteration 4 Hardening

ile 2014 La, la la.
Im lookin
for bugs
Thank you: Hubert Stoffels, from Pittsburgh, USA '''Title:''' Jonathan's Run Falls
'''Description:''' http://commons.wikimedia.org/wiki/File:Jonathan%27s_Run_Falls.jpg
HELLLLP!

Thanks to Yorian, Picture of a waterfall nearby Flam, Norway http:// 59
commons.wikimedia.org/wiki/File:Waterfall_in_Norway.jpg
What Happens We Save Test Until the End?
Test and Fix Test and Fix

Iteration 1 Iteration 2 Iteration 3 Iteration 4 Test Hardening
and Fix
Test and Fix
Test and Fix Test and Fix

Do Your Work Degrade into a Fire Fight?
Why Do
es This
Happen
??

Hackin
g in new
features
, chasin
manag g and
ing bug
not Tech s is
nical
Excellen
ce
Whats the Problem?
The biggest problem worldwide for

Scrum teams is getting shippable code
at the end of every sprint.
Jeff Sutherland
from: Scrum with XP and Beyond

The cad
ence of
changes d e v elopmen
with Sc t
rum
Are you
changin
enginee g the ho
r your p w you
roducts
?
The Marriage of Scrum and XP

So Far the Marriage is Unequal
400,000
Certified Scrum Developers Certified Scrum Masters

300,000
s six 333820
k e
s
ta
ter
n i t D ?
as
200,000
e a C S
M
i s m o n e 54509
m
s t h s te r
u
o e a
cr
D m
dS
s t o
M
fie
CS
100,000
rti
Ce
T
y
0
2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014
Year
- A Brief Debrief -
Current Development Practice
in Industry
As viewed from the pre-

training surveys I use to
better understand
attendee backgrounds

How do you test
your code?

May 7 11:42:14: --- last message repeated 4 times ---
May 7 12:08:58 Cowboy kernel[0]: hibernate image path: /var/vm/sleepimage
May 7 12:08:58 Cowboy kernel[0]: sizeof(IOHibernateImageHeader) == 512
May 7 12:08:58 Cowboy kernel[0]: Opened file /var/vm/sleepimage, size 8589934592, partition base 0x0, maxio 400000 ssd 1
May 7 12:08:58 Cowboy kernel[0]: hibernate image major 14, minor 0, blocksize 512, pollers 5
May 7 12:08:58 Cowboy kernel[0]: hibernate_alloc_pages flags 00000000, gobbling 0 pages
May 7 12:08:58 Cowboy kernel[0]: hibernate_setup(0) took 0 ms
May 7 12:09:01 Cowboy kernel[0]: en1: BSSID changed to 00:40:96:a1:33:c9
May 7 12:09:01 Cowboy kernel[0]: wlEvent: en1 en1 Link DOWN
May 7 12:09:01 Cowboy kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
May 7 12:09:01 Cowboy kernel[0]:
May 7 12:09:37 Cowboy kernel[0]: hibernate_page_list_setall start 0xffffff80d4cff000, 0xffffff80d4f98000
May 7 12:09:37 Cowboy kernel[0]: hibernate_page_list_setall time: 415 ms
May 7 12:09:37 Cowboy kernel[0]: pages 2040801, wire 338507, act 950045, inact 182445, spec 36, zf 113125, throt 0, could discard act 169869 inact 207719
purgeable 38826 spec 40229
May 7 12:09:37 Cowboy kernel[0]: hibernate_page_list_setall found pageCount 1584158
May 7 12:09:37 Cowboy kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0
May 7 12:09:37 Cowboy kernel[0]: IOHibernatePollerOpen(0)
May 7 12:09:37 Cowboy kernel[0]: writing 1583874 pages
May 7 12:09:37 Cowboy kernel[0]: encryptStart 4f820
May 7 12:09:37 Cowboy kernel[0]: encryptEnd 108b02c0
May 7 12:09:37 Cowboy kernel[0]: image1Size 474682880, encryptStart1 4f820, End1 108b02c0
May 7 12:09:37 Cowboy kernel[0]: encryptStart 1c4b1600
May 7 12:09:37 Cowboy kernel[0]: encryptEnd b7957b30
May 7 12:09:37 Cowboy kernel[0]: PMStats: Hibernate write took 35189 ms
May 7 12:09:37 Cowboy kernel[0]: all time: 35189 ms, comp bytes: 6487916544 time: 6366 ms 971 Mb/s, crypt bytes: 2882564048 time: 4618 ms 595 Mb/s,
May 7 12:09:37 Cowboy kernel[0]: image 3080027136, uncompressed 6487916544 (535388), compressed 3068648576 (47%), sum1 ec64ffd2, sum2 571d97a2
May 7 12:09:37 Cowboy kernel[0]: wired_pages_encrypted 224499, wired_pages_clear 113814, dirty_pages_encrypted 1245651
May 7 12:09:37 Cowboy kernel[0]: hibernate_write_image done(0)
May 7 12:09:37 Cowboy kernel[0]: sleep
May 7 14:06:05 Cowboy kernel[0]: Wake reason: EC.LidOpen (User)
May 7 14:06:05 Cowboy kernel[0]: en1: 802.11d country code set to 'X0'.
May 7 14:06:05 Cowboy kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153
157 161 165
May 7 14:06:06 Cowboy kernel[0]: Sound assertion "0 == fAudioEngineArray" failed in AppleHDADriver at line 3163 goto Exit
May 7 14:06:08 Cowboy kernel[0]: Previous Sleep Cause: 5
May 7 14:06:08 Cowboy kernel[0]: MacAuthEvent en1 Auth result for: 00:40:96:a0:63:95 MAC AUTH succeeded
May 7 14:06:08 Cowboy kernel[0]: wlEvent: en1 en1 Link UP
May 7 14:06:08 Cowboy kernel[0]: AirPort: Link Up on en1
May 7 14:06:08 Cowboy kernel[0]: en1: BSSID changed to 00:40:96:a0:63:95
Congra
tulation
s!!!
You are using state of art
practices from 1979
Debug-l
ater
Program
ming

The Physics of Debug Later
Programming (DLP)
Td Tfind T fix
Time
Mistake made Bug discovery

(bug injection)
Bug found Bug fixed
As Td increases, Tfind increases dramatically

Tfix is usually short, but can increase with Td
http://www.renaissancesoftware.net/blog/archives/16
A Bugs Life
From http://www.softwaretestinghelp.com/bug-life-cycle/
Your program will have
bugs. And they will
surprise you when you
find them.

Zune 30G
8
200
1,
r3
be
m
ce
Technical Excellence De www.wingman-sw.com 82
BOOL ConvertDays(UINT32 days, SYSTEMTIME* lpTime)

One That Got Away
static void SetYearAndDayOfYear(RtcTime* time)
{
int days = time->daysSince1980;
int year = STARTING_YEAR;
while (days > 365)
{
if (IsLeapYear(year))
{
if (days > 366)
{
days -= 366;
year += 1;
}
}
else
{
days -= 365;
year += 1;
}
}
!
time->dayOfYear = days;
time->year = year;
}

This Test Could Have Prevented it
TEST(Rtc, check20081231)
{
days = daysSince1980(2008, 366);
CHECK(ConvertDays(days, &time));
assertDate(WED, 2008, 12, 31);
}
!

h e r e d o t h e
W
o m e f r om ?
bugs c

Really, Its Not Our Fault?
We put
them th
ere
James D. Murphy

This Work Flow is Designed to Allow
Defects
Development
Test
Defects
A Bugs Life
From http://www.softwaretestinghelp.com/bug-life-cycle/
Edsger Dijkstra
If you want more effective

programmers, you will discover
that they should not waste their
time debugging, they should not
introduce the bugs to start with.

We tend to do what we know
People do what they can conceive of,

but sometimes there are better solutions,
or considerations and risks they never
knew were out there. They dont take a
solution they dont know about.

1 year 1 year 1 year 1 year 1 year
Ive got 10 years

experience!
1 year 1 year 1 year 1 year 1 year

It is almost impossible for an individual left to their

own devices to get self-assessment right. The worth of
ones ideas runs through other people. That is, workers
should pay attention to what other workers are doing.
You can watch other people to benchmark how they
handle the same sorts of tasks or situations. Seek out
feedback from other workers or managers.

Kent Beck Ron Jeffries
Ward Cunningham Martin Fowler

eHarmony Match

XP Identifies Shared Values
and Defines the Technical Practices
Needed for Growing Computer Software

Quality is important Focus on it every day
Testing is good Test all the time
Reviews are good Review all the time
Talk to your customer

Customer input is good
every day
Keep the plan alive, plan to
Planning is important replan

Programming (DLP)
Td Tfind T fix
Time

(bug injection)
Bug found Bug fixed

HELLLLP!

Thanks to Yorian, Picture of a waterfall nearby Flam, Norway http:// 101
commons.wikimedia.org/wiki/File:Waterfall_in_Norway.jpg
Edsger Dijkstra
If you want more effective

programmers, you will discover
that they should not waste their
time debugging, they should not
introduce the bugs to start with.

Write a test
T Watch it fail
Make it pass
D Refactor (improve)
Repeat until done
D

If test moved upstream, could we get
working features to flow?
Copyright 2008-2013
2008-2014 James W. Grenning
Technical
devconfu,Excellence
Nov 2013 www.renaissancesoftware.net
www.wingman-sw.com 104
All Rights Reserved.
Reserved For@jwgrenning.
use by training attendees. OOP,Riga,
Munich
Latvia
2015
Test Driven Development james@renaissancesoftware.net
Oop@wingman-sw.com
Development and Test are a Continuum
Preventing Defects
Development
Test

The Physics of Test Driven
Development
T d Tfind T fix
Time
Mistake
Mistake fixed
made
Mistake Root cause
discovery found
When Td approaches zero, Tfind approaches zero

In many cases, bugs are not around long enough to be considered
bugs.
See: http://www.renaissancesoftware.net/blog/archives/16

i s a c h a l l e n g e .
TD D
s h a r d t o l e a r n .
It
TDD i s F U N !
A Complex system that
works is invariably
found to have evolved
from a simple system
that worked.

Is your team doing TDD?
Does your team create

unit tests?
n g t es ts a f te r i s
W r i t i
not so f u n , b u t
e st s a re C r i t ic a l !
Uni t T
System Level Tests Cannot be
Thorough
How many sub-system tests are needed?
Tests
10
5 interactions states 5 interactions
10 5 interactions 10
states states

TDD unit tests can be thorough
How many unit tests are needed?
Tests Tests
10
5 interactions states 5 interactions
10 5 interactions 10
states states

Looks and
feels right
Wired properly and

meets customer needs
Solid
foundation

Tests Must be Automated

Assume Test Effort is
Proportional to
25
Development Effort
20
Effort
15
10 dev
5 test
Iterations
If a system is working,
leave it alone. Don't
change anything.
Systems dont
appreciate being fiddled
and diddled with.
25% of all defects are

introduced while
changing and fixing code.
[R.B Grady, Software Process Improvement]

System Antics
System - something setup to attain a goal
nt r ic
, o r ecce
lou s
f ri v o
i n g ,
u s v i o r
s - am b e ha
n t i c
A

Systems

System Antics

Because
system
up -- we s act
have to
very car b e
eful.

Manual Test is
Unsustainable
25
20 w t h
le gro
Effort
a b
15 s ta in
su
Un
10 dev
5 test
Iterations
Risk Accumulates in
the Untested Code Gap
25 Untested Code Gap
20 w t h
le gro
Effort
a b
15 s ta in
su
Un
10 dev
5 test
Iterations
My Take Away
Tests Must be Automated
Keep the cost of retest low
Kee p th e s ys t e m
running
Try to Reframe the Problem
We cant afford t
o write automated
it takes away fro tests,
m adding new fe
atures
o n o t a u t o m a t e t e s ts ,
We cant afford t y
e s t ti m e t a k e s a w a
the manual ret
i n g n e w f e a t u r e s
from add
We believe the agile
community must:
#1 Demand technical excellence

#2 Promote Individual [Change] and Lead
Organizational Change

Technic
al
Excellen
ce isnt
Just Pas
sing
Tests
Why d o e s co d e
structur e m a t t e r ?

l u e s o f S o f twa r e
The Two Va

Defined
Refactoring is the process of changing a software

system in such a way that it does not alter the external
behavior of the code yet improves its internal
structure. [REF]
!
Refactoring Debt

Refactoring Goal
Clean code that works

Ron Jeffries

How?
Remove duplication
Fix bad names
J.B. Rainsberger

Donald Knuth Says
Let us change our

traditional attitude to the
construction of programs.
Instead of imagining that
our main task is to
instruct a computer what to
do, let us concentrate rather
on explaining to human
beings what we want a
computer to do.

Really, Its Not Our Fault?
How are
we doin
at that o g
ne?
James D. Murphy

Spaghetti Slide

Martin Fowler Says
Any fool can write code

that the compiler
understands, but it takes
real skill to write code
other programmers can
understand.
From Refactoring - Improving the Design of Existing Code

Code Badness Over time
100
75
Code Badness
50
25
Time
100
75
Code Badness
50
25
Time
Developers Need to Know and Practice
Refactorings Three Critical Skills
Recognize what is wrong, fix it!

Keep the code working the whole time!
If a system is working,
leave it alone. Don't
change anything
Systems dont
appreciate being fiddled
and diddled with

Refactoring vs.
Humpty Dumpty Redesign
ether. Envisioned
to g
u t i t b ac k
i g n e ffort. design
e i t a part, p during redes en
Tak
i s b roken Brok
stem g
T h e s y Debu rk
o
Code with Rew dictable
e
design problem Unpr py
p
Refacto Unha
r to the Improved
Test are better d
a lways p esign. design that works
The sys assing.
tem is n
ever bro
ken.
Humpty Dumpty from The Book of Knowledge,

p. 968, Vol. III, The Grolier Society, New York, 1911.

Automated Tests Make Refactoring Safer
Test Move
Test Extract
Test Replace switch
Test Extract
Test Encapsulate
Test Move
Test Extract
Test Rename

Sustain Low Code Badness Over time
100
75
Code Badness
50
25
Time
Spaghetti Slide

100
75
Code Badness
50
25
Time
Why d o e s co d e
structur e m a t t e r ?

The Law ye r s ar e
Coming

a s l i t t l e a s a s i n g l e b i t
'v e d e m o n s t r a t ed h o w
"We t r o l o f t h e
s e t h e d ri v e r t o l o s e c o n
flip c a n c a u
c a r s d u e t o s o f t w a r e
engine speed in real e t ec t e d b y a n y
n t h a t i s n o t r el i a b l y d
malfun ct i o
fail-safe," f B a r r G r ou p
a r r , C T O , c o - f o u n d e r o
- M i c h ae l B
http://www.eetimes.com/document.asp?doc_id=1319903 151
Kitchen Sink (a.k.a. do it all) task
Responsible for closed loop control and failsafes
ov erfl ow an d so ft w ar e bu gs le d to m em or y
Stack
on , he sa id . A nd it tu rn s ou t th at th e crux of
corrupti
e w as th es e m em or y co rr up ti on s, w hi ch ac te d
the issu
"like ricocheting bullets."
n t w a n t t o cr e at e
You do
this website

Why doesnt your team use
TDD and Refactoring and the
other technical practices of
Agile?

Were different!

We cant use TDD
and Refactoring!

Everything is fine.

REALLY!

pay no attention
to that fire over
there
REALLY!

Were BUSY!
ACT

What Slows You Down?

90%
done
1

Were different!

Embedded software
is special

Web service software
is special

Health Insurance
software
is special

Design automation
is special

Financial Software
is special

YOU
are special

It just does not
matter.

What are We Supposed to Do?
The intention of Scrum is to make

them [your problems] transparent
so the organization can fix them.
Ken Schwaber

What is the biggest problem of getting
there?
The biggest problem worldwide for

Scrum teams is getting shippable code
at the end of every sprint.
from: Scrum with XP and Beyond

W h a t is i n yo ur
way?

y B o s s w nt
o
` let me
M

o p m e n t
D e v e l t
o n s w a n
a n i z a t i
Org o pm e n t .
t d e v e l
fas
178
t i m e f o r
t h a v e
I don r a s t u f f !!
t h i s e x t
a ll
179
Programming (DLP)
Td Tfind T fix
Time

(bug injection)
Bug found Bug fixed

Refactoring Conferences
More
Domain Development New people
People who Knowledge teams
learn things
Disciplined
process Orange
system Fridays Mentor other
complexity More work HR interviews
people
Skills coordination
Cowboy Daily
coding Work Meetings
Technical experience
Unstable /
debt slow Tests Slow workstation Waste and
Meetings UX meetings
Non-value
added activity
Deadlines Short term
Development
boost
Speed Board
Overtime Work / Life meetings
Sport at work
balance
Passion
Sport /
Hobbies
Open outside work
Space
Cooperative
Bugs testing Prototypes
Focused Re-work
Work Large WIP
people rotations
between teams Unclear
Wait states requirements
Multi-tasking Good Specs
http://bit.ly/sw-dev-speed
Emergency
rotation Bad UX - Dev
IM/Skype Do right things transition
Good Features
Fast feedback Ranking Model
Michael Dubakov
Good It depends Bad
Increasing eect Decreasing eect Speed in SW Development
http://bit.ly/sw-dev-speed 182
system
complexity
Skills
Development
Speed
183
Technical
debt

Development
boost
Speed
Overtime
184
system
complexity
Technical
debt

Development
boost
Speed
Overtime
185
system
complexity
Technical
debt

Development
boost
Speed
Overtime
Focused
Work
186
system
complexity
Technical
debt

Development
boost
Speed
Overtime
Focused
Work Large WIP
people rotations
between teams
Multi-tasking
Emergency
rotation
187
system
complexity
Technical
debt

Development
boost
Speed
Overtime
Bugs
Focused Re-work
Work Large WIP
people rotations
requirements
Multi-tasking
Emergency
rotation
Do right things
188
system
complexity
Technical
debt
Slow workstation

Development
boost
Speed
Overtime
Bugs
Focused Re-work
Work Large WIP
people rotations
requirements
Multi-tasking
Emergency
rotation
Do right things
189
More
Development
teams
system
complexity
Technical
debt
Slow workstation

Development
Development
boost
Speed
Speed
Overtime
Bugs
Focused Re-work
Work Large WIP
people rotations
requirements
Multi-tasking
Emergency
rotation
Do right things
190
More
Development New people
teams
system
complexity HR interviews
More work
Mentor other
coordination
people
Technical
debt
Slow workstation Waste and

Short term Non-value
Deadlines Development
Development
Development
boost added activity
Speed
Speed
Overtime
Meetings
Bugs
Focused Re-work
Work Large WIP
people rotations
requirements
Multi-tasking
Emergency
rotation
Do right things
191
More
teams
system
More work
Mentor other
coordination
people
Technical
debt

Development
Development
Speed
Speed
Overtime
Meetings
Bugs
Focused Re-work
Work Large WIP
people rotations
requirements
Multi-tasking
Emergency
rotation
Do right things
192
Of cou
rse we
have t d o nt
ime!!
193
More
Conferences Development New people
teams
Domain
system People who Knowledge
complexity learn things HR interviews
More work
Mentor other
coordination
people
Technical
debt
Skills

Work
Short termexperience Non-value
Development
Development
Speed
Speed
Overtime
Development
Speed Meetings
Work / Life
balance
Passion Bugs
Focused Re-work
Work Large WIP
people rotations
requirements
Multi-tasking
Emergency Focused
rotation Work
Do right things
Conferences
Domain
People who Knowledge
learn things
Skills
Work
experience
Development
Speed
Work / Life
balance
Passion
Focused
Work
system
complexity
Technical
debt

Development
boost
Speed
Overtime
l i n e s ,
r e d e a d
y a s i n g
Wh d i n c r e a
m e , a n h a
o v e rt i b t s u c
i c a l d e
t e ch n t ic e i n
a r p r a c
po p u l t ?
lo p m e n
deve 196
e d e s t r u c ti v e p ra c t ic e s
Why a r e t h
o r e p r e v a l e n t?
so much m More
teams
system
More work
Mentor other
coordination
people
Technical
debt

Development
Development
Speed
Speed
Overtime
Meetings
Bugs
Focused Re-work
Work Large WIP
people rotations
requirements
Multi-tasking
Emergency
rotation 197
Do right things
People do what they can conceive of,

but sometimes there are better solutions,
or considerations and risks they never
knew were out there. They dont take a
solution they dont know about.

Managers, Leaders and Coaches
TODO
Make sure your team
knows state of the art
practices
Support
Make sure your learning,
organization problem solving,
knows why they and continuous
are important improvement
Yeah but Im an engineer

People are generally
doing the best they know
Often, people dont know

what they dont know
Developers
TODO
Build Trust -
Become an
Make your
expert in
Work Visible
your craft
Work with
others Become an
learn and try advisor to your
new things organization
a r e o f l i m it s
Be w

Scrum Masters
TODO
Encourage your
people to be
problem solvers N ot do gm a
followers
Remember: there are no scrum slaves
Managers
TODO:
Grow great Stop

teams Motivating
Your Team

Motivation
Motivating an individual or
a team is hard
While demotivating them is

really easy!
Avoid De-motivators
Unrealistic Punishing
deadlines the truth
Encouraging
poor quality work
Lack of trust Stretch goals
Motivators
Knowing Problem
the Vision solving
Knowing
Trust
why it is
important Mutual respect
I Tried to Avoid
Computers

Thanks @tech_faq
!
https://twitter.com/tech_faq/status/386781833343414272/photo/1
210
People will pay me
for this?!!

Putting out fires in the untested
code gap is not technical
excellence
25 Untested Code Gap

20
r owth
le g
Effort
a b
15 st ain
nsu
U
10 dev
5 test

http://commons.wikimedia.org/wiki/File:Abies_nordmanniana_PAN_2.jpg
Copyright 2008-20XX
2008-2014 James
JamesW.
W.Grenning

Grenning
__EVENT__ www.wingman-sw.com 213
All Rights Reserved @jwgrenning. OOP,The
Munich
End 2015 james@wingman-sw.com
Oop@wingman-sw.com
Demand Technical Excellence
Talk to me on Twitter
@jwgrenning!
!
Find my book at!
http://wingman-sw.com/tddec
!
Find me on linkedin.com
http://www.linkedin.com/in/jwgrenning
Please remind me how we met.
!
http://www.wingman-sw.com
http://www.wingman-sw.com/blog


OOP 2015 Technical Excellence - Key

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OOP 2015 Technical Excellence - Key

Uploaded by

Copyright:

Available Formats

Technical Excellence

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Ward Cunningham Martin Fowler

Copyright 2008-2014 James W. Grenning

Robert Martin Alistair Cockburn

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

MessageProcessor SerialDriver SemaphoreFake

Copyright James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Its about col

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Certified Scrum Developers Certified Scrum Masters

Scrum exposes every inadequacy or

From an interview with Ken Schwaber on agilecollab - http://www.agilecollab.com/interview-with-ken-schwaber

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

The intention of Scrum is to make

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

In Company A 32% of the engineers said

87.5% of them are wrong!

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

#1 Demand technical excellence

Copyright 2008-2014 James W. Grenning

"The intention of Scrum is to make

Copyright 2008-2014 James W. Grenning

Iteration 1 Iteration 2 Iteration 3 Iteration 4 Hardening

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Test and Fix Test and Fix

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

The biggest problem worldwide for

from: Scrum with XP and Beyond

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Certified Scrum Developers Certified Scrum Masters

As viewed from the pre-

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Mistake made Bug discovery

As Td increases, Tfind increases dramatically

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning

Copyright 2008-2014 James W. Grenning