The document discusses LiveAccounts' journey to implementing continuous delivery practices to improve their software delivery process. Some key points: - They quadrupled feature throughput, shortened delivery times by 87%, and improved team satisfaction. - They evolved their practices incrementally, focusing on automation, common tools/processes, and empowering their cross-functional team. - Changes included setting up a shared development environment, implementing version control/automated builds/testing, and configuring a continuous delivery pipeline to automate deployments. - This reduced lead times from 30 days to 2 hours for new features to reach production.

1. LiveAccounts:
Continuous Delivery in the Real World
Nish Mahanty
Lawrence Song

2. “Rapidly deliver value to our customers”
CTO

3. Good news journey
Quadrupled our feature throughput
Shortened our delivery times by 87%
Improved team satisfaction
Metrics
Team empowerment
Tools

4. Just the facts Ma’am

5. Legacy code

6. Manual Build

7. Unpredictability

8. Distributed team

9. Real bug?

10. Late night deployments

11. Delivery Value Stream
Develop
3 Smoke 3 Smoke 1 Smoke
Functional Regression
1 3 0.3
Dev QA Staging Prod
Compile Assemble Package Assemble Package
Assemble Package Restore DB Apply DB Changes
Restore DB Apply DB Changes Deploy Package
Apply DB Changes Deploy Package
Deploy Package

13. Dude, where’s my new feature?

14. What we believe in
(and what we don’t)

15. Code quality
Before Current

16. Automated functional tests
173
160
146
# of Scenarios 132
110
79
56
21
0
S O N D J F M A M

17. Unit test coverage – new code
93 94 94
80 83
65 65 65
60
S O N D J F M A M
% Coverage

18. Code branches
5
2
1
Before Now Next

19. Deployment Duration
130
98
S O N D J F M

20. Cycle Time (Features and Defects)
30
9.8
S O N D J F M

21. Duration
11
87%
faster release
1
Delivery

22. How we did it

23. One team
Develop
3 Smoke 3 Smoke 1 Smoke
Functional Regression
1 3 0.3
Dev QA Staging Prod

24. Build a common vision

25. Common KPIs
Build Trust
Improve Comms

26. Empower the team to change things

27. Approach
• Close collaboration
• Incremental
• Data driven
• Automation
• Consensus base

28. Development Environment
Develop
3 Smoke 3 Smoke 1 Smoke
Functional Regression
1 3 0.3
Dev QA Staging Prod
3 days to set up environment 30 min to set up
Shared database Database change management
Shared environment Development sandbox
Manual build Automated builds
No continuous integration build

29. Evolution, not revolution
Manual Maven Buildr
No CI Hudson Go
Perforce Git

30. Code Quality
• Agreed on coding standards as a team
• Unit Test Code Coverage: Minimum Value 80%
• Cyclomatic Complexity <= 7
• Checkstyle
• JsLint
• Fail a build

31. Deployment
Develop
3 Smoke 3 Smoke 1 Smoke
Functional Regression
1 3 0.3
Dev QA Staging Prod
3 days to QA environment 30 min to each environment
20 page checklist Auto configuration management
1 day getting prod data to env 1 click deployment
Similar timeframes for stg/prod 1 click restore prod db
Frustrated QAs

32. Testing
Develop
3 Smoke 3 Smoke 1 Smoke
Functional Regression
1 3 0.3
Dev QA Staging Prod
4 days (4 QAs) 1 day (2 QAs)
Tedious regression Automated functional tests
Slow feedback cycle

33. Behaviour Driven Dev’t by empowered testers

35. Automated continuous delivery pipeline
Dev Version Build, Test & Automated QA Env & Staging Prod &
Team Control Assemble regression test Smoke test Smoke Test Smoke Test
check in
trigger
feedback trigger
feedback
one click
feedback
one click
feedback
one click
feedback

36. What did we learn?
• Automation, Automation, Automation
• Continuous feedback/improvement
• Takes longer to automate for Windows
• Put infrastructure configuration into version control
• Run automated smoke tests for each deployment

37. Change in value stream times
Develop
3 Smoke 3 Smoke 1 Smoke
Functional Regression
1 3 2 hrs
Dev QA Staging Prod
30 min 30 min 30 min
1 hr 7 hrs 1 hr

38. Duration
11
87%
faster release
1
Delivery

39. How you can do it

40. How do I sell this to my stakeholders?
Emphasise business benefits
– increased delivery predictability
– shorter time-to-market
– less rework
– lower risk
– lower application total cost of operation
Show them the metrics!

41. Where do I start?
Team: What’s the major pain point?
Automate manual processes
Measure stuff!
Use experts to accelerate adoption and reduce learning curve

42. We’re hiring...
@nishmahanty @lawrencesong
nish.mahanty@myob.com lawrence.song@myob.com