Software G Forces
Download as PPT, PDF15 likes4,485 views
The document discusses how software deployment timeframes have decreased from annual to hourly and the effects of accelerating deployment cycles on software development practices and teams. Faster deployment requires more automated testing, refactoring, continuous integration, shorter-lived feature branches, less upfront documentation and design, just-in-time usability testing, and removing impediments to faster cycles. Teams adapt through practices like stand-up meetings, kanban, dedicated QA roles, temporary feature branches, and an emphasis on releasing minimum viable products.
1 of 13
Downloaded 106 times
Software G Forces
- 1. Software G Forces: The Effects of Acceleration Kent Beck Three Rivers Institute
- 2. Deployment: 1990 Annual Quarterly Monthly Daily Weekly Hourly
- 3. Deployment: 2010 Annual Quarterly Monthly Daily Weekly Hourly
- 4. Deployment: 2030 Annual Quarterly Monthly Daily Weekly Hourly
- 5. Relativity
- 6. Annual to Quarterly Automated acceptance tests Refactoring Continuous integration Subscription
- 7. Quarterly to Monthly Developer testing Stand-up meetings Cards on a wall Pay per use Q/A department Multiple deployed versions Design document Change requests Analysis team Build team
- 8. Monthly to Weekly Live, 2-way data migration Defect zero Temporary branches Keystoning Kanban Bootstrap financing Test team One-way data migration Release branch Patches Up-front usability design Venture capital
- 9. Weekly to Daily Immunization A/B testing Staging Operations team Stand-up meetings
- 10. Test the waters
- 11. Nemawashi Remove all impediments to a faster deployment cycle
- 12. Visibility
- 13. Questions?