Just Deploy It
Download as PPTX, PDF0 likes806 views
The document discusses the challenges and delays in software deployment, emphasizing the need to avoid lengthy release plans and 'big bang' deployments. It suggests prioritizing minimal features and essential functionalities for quicker launches, as well as reducing the focus on non-critical elements like logins and extensive load testing. The overall goal is to streamline the deployment process and improve efficiency.
Just Deploy It
- 2. Have you deployed anything today? DEPLOY
- 3. We’ve come a long ways…
- 4. … but we are still taking too long to deploy JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC
- 5. What is holding you back from launching right now ?
- 6. #1 – Avoid Release Plans
- 7. #1 – Avoid Release Plans Test Code Release Every 2 weeks
- 8. Instead… Feature Feature Ready Highest Priority to build Feature Ready to deploy Feature Feature Feature Feature Feature Feature
- 9. #2 – Avoid Big Bang Deployments “Big release” Feature B Feature A Design Bug fix Change Pricing Feature C Change meh. Which was the cause?
- 10. Instead… Define Test the Measure Biz Test Code it! code Deploy! results Learn!
- 11. #3 – Logins are low priority Too-Typical Developer: “Great! First I’m going to setup our user types, an administration site, and this cool security framework…”
- 12. #3 – Logins are low priority PWN3D!!!
- 13. Instead… 1. Most important features/assumptions 2. Minimal security necessary 3. Lots of other more important things… 4. … then pretty admin sites
- 14. #4 – Delay Load Testing
- 15. #4 – Delay Load Testing epic fail.
- 16. Wait for benefits to outweigh the costs
- 17. #5 – Kill the Betas
- 18. Instead…
Editor's Notes
- #2: I’m Arin Sime and I’m a software developer with a few things on my mind. I’d like to share with you some antipatterns that I see too much in startups.20 slides, 15 seconds each
- #3: How many of you deployed something today? How many of your teams deployed something last week, or will deploy something tomorrow? If you are like most people I meet the answer is you are not deploying often enough.
- #4: We’ve come a long way from the bad old days of shrink wrapped software that you release annually on a big waterfall cycle with lots of process.Photopurchased from Fotolia, © Sarunyu_foto - Fotolia.com
- #5: But we are still taking too long to deploy. Many companies still use the same processes and mindsets as they did with annual releases, it’s just now they do mini waterfalls every month.
- #6: So this is the key question that I have for you: What is holding you back from launching your business or that new feature right now? I’m going to share with you 5 tips to avoid taking too long to release.
- #7: The first tip is If you have a plan for what you are going to release in the first quarter of next year, then you are wasting time. That is too far into the future for a startup to have any detailed release plans.
- #8: Now I love agile methods like Scrum, and I use them all the time. But scrum teaches us to work in 2 week cycles, and often times people then start thinking of multi-sprint release cycles. That is for big companies using Scrum, not you as a startup.
- #9: Instead,focus on a strongly prioritized backlog.Don’t plan for items more than 2 weeks ahead and just build and deploy each feature, one at a time. Just deploy it!
- #10: Tip 2: If you group together new features, bug fixes, and design changes into big releases, and you don’t get the user reaction you wanted, how do you knowwhich change resulted in positive or negative behavior? Who knows!
- #11: Instead, make sure to release code one feature at a time.Think about how you can test that feature and build that test into the code, then Just deploy it … and measure it!
- #12: How often have your development teams started with boring stuff like logins and frameworks? When I see the demo of a project’s first sprint, and it’s just a login page, it makes me cry a little bit inside.
- #13: Now you might be saying, but I’ll get hacked! You might, but I’m not saying you should post a list credit card numbers on your site, at least not without a login around them! But there is plenty you can test before you put in fancy security.
- #14: Instead start with a more important feature or risky assumption, and add in the security and pretty admin site later. Forget about logins and just deploy it!
- #15: Tip 4 is to ignore load testing for now. We all imagine this is what will happen the day we launch, but that’s highly unlikely. Sorry to break the bad news!
- #16: The only time that day 1 onslaught may happen is if you are timing your “big bang release” with a big bang media blitz. But that’s never a good idea.Image © sahuad - Fotolia.com
- #17: Instead, wait to load test until you are sure the feature is worth the costs of tools and most importantly your time. Drop the load test FOR NOW and just deploy it!
- #18: Finally, I really don’t like the term beta. I’m trying to cut it out of my vocabulary all together, and Google is not helping me. Betas imply a big bang release, delayed validation, and big costs.
- #19: We are all in beta constantly.We should be constantly testing our assumptions, and sneaking out new features for individual feedback. So kill the beta and Just deploy it!Graphic based on © vinz89 - Fotolia.com
- #20: In summary, I want you to do less than you are now. Do a whole lot less AT A TIME and then release value more often.
- #21: Everybody say it with me … Just Deploy it! Thank you!