Your SlideShare is downloading. ×
Software G Forces
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Software G Forces

7,877
views

Published on

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.

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.

Published in: Technology, Business

1 Comment
11 Likes
Statistics
Notes
No Downloads
Views
Total Views
7,877
On Slideshare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
93
Comments
1
Likes
11
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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?