The document discusses challenges that software teams may face when delivering work. It emphasizes the importance of delivering value to clients through continuous delivery. It recommends establishing layered barriers through practices like test-driven development and continuous integration to catch issues early. However, it notes barriers will be broken and surprises will occur, so teams must make it safe to fail and avoid assuming external support. The overall message is that teams must focus on delivering value to clients above all else.

1. I WIsH I KneW ThAT BEfORe
GETTING tHiS JoB
phillip calçado
http://blog.fragmental.com.br
http://fragmental.tw

2. ThE WoRlD HaS
ChAnGEd

3. CLIenTS
WoN`T TRUST
YOUR
TeaM

4. ThEy`Ve bEEn
BIttEn
bEfOrE

5. YoU Can PRETEND to LIVE
As If NOthING Had
OcCUrReD

6. Or fIgHt FoR
SuRViVaL

7. aNd OnLy ONe ThIng
GuaRanTeEs SuRVivAl:

8. aNd OnLy ONe ThIng
GuaRanTeEs SuRVivAl:
DeLiVeR
vALUE

9. ‣All the time
DeLiVeR ‣At the right
time
vALUE ‣Before it’s too
late

10. SuRpRisEs

11. AvOiD
SuRpRisEs

12. BuIlD
BaRRieRs

13. <interlude>

14. In a REgUlAr
DeV ShOp
(ThaT CoulD Be
YoUrS)

16. Architecture

17. Architecture
Module A
Module B
Module C
Module D
Module E

18. Architecture Test Plan
Module A
Module B
Module C
Module D
Module E

19. Architecture Test Plan
Test Case -
Module A Module A
Test Case -
Module B Module B
Test Case -
Module C Module C
Test Case -
Module D Module D
Test Case -
Module E Module E

20. 010001001
111100011
010110000
110101010
110101010
101010101

21. 010001001
111100011
010110000
110101010
110101010
101010101

22. Δ
SuRpRisE
010001001
111100011
010110000
110101010
110101010
101010101

23. 010001001
111100011
010110000
110101010
110101010
101010101
Feedback

24. 010001001
111100011
010110000
110101010
110101010
101010101
Feedback

25. 010001001
111100011
010110000
110101010
110101010
101010101

26. 010001001
111100011
010110000
110101010
110101010
101010101

27. </interlude>

28. BuIlD
BaRRieRs

29. LaYeReD BaRRieRs
1.Developement
2.Integration
3.Verification
4.Acceptance
5.Production

30. 1.Development
‣Does this change work?
‣Is it “ready”?

31. 2.Integration
‣Works outside my machine?
‣Plays nicely with stuff other
people built?

32. 3.Verification
‣Fulfils the spec?
‣Brittle?
‣Breaks something that was
working before?

33. 4.Acceptance
‣Customer thinks it is ready?
‣Small changes required?

34. 5.Production
‣Does it work in the real world?

36. 1.Development
‣Test-Driven Development
‣Fast Build Process

37. 2.Integration
‣Fast Build Process
‣Continuous Integration

38. 3.Verification
‣Test-Driven Development
‣Tests are part of Continuous
Integration
‣Testers actually write their tests

39. 4.Acceptance
‣Client is always around
‣Sandwich Model (Kickoff-Play-
Walkthrough)
‣Domain-Driven Design

40. 5.Production
‣Incremental delivery
‣Frequent delivery
‣Prod-like environments

41. BuIlD
BaRRieRs

42. BuT Be AwARE
THaT TheY
WILL BE BroKEn

43. ReD AlERt

44. ReD AlERt

45. ReD AlERt

46. ReD AlERt

47. ReD AlERt

49. your team is not the
CentRe oF thE UNivErsE

50. the goal is not to be
faIlpRoOf. it is to
make it sAfe tO FAIL.

51. Do NOT AsSUmE people
will give you SuPPorT

52. keep your career
goals oUt of your
tEaM’s GoAls

53. OBRIGADO
(all pics were stolen from Dawn of the Dead, best
zombie movie evah.)
http://www.thoughtworks.com
work@thoughtworks.com