4 months to 1 day sans buzzwords -Devops Days - India 2013

http://devopsdays.org/events/2013-india/program/

Talk about frequent releases in software devlopment. The 'why', 'why not' and 'how' with the "Theroy of constraints" premise.
By -
@pavanks - Pavan KS
@anandhak - Anandha Krishnan

Mavenhive - www.mavenhive.in

Transcript

1. We will be talking about frequent releases
2. Sample workflow to help go fast
3. Activities that help go fast rapid, reliable releases traceability visibility SCM continuous integration release candidates deployment mechanism and strategy parallelization environments configuration management value stream map components dependency management metrics charts trends faster reduce cycle time smoke tests functional tests load tests exploratory tests user acceptance …..… role separation audit trail binaries artifact repository continuous delivery build and deployment process collaboration unit tests code metrics pretty good build one-click production deployment path to production rollbacks
4. And some tools
5. Buzzword alert!
6. 4 Months to 1 Day Pavan Sudarshan @pavanks Anandha Krishnan @anandhak (Jake) Sans Buzzwords
7. Assumptions → You have software that has been deployed to prod → Your software is under active development → You have put at least one working software to production
8. What is in it for me? → Why should software be released often? → Why not? → How frequently? → How do we release faster?
9. Frequent everything! instead… Lets do Q&A frequently Usually, speakers talk Q & A gets “taken offline”
10. So, what’s wrong with buzzwords? Every buzzword inherently sounds important. It seems like something that you absolutely need.
11. So, what’s wrong with buzzwords? → Focus on solutions, not problems → Tend to be much more than “Just Enough”
12. So, lets stop looking at solutions and start looking at the problems instead
13. Frequent releases... Why should anyone even do it? PS: Lets not just say - For “fast feedback” :)
14. Lets take a step back
15. Why frequent releases? → Learn what your customers “actually want” → Always develop using signed off inventory → Integration is no longer an event → Customers might enjoy constant updates
16. → Does anyone even care? → Customer doesn’t know what will work → Automation is pricey. Build more features? → Something very small and simple? Why not? When not!
17. How Frequent is “Frequent”? → Driven purely based on business goals → 4 months might be just as good as 2 days → Let it evolve. It can change over the life cycle of the project. → Do what makes sense! (Seriously)
18. How to go faster... tldr; Theory of Constraints
19. How to go faster... → Critical Chain → Fail fast, learn fast → Less becomes more → Enough is enough → Production - Holier than thou?
20. How to go faster... → Critical Chain → Fail fast, learn fast → Less becomes more → Enough is enough → Production - Holier than thou?
21. Critical Chain → Helps identify bottlenecks → Time taken for a line of code to go to prod → Assumption: Only one way to deploy to prod ◦ Makes optimizing straightforward → Workflow leading up to prod itself could be complex
22. How to go faster... → Critical Chain → Fail fast, learn fast → Less becomes more → Enough is enough → Production - Holier than thou?
23. → Failure is great! It tells you what not to do. ◦ A bug in prod, failed smoke build, customer asking you to change a feature etc. are all good → Don’t add gates, add checks → Build promotion is a good metaphor → http://www.youtube.com/watch? v=Fpmse9PpDZE Fail fast, learn fast
24. → Critical Chain → Fail fast, learn fast → Less becomes more → Enough is enough → Production - Holier than thou? How to go faster...
25. Less becomes more 3 months of work 3 iterations of 2 weeks each
26. Less becomes more → Fast != Burn out → Breaking down work into pieces is vital → More the number of iterations, finer the feedback → Its all about course correction quickly
27. How to go faster... → Critical Chain → Fail fast, learn fast → Less becomes more → Enough is enough → Production - Holier than thou?
28. Enough is enough → Enough in the eye of the stakeholder → As a kid, how long did you take to clean your room? ◦ 40 minutes? ◦ 2 hours? ◦ A whole day?
29. This is how Mark did it - True Story* “My strategy was to do just enough work and then pull my mom in so she could pass or fail my room’s tidiness” - Mark Chang, Friend (http://www.thoughtworks.com/insights/blog/fail-fast-learn-fast) (*) Barney Stinson, HIMYM
30. How to go faster... → Critical Chain → Fail fast, learn fast → Less becomes more → Enough is enough → Production - Holier than thou?
31. Production - Holier than thou? → Most Customers don’t care about prod issues. ◦ They care more about turn around on fixing issues → Adding gates to prevent issues from creeping into prod is not smart ◦ There are many more issues hiding, you just don’t know them → Audit, don’t restrict. Avoid bottlenecks → Respect, not fear!
32. Recap... → Critical Chain → Fail fast, learn fast → Less becomes more → Enough is enough → Production - Holier than thou?
33. We don’t know about you, but... We are starving. Lets go eat.