+ Follow

Continuous Deployment: Startup Lessons Learned

by ashmaurya on Apr 24, 2010

8,136 views

More…

Less

20 Embeds 1,024

http://www.ashmaurya.com	309
http://aceleradora.net	231
http://www.manualdastartup.com.br	208
http://www.slideshare.net	72
http://gerentedeprodutos.com.br	53
http://www.gerentedeprodutos.com.br	50
http://madebymany.com	24
http://gerentedeprodutos.blogspot.com	23
http://devgiant.net	12
http://dius-staging.dius.com.au	9
http://static.slidesharecdn.com	7
http://dius.com.au	7
http://locawebianos.com.br	6
http://diuscomputing.com.au	4
http://www.locawebers.com.br	3
http://www.shareyolink.com	2
http://translate.googleusercontent.com	1
http://webcache.googleusercontent.com	1
http://blogs.msdn.com	1
http://feeds.feedburner.com	1

More...

Statistics

Favorites: 32
Downloads: 354
Comments: 2
Embed Views: 1,024
Views on SlideShare: 7,112
Total Views: 8,136

Continuous Deployment: Startup Lessons Learned — Presentation Transcript

Continuous Deployment Case-study: WiredReach COMMIT DEV MONITOR TEST RELEASE QA DEPLOY Ash Maurya @ashmaurya http://www.ashmaurya.com

How do you maximize progress in a Lean Startup?

By maximizing validated learning about customers.

Requirements Development QA Release

Some learning Requirements Development QA Release

Most learning happens Some learning here Requirements Development QA Release

Most learning happens Some learning here Requirements Development QA Release Very little learning

Product Development gets in the way of learning about customers.

Most learning happens Some learning here Requirements Development QA Release Very little learning

Most learning happens Some learning here Requirements Release

Most learning happens Some learning here Continuous Requirements Release Deployment Shortens cycle time

1. Before and After 2. How we got started 3. How we build features

About WiredReach Dead-Simple Sharing Software BoxCloud The simple way to share ﬁles with clients and coworkers. CloudFire Photo and Video Sharing for Busy Parents and Photographers.

Before After COMMIT DEV MONITOR TEST RELEASE QA DEPLOY 2 week release cycles Multiple releases a day

Before After PRODUCTION PRODUCTION CERTIFICATION SANDBOXES Staging area Standalone sandboxes

Before After COMMIT DEV MONITOR TEST RELEASE QA DEPLOY Releases were all day events Releases are non-events

Before After COMMIT DEV MONITOR TEST RELEASE QA DEPLOY Release size: Release size: hundreds of lines of code < 25 lines of code

Before After COMMIT DEV MONITOR TEST RELEASE QA DEPLOY More emergency releases Less firefighting

Before After COMMIT DEV MONITOR TEST RELEASE QA DEPLOY Coding days versus Coding days AND Customer days Customer days

Continuous Deployment sounds great, but...

Taking the plunge is scary as hell

Requirements Development QA Release

$ Requirements Development QA Release

$ Requirements Development QA Release Very little learning

$ Automated Requirements Development QA QA Release Very little learning

$ Automated Requirements Development QA QA Release Production Very little learning Monitoring

1. Before and After 2. How we got started 3. How we build features

Code in small batch sizes

Deploy manually at ﬁrst, then automate.

Always test the User Activation ﬂow

Watch the release cycle time COMMIT MONITOR TEST DEPLOY Less than 30 minutes

Be ready to stop the production line

Build a cluster immune system. Incrementally. Build a cluster immune system. Incrementally.

Challenges: Downloadable software

1. Before and After 2. How we got started 3. How we build features

Don’t be a feature pusher NEW FEATURES 20% CONTINUOUS RELEASE 80% EXISTING FEATURES

Constrain the features pipeline Validated Backlog In-Progress Done Learning Was this feature any good?

Closing the loop with validated learning Qualitative Quantitative Start here Verify with data

When is the right time to start ? There is no better time than the present.

Thanks! Ash Maurya twitter: ashmaurya blog: http://www.ashmaurya.com Getting Lean - the book How to iterate your web application to product/market ﬁt http://www.wiredreach.com/gettinglean.html

Thomas Lidforss , Managing Partner at Thomas Lidforss International Great presentation making it easy for people who do not understand agile development processes to get the point and the value. 1 year ago

Are you sure you want to Yes No

Walter Adamson , Principal - Melbourne at iGo2 Group Great lessons for SaaS providers as well.
Walter @g2m
http://xeesm.com/walter 2 years ago

Continuous Deployment: Startup Lessons Learned

by ashmaurya on Apr 24, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

20 Embeds 1,024

Statistics

Continuous Deployment: Startup Lessons Learned — Presentation Transcript