Abridged slides from my XP for non-coders workshop delivered at Lean Agile Scotland 2019

1. EXTREME PROGRAMMING TECHNIQUES WITHOUT THE CODE
(ABRIDGED NOTES)
X
EXTREME DELIVERY
Eddie Kenny

2. EDDIE KENNY – “AGILE COACH”
• Working with Agile since 2004 using XP, Scrum, Lean,
Kanban & even helping those afflicted by Scaled Agile.
• Passionate about continuous learning & continuous
improvement
• Coach teams, scrum masters, product owners, leaders,
other coaches, organisations and little humans.
• Co-founder of the Lean Agile Brighton conference.
OCTOBER
17/18TH
I’LL TALK
TO
ANYONE

3. HANDS
UP
TIME

4. ME @
LASCOT
2018
XP
REVISITED

6. SO WHAT ARE
YOU DOING
ABOUT IT?

7. AND NOW …

8. enquiries@kenzen.uk
QUICK RECAP …
t: @eddiekenny9

9. “ATTENTION TO TECHICAL
EXCELLENCE ENHANCES AGILITY”
PRINCIPLE 9/12

10. TECHNICAL PRACTICES MATTER
Many Agile adoptions have
treated technical practices
as secondary compared to
management & team
practices. Our research
shows that technical
practices play a vital role

11. TECHNICAL PRACTICES NEED
TO BE A PRIMARY CONCERN
FOR AGILE ADOPTION &
TRANSFORMATION EFFORTS

12. TECH PRACTICES
POSITIVELY IMPACT
SOFTWARE DELIVERY
PERFORMANCE
AND
ORGANISATIONAL
PERFORMANCE

14. POWER
TOOLS

16. “WE ARE ALREADY
DOING THAT”
“THAT WON’T
WORK HERE”
“IT’S THE TEAMS
JOB TO DECIDE ON
ENGINEERING
PRACTICES, NOT
YOURS”

17. TEST DRIVEN DEVELOPMENT

18. UNIT TESTING vs TDD
DEVELOP CHECK IT WORKS
DEVELOP CHECK 1 & 2 WORK
DEVELOP CHECK 1,2 & 3 WORK
DEVELOP STOP CHECKING
DEVELOP DEVELOP DEVELOP DEVELOP
DEVELOP DEVELOP DEVELOP DEVELOP
TEST …. WTF?
WRITE UNIT TESTS
GET BORED

19. UNIT TESTING vs TDD
DEVELOP IT WORKS
TEST?
WRITE TEST RUN TEST
DEVELOP THEY WORKWRITE TEST RUN TESTS
DEVELOP THEY WORKWRITE TEST RUN TESTS
DEVELOP THEY WORKWRITE TEST RUN TESTS

21. REFACTOR
MERCILESSLY

22. Code refactoring is the process of
restructuring existing code without changing
it’s external behaviour.
Refactoring is intended to improve non-
functional attributes of the software
[E.g. quality, performance, extensibility, readability]

24. YOUR TESTS ARE A SAFETY NET
& DOCUMENT WHAT YOUR SYSTEM SHOULD DO

25. CONTINUOUS
INTEGRATION

26. CONTINUOUS
INTEGRATION?

27. Continuous Integration (CI) is a
practice that requires developers
to integrate code into a shared
repository several times a day. Each
check-in is then verified by an
automated build, allowing teams to
detect problems early.

28. CI FOR A
DOLLAR
A DAY
https://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html

29. enquiries@kenzen.uk
MOB PROGRAMMING
&
TRUNK BASED DEVELOPMENT
t: @eddiekenny9

30. https://www.youtube.com/watch?v=p_pvslS4gEI

31. enquiries@kenzen.uk
THANK YOU
t: @eddiekenny9
CREDITS:
• Amitai Schleier (who’s original TDD workshop this is based on) t: @schmonz
(https://agileoutloud.wordpress.com/2018/05/11/tdd-by-storywriting/)
• Dan North (who taught me TDD and indirectly BDD before it was BDD)
• Dave Coombes & Darren Rowley (who taught me CI, XP, Dependency Injection and lots more)