Software G Forces

Post on 05-Dec-2014

9.256 views 0 download

description

What happens to software development when deployment frequency increases? Some of the practices that make good sense with annual deployments are fatal with daily deployments and vice versa.

Transcript of Software G Forces

Software G Forces:The Effects of Acceleration

Kent BeckThree Rivers Institute

Deployment: 1990

Annual Quarterly Monthly DailyWeekly Hourly

Deployment: 2010

Annual Quarterly Monthly DailyWeekly Hourly

Deployment: 2030

Annual Quarterly Monthly DailyWeekly Hourly

Relativity

Annual to Quarterly

+ Automated acceptance tests

+ Refactoring+ Continuous

integration+ Subscription

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

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

Weekly to Daily

+ Immunization+ A/B testing

- Staging- Operations team- Stand-up meetings

Test the waters

Nemawashi

• Remove all impediments to a faster deployment cycle

Visibility

Questions?