This document discusses revisiting eXtreme Programming (XP) as a way to enhance agility beyond just adopting a framework like Scrum. It argues that technical practices from XP, like test-driven development and continuous integration, should be a primary focus of agile adoption efforts, not an afterthought. Adopting only Scrum processes without the XP technical practices leads to "flaccid" agility. The document encourages embracing XP's values and technical practices to develop software better, faster, and happier.

1. XP
REVISITED
REDISCOVERING XP AS A
PATHWAY TO ENHANCED
AGILITY
EDDIE KENNY
AGILE COACH

2. • http://leanagilebrighton.co.uk/
• https://www.meetup.com/Lean-Agile-
Brighton/
AGILE COACH
• http://his-scrum-masters-voice.blogspot.com/
• http://coachmachine.blogspot.com/
• http://agilementors.blogspot.com/
@eddiekenny9

3. FAST
FEEDBACK
LOOPS

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

6. ENGINEERING
EFFORT IS
DISCONNECTED
FROM AGILE
PROCESS

8. ANOTHER MEETING?

9. LIBERTARIAN
PATERNALISM
WE KNOW
WHAT’S BEST
FOR YOU

11. AGILE
PROCESS
TECHNICAL
PRACTICE

12. LET’S
REWIND

13. THE
ORIGINAL
PROBLEM
AGILE WAS
SOLVING
FOR?

16. FRAMEWORK
ADOPTION

19. AGILE ADOPTION
=
FRAMEWORK ADOPTION

20. THE GREAT REDUCTIONIST FAÇADE
A.K.A.
SLICE & DICE
A.K.A.
TAYLORISM

24. COMMON
PATTERNS OF
SCRUM ADOPTION

25. SLICING THINGS DIFFERENTLY
SPRINT 1 SPRINT 2 SPRINT 3 SPRINT 4 SPRINT 5
DEVELOP TEST UAT RELEASE
DEVELOP
TEST UAT RELEASEDEVELOP DEVELOP

26. MOVING THE WORK AROUND A BIT
DEV TEST UAT RELEASEDEV TEST DEV TEST
D T UAT RELEASED T D T D T D T D T D T D T D T

27. OVERLAPS & CARRYOVER
DEV TEST UAT RELEASEDEV TEST DEV TEST
D T UAT RELEASED T D T D T D T D T D T D T D T
DEV TEST DEV TEST DEV TEST
D T D T D T D T D T D T D T D T D T

28. DESTRUCTIVE
ABUNDANCE

29. TWICE THE WORK – HALF THE TIME?
WATERFALL DELIVERY
SCRUM SCRUM SCRUM SCRUM SCRUM
XP XP XP

31. THE
POTENTIALLY
SHIPPABLE
INCREMENT
DELUSION

32. FLACCID SCRUM
SCRUM IS A PROCESS
THAT’S CENTRED ON
PROJECT
MANAGEMENT &
DELIBERATELY OMITS
ANY TECHNICAL
PRACTICES .. IN
CONTRAST TO
EXTREME
PROGRAMMING

33. COURAGE
RESPECT
COMMUNICATION
SIMPLICITY
FEEDBACK
COURAGE
RESPECT
FOCUS
OPENNESS
COMMITMENT

34. SCRUM
XP
DAILY SCRUM
SPRINT PLANNING
SPRINT REVIEW
PRODUCT BACKLOG
SPRINT RETROSCRUM MASTER
PRODUCT OWNER
SPRINT BACKLOG
INCREMENT
TEAM
SPRINT
ITERATION
PLANNING GAME
DAILY STAND UP
DEMO
RETRO
TEAM
XP COACH
ONSITE CUSTOMER
PRODUCT BACKLOG
ITERATION BACKLOG
INCREMENT?
CONTINUOUS INTEGRATION
TDD BDD REFACTORING
SUSTAINABLE PACE
PAIR PROGRAMMING
COLLECTIVE OWNERSHIP
AUTOMATED ACCEPTANCE
TESTS

35. SCRUM =
*ARTIFACTS = Product backlog + sprint backlog +
Potentially shippable increment
XP =
Values + Ceremonies + Roles + *Artifacts
+ Technical practices
Values + Ceremonies + Roles + *Artifacts

36. XP = + Technical practicesSCRUM

37. 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

38. CONTINUOUS
INTEGRATION?

39. 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

40. 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

41. REFACTOR
MERCILESSLY

42. POWER
TOOLS

43. CONTINUOUS ATTENTION TO
TECHNICAL EXCELLENCE
ENHANCES AGILITY
THE TECHNICAL PRACTICES ARE PART OF YOUR METHODOLOGY
AND THIS IS HOW WE INVITE THE ENGINEERING COMMUNITY IN

44. BUILD PROJECTS AROUND
MOTIVATED INDIVIDUALS
MOTIVATE TECHNOLOGISTS
WITH CONTINUOUS LEARNING

45. CONTINUOUS
LEARNING
LEADS
TO HAPPY
ENGINEERS

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

48. BRANDING ISSUE
1. EXTREME
2. PROGRAMMING

50. XP

51. BASED ON WHERE
WE ARE NOW
REVISIT
XP

52. CHANGE AGENTS – ADVOCATE FOR XP
(SCRUM ALONE WON’T GET YOU THERE)
LEADERS/ DECISION MAKERS – ADD XP TOO
(SCRUM ALONE WON’T GET YOU THERE)
ENGINEERS – DOUBLE DOWN
(LEARN XP TECHNIQUES PROPERLY)
TO DO

53. EVERYONE
ADD THE XP

54. DEVELOP SOFTWARE
7-Oct-18 AXP Internal 54
BETTER, FASTER, HAPPIER

55. Thank you

56. XP READING
• Flaccid SCRUM
https://martinfowler.com/bli
ki/FlaccidScrum.html
• SCRUM & XP (Mike Cohn)
https://www.mountaingoats
oftware.com/blog/differenc
es-between-scrum-and-
extreme-programming