The document discusses trends in software development for 2014, including clean code and software craftsmanship, DevOps, continuous delivery, Docker and Vagrant, scaling agile, and microservices. For each trend, it provides a brief description and discusses possible impacts and how teams can implement the trend to improve team performance and deliver value through shorter cycles, faster learning, and lower risk development.

1. Fredrik Wendt
fredrik@growing-agility.com
@wendtse
Team Performance
The Impact of Clean Code & CD

2. What do you see is trending?
What does your dev team(s) talk about?
#TechnicalExcellence

3. Trends of 2014:
✔ Clean Code & Soft-
ware Craftsmanship
✔ DevOps
✔ Continuous Delivery
✔ Docker & Vagrant
✔ Scaling Agile
✔ Microservices

4. For each trend:
– What is it?
– Possible impact?
– How to do it?
Big picture
Technical Excellence
Trends of 2014:
✔ Clean Code & Soft-
ware Craftsmanship
✔ DevOps
✔ Continuous Delivery
✔ Docker & Vagrant
✔ Scaling Agile
✔ Microservices

5. ✔ Clean Code & Soft-
ware Craftsmanship
✔ DevOps
✔ Continuous Delivery
✔ Docker & Vagrant
✔ Scaling Agile
✔ Microservices

7. The primary recipient of the
source code your team(s) write?
What's the main challenge
for that source code to
be put to effective use?

8. The primary recipient of the
source code your team(s) write?
What's the main challenge
for that source code to
be put to effective use?

10. Why?
✔ Lower barrier to entry
✔ Higher quality
✔ Fewer bugs
✔ Less firefighting
✔ Higher throughput
✔ Job satisfaction

11. 90%!
Write to read

12. Computers scale easily
Humans don't scale

13. Computers scale easily
Humans don't scale
Humans are expensive
Computers aren't

14. Why?
✔ Lower barrier to entry
✔ Higher quality
✔ Fewer bugs
✔ Less firefighting
✔ Higher throughput
✔ Job satisfaction

15. How?
✔ Pair programming
✔ Code reviews
✔ Book circles
✔ Online courses
✔ Coding dojos
Tools

18. A fool can write code
that a computer can understand.
Good programmers write code
that humans can understand.
- Martin Fowler

20. DevOps

21. more features
faster, sooner
stable systems
24/7 availability

23. What?
Changing how IT operates,
in order to
win as a whole!
✔ Systems Thinking, Flow
✔ Feedback
✔ Experimentation &
Learning

24. What?
Changing how IT operates,
in order to
win as a whole!
✔ Systems Thinking, Flow
✔ Feedback
✔ Experimentation &
Learning

25. How?
✔ Collaboration
✔ Automation
✔ Progressive Deployment
✔ Continuous Testing
✔ Continuous Delivery
✔ Continuous Monitoring

26. ✔ Clean Code & Soft-
ware Craftsmanship
✔ DevOps
✔ Continuous Delivery
✔ Docker & Vagrant
✔ Scaling Agile
✔ Microservices

28. Continuous Delivery is
an approach to delivering software that
reduces the cost, time and risk
of delivering incremental changes to users.

29. C. Integration
C. Delivery
C. Deployment

30. C. Integration: ability to integrate easily
C. Delivery: release on demand
C. Deployment: release is default

31. C. Integration: build?
C. Delivery: deploy, upgrade?
C. Deployment: incremental change?

32. C. Integration: build?
C. Delivery: deploy, upgrade?
C. Deployment: feature! A/B

35. How?
✔ Version Control Everything
✔ Automate just about Everything
✔ Pipeline – Value Stream Map

38. ✔ Clean Code & Soft-
ware Craftsmanship
✔ DevOps
✔ Continuous Delivery
✔ Docker & Vagrant
✔ Scaling Agile
✔ Microservices
Enables
fast,
low-risk
deployments
of incremental
changes

39. ✔ Clean Code & Soft-
ware Craftsmanship
✔ DevOps
✔ Continuous Delivery
✔ Docker & Vagrant
✔ Scaling Agile
✔ Microservices

41. Hardware Hardware
Host OS Host OS
Hypervisor Docker Engine
Guest OS Guest OS
Bins/Libs Bins/Libs
App A App B
Bins/Libs Bins/Libs
App A App B
Virtualization Containerization

42. Hardware Hardware
Host OS Host OS
Hypervisor Docker Engine
Guest OS Guest OS
Bins/Libs Bins/Libs
App A App B
Bins/Libs Bins/Libs
App A App B

43. Hardware Hardware
Host OS Host OS
Hypervisor Docker Engine
Guest OS Guest OS
Bins/Libs Bins/Libs
App A App B
Bins/Libs Bins/Libs
App A App B

44. Hardware Hardware
Host OS Host OS
Hypervisor
Guest OS Guest OS
Bins/Libs Bins/Libs
App A App B
Bins/Libs Bins/Libs
App A App B

45. Bins/Libs
App A
Bins/Libs
App A
Bins/Libs
App A
Bins/Libs
App A
ProdStageCIDevel »»»

47. Docker
✔ Isolated deployment unit
✔ Fully (version) controlled
environment
✔ Same configuration
mechanism
✔ Same tools used by Dev
and Ops

48. Docker
✔ Microservices
✔ Orchestration circus
✔ May add complexity to
development work

49. Describes how to setup
one or more machines.
Base box: Ubuntu
Install : Eclipse, Git,
: Java8
Controlled
Development
Environment!

51. ✔ Clean Code & Soft-
ware Craftsmanship
✔ DevOps
✔ Continuous Delivery
✔ Docker & Vagrant
✔ Scaling Agile
✔ Microservices

52. Lots of people
working on
one product

54. Non-trivial:
✔ Integration
✔ Dependencies
✔ Synchronization
✔ Orchestration
Slicing and dicing?

55. ✔ Clean Code & Soft-
ware Craftsmanship
✔ DevOps
✔ Continuous Delivery
✔ Docker & Vagrant
✔ Scaling Agile
✔ Microservices

60. Microservices
✔ No one clear crisp definition
✔ NOT monolith
✔ Own lifecycle
✔ Manage it's own data
✔ Belongs to one team

61. ✔ Team performance – ability to deliver value in a
period of time, with sustainable pace

62. Better understand
where VALUE lies & what it is,
and when we do,
how to realize it
✔ Shorter cycles
✔ Faster learning (dev, ops, biz)
✔ Lower risk, safer development

63. Better understand
what VALUE is & where it lies,
and when we do,
how to quickly realize it
✔ Shorter cycles
✔ Faster learning (dev, ops, biz)
✔ Lower risk, safer development