o Save
lots of time, test quickly
o Confidence
in testing environment, focus on features
o You
also gain confidence in the deployment tool, which allows you to deploy more
often, and faster.
·
Small Release, More Often Release
o Integrate
customer feedback into bug fixing
o Drive
better customer experience
o Drive
cost-per-release down
o Release
often. How often? One release every month/week/day ?
·
"One week" worked for some web sites.
·
In reality, this should simply be as low as is
practical and useful for the business needs of the group.
·
We found that the lower we could get this, the
more flexibility we had in getting changes out to prod quickly and reliably,
getting better customer experiences faster.
·
In particular, get really fast at verifying that
things that haven't changed aren't broken.
·
This will really help with testing things like
adopting new versions of the SDK.
o More-often-and-quicker
release is enabled by
·
Good auto-deployment tools.
·
Well documented deployment and troubleshooting
processes.
