How to release every week? Case study of Continuous Integration from VNDirect
1 like673 views
The document outlines an approach for releasing software weekly despite working with a legacy system. It recommends fully covering tests, adding features incrementally, and avoiding big bang deployments. Current statistics show 70% unit test coverage, 1500 acceptance tests, resolving technical debt within 5 days, and no critical issues. Challenges include difficulty testing legacy code, conflicts with vendors, and coordination issues with pairing and mob programming.
1 of 17
Download to read offline
More Related Content
What's hot (12)
Ad
Viewers also liked (19)
Ad
More from Đới Học viện Agile (13)
How to release every week? Case study of Continuous Integration from VNDirect
- 1. How to release everyweek With legacy system
- 2. HUNG HOANG Tech Lead CHAU HOANG Agile Coach
- 4. XP
- 5. LEGACY SYSTEM Where it all began
- 7. Image courtesy of The-Challenge.org
- 8. CODE Partially owned TEST Must be fully covered FEATURES Adding as you go DEPLOYMENT Big Bang Forbidden
- 9. Approach
- 10. How things are stored
- 11. Workflow User Stories Tasks Development Deploy Staging/ProductionPackage Repo Repo
- 12. Testing via RF
- 13. Current Stats 70% UNIT TEST COVERAGE 1500 ACCEPTANCE TESTS 5days DELTA TECHNICAL DEBTS 0 CRITICAL ISSUES
- 14. Issues • TDD as you wish • Legacy acceptance tests • Difficult test setup • Conflict with vendor • Pair/trio/mob mess
- 15. Robot Framework
- 16. WE’RE HIRING
- 17. Q&A