Before software as a service, computer programs were distributed on CD-ROMs and a new version came out every few years. Change was slow, and an upgrade was more akin to learning a new system than an incremental improvement.

Now, lots of software is provided over the internet, "as a service", available through a web browser. One key aspect of this that makes it better than the old way is the ability to change the software nearly instantly, just by deploying new code. Because this software is accessed through a web browser and doesn't require any installation, updating the code that runs on the server has the effect of upgrading all users to the newest version immediately.

Deploying more often should lead to more features and less bugs, which is great. But it's also harder to get right. In this talk I'll be going over some techniques that we use to plan incremental improvements and communicate them with customers and the rest of the team.