+ All Categories
Home > Technology > Software G Forces

Software G Forces

Date post: 05-Dec-2014
Category:
Upload: kentbeck
View: 9,256 times
Download: 0 times
Share this document with a friend
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.
13
Software G Forces: The Effects of Acceleration Kent Beck Three Rivers Institute
Transcript
Page 1: Software G Forces

Software G Forces:The Effects of Acceleration

Kent BeckThree Rivers Institute

Page 2: Software G Forces

Deployment: 1990

Annual Quarterly Monthly DailyWeekly Hourly

Page 3: Software G Forces

Deployment: 2010

Annual Quarterly Monthly DailyWeekly Hourly

Page 4: Software G Forces

Deployment: 2030

Annual Quarterly Monthly DailyWeekly Hourly

Page 5: Software G Forces

Relativity

Page 6: Software G Forces

Annual to Quarterly

+ Automated acceptance tests

+ Refactoring+ Continuous

integration+ Subscription

Page 7: Software G Forces

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

Page 8: Software G Forces

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

Page 9: Software G Forces

Weekly to Daily

+ Immunization+ A/B testing

- Staging- Operations team- Stand-up meetings

Page 10: Software G Forces

Test the waters

Page 11: Software G Forces

Nemawashi

• Remove all impediments to a faster deployment cycle

Page 12: Software G Forces

Visibility

Page 13: Software G Forces

Questions?


Recommended