Downloaded 53 times
![Testing Recommendations
• Automated Acceptance Tests
•
•
•
•
•
Fast Feedback
Reduce Tester workload
Testers can do Exploratory Testing
Regression Tests
Requirements can be generated from Tests
• Acceptance Test Approaches
• Acceptance Test Driven Development (ATDD)
• Behavior Driven Development (BDD)
Given [some precondition] When [some event] Then [some result]
35](https://image.slidesharecdn.com/cd101-2013-131126010954-phpapp01/85/ContinuousDelivery-101-35-320.jpg)
![Gamified development!
• Gamifying (Agile) Development –
• Stories, Narratives, Spikes
• Project initiation (iteration 0), technology discovery thru games
• Hackathons
• Gamify feature development [motivation, social, engaged, velocity, quality]
• Develop from Cradle to Grave – rewards for tdd, automation from dev to prod (making life easier,
process improvements)
• Progress, Rules and Social impact–
• TDD (rules), Kanban (visual), CI build monitors, Card Wall (visual)
• Socialize – Yammer, Project Dashboards, Leaderboard (Jenkins CI Game Plugin)
42](https://image.slidesharecdn.com/cd101-2013-131126010954-phpapp01/85/ContinuousDelivery-101-42-320.jpg)
Uploaded byKishore Bhatia
ContinuousDelivery-101
This document provides an overview and agenda for a webinar on continuous delivery in the enterprise. The webinar will define continuous delivery and differentiate it from continuous integration, Agile, quality and DevOps practices. It will explore the continuous delivery pipeline and key aspects like continuous development, integration and the ability to continuously release software. Attendees will learn about their role in continuous delivery and why it is important. The webinar will also discuss tools, products and solutions for continuous delivery and include case studies. It aims to explain how organizations can adopt continuous delivery practices.
More Related Content
Similar to ContinuousDelivery-101
ContinuousDelivery-101
- 1. Webinar Series ContinuousDelivery in the Enterprise Continuous Delivery 101
- 2.
- 3. Agenda • What isContinuous Delivery? • I thought I knew CI, Agile, Quality and DevOps! • Continuous development, integration and the ability to continuously release – The CD Pipeline • Key aspects and players • What’s my role in CD and why should I care? • Work, Gamified! • CD Tools, Products and Solutions out there! • Wrap-up: Case Studies, What’s Virtusa doing on CD? • Coming up next… 3
- 4. What is ContinuousDelivery?
- 5. The Big Question- What does it take to get a feature/hotfix/patch to your customer? • What’s involved in doing a release? • How long does it take? • How many steps are involved? • How successful is the process? • How often do you do them? • Do you have “heroes”? • What would happen if a particular environment disappeared/melted down? • Do your environments match? • How quickly can you build an environment? • How hard is it to do a patch? A major release? 5
- 6.
- 7.
- 8. Continuous Delivery • ContinuousDelivery is a software development discipline where you build software in such a way that the software can be released to production at any time. • Your software is deployable throughout its lifecycle • Your team prioritizes keeping the software deployable over working on new features • Anybody can get fast, automated feedback on the production readiness of their systems any time somebody makes a change to them • You can perform push-button deployments of any version of the software to any environment on demand Martin Fowler - http://martinfowler.com/bliki/ContinuousDelivery.html 8
- 9. I thought Iknew CI, Agile, Quality and DevOps!
- 10.
- 11. Audience Poll -1 Who drives Continuous integration and delivery in your project? •DEV •Operations 11
- 12. Audience Poll -2 On average how frequently are changes integrated into the release branch/trunk? (not the developer feature/promo/task branch, but the main code line from which a release candidate is built) •daily •weekly •with each sprint •only once feature development is complete 12
- 13. Audience Poll -3 What latent code strategies have you used within the last 12 months? •None...SCM feature branching •Hidden code •Abstraction •Feature toggles 13
- 14. Audience Poll -4 Merge problems? •None – We don’t do multiple releases and our single release process has minimal merges whatsoever •We don’t do multiple releases but our single release process has merge issues •Multiple releases – Merge issues •Automated Merge process using SCM Streams and CI automation 14
- 15. Quick Case Study Etsy(Online retailer): 22+ million members 800,000+ active shops 18+ million items currently for sale 400+ employees Business Problem - Our site is so successful, how can we move fast enough to keep up with feature demand? 15
- 16. We’re pretty Agile– Aren’t We? *Etsy Scenario 16
- 17. We’re developers andwe can solve any problem! 17
- 18. We own ourstuff from cradle to grave! 18
- 19. We can absorbchange with minimal impact! 19
- 20. We test ourcode – it always works in my local! 20
- 21. We don’t workon weekends! 21
- 22. We’re pretty Agile– Aren’t We? 22
- 23. Etsy - They’repretty Agile!!! 23
- 24. Etsy - ContinuousDeployment Math! • N = # of deploys • P = probability of site degradation • S = average severity of degradation • T = time to detect/resolve Expected Downtime = N*P*S*T 24
- 25. Etsy - Release!!! N= # of deploys S = avg. severity of degradation ED = Expected Downtime P = prob. of degradation T = time to detect/resolve Before CD N=1 P = 0.5 S = 0.7 T = 100 After CD N = 250 P = 0.1 S = 0.05 T=5 E.D = 35 E.D = 6.25 25 *Arbitrary Numbers
- 26.
- 27. Continuous development, integrationand the ability to continuously release – The CD Pipeline
- 28. Fundamental Prerequisites! 28 Agile ToolsIntegration, Aggressive Automation, Measurable continuous improvements
- 29. Design 3 inevitabilities wedesign for: • Things break, unexpectedly • What we’re building changes • We don’t get to start over 29
- 30. Architectural Principles Don’t betagainst the future. Our customers are humans. Simplicity always wins, in the end. Ambiguity kills momentum. Make failure cheap. Technical debt is an inevitable by-product of shipping code. Optimize for change. 30
- 31. Continuous Delivery Abstractmodel 31
- 32. Configuration Management Version Everything!!! •Single Identifier • Dependencies • App Configurations • Data • Environments 32
- 33. Continuous Integration (BuildPipeline) • • • • • • • • Check-in Daily Make Code Self Testing Commit to Trunk Automate the Build Keep the Build Fast Every Commit results in Build/Validate Test in Clone of Production Automate Deployments 33
- 34.
- 35. Testing Recommendations • AutomatedAcceptance Tests • • • • • Fast Feedback Reduce Tester workload Testers can do Exploratory Testing Regression Tests Requirements can be generated from Tests • Acceptance Test Approaches • Acceptance Test Driven Development (ATDD) • Behavior Driven Development (BDD) Given [some precondition] When [some event] Then [some result] 35
- 36.
- 37.
- 38.
- 39. What’s next forAgile? 2001-2012 2012 onwards… Continuous Integration, delivery, design, feedback Continuous play Courtesy – Thoughtworks 39
- 40. So, what isGamification? Gamification is integrating game thinking and design into activities to increase engagement, learning and fun. 40
- 41.
- 42. Gamified development! • Gamifying(Agile) Development – • Stories, Narratives, Spikes • Project initiation (iteration 0), technology discovery thru games • Hackathons • Gamify feature development [motivation, social, engaged, velocity, quality] • Develop from Cradle to Grave – rewards for tdd, automation from dev to prod (making life easier, process improvements) • Progress, Rules and Social impact– • TDD (rules), Kanban (visual), CI build monitors, Card Wall (visual) • Socialize – Yammer, Project Dashboards, Leaderboard (Jenkins CI Game Plugin) 42
- 43. Metrics and Rewards! •An integrated view of the development efficiency can be derived from usual metrics all along • SVN Metrics • JIRA Metrics • Code review metrics • CI Metrics • Deployment Metrics • Automated unit/acceptance test metrics • Is there a tool (or a set of tools integrated) that pulls out and then co-relates this information to derive meaningful metrics? 43
- 44. How developers are paid– Virtual Currency 44 Courtesy - Web
- 45. Metrics and Rewards… Description RewardPoints Check-in and build passes (with unit tests) 1 One or more unit tests failed -10 Compiler error (come on now) -20 Big check-in caused build to remain in a broken state for hours -40 Code review (complexity, re-use, leaks, copypaste) -40 OthersJIRA metrics Stack Exchange like metrics (Forums, QnA, tech discovery) Continuous Improvement metrics (e.g. Maven build – time, accuracy, adherence to standards, Deployment Engine metrics) Jenkins - https://wiki.jenkins-ci.org/display/JENKINS/The+Continuous+Integration+Game+plugin 45
- 46. CD Tools, Productsand Solutions out there!
- 47. CD Tools Matrix(Continuously evolving) Version Control (SCM) Dependency Mgmt DB mgmt Infrastructure Mgmt CI Build Automation Test Deployment Automation ALM Subversion Nexus Liquibase Puppet Hudson Maven Junit/jMock /Mockito/D bunit XebiaLabs – Deployit Jira Git Artifactory Flyway Chef Jenkins Ant Selenium/W ebdriver uDeploy (IBM UrbanCode) Bugzilla Mercurial Bamboo Gradle infinitest ElectricCloud – Electric Commander QC Accurev Teamcity Buildr Fitnesse RebelLabs – LiveRebel Go Jbehave/Cuc umber 47
- 48.
- 49.
- 50.
Editor's Notes
- #6 “Software development providers can’t deliver new services at the rate business leaders want” - Forrester Consulting “Continuous Delivery: A Maturity Assessment Model”, March 2013
- #7 Key Pain Points: Painful releasesInability to predict delivery affecting business commitments Deployment to environmentsCode quality Environment configuration & management Expensive, time consuming manual QA (unable to build lab) -Partial Agile implementation (Scrum but no technical processes)
- #9 “Software development providers can’t deliver new services at the rate business leaders want” - Forrester Consulting “Continuous Delivery: A Maturity Assessment Model”, March 2013 Delivery vs. Release •Delivery: integrated, passing all stages of pipeline validation •Release: accessible by customers and market •Deliver continuously, release when business decides •Requires latent code strategy (inherently latent code, abstraction, feature toggles, etc.)
- #18 “Software development providers can’t deliver new services at the rate business leaders want” - Forrester Consulting “Continuous Delivery: A Maturity Assessment Model”, March 2013
- #19 Throwing Code off the wall - QA testing and Deployment
- #20 “Software development providers can’t deliver new services at the rate business leaders want” - Forrester Consulting “Continuous Delivery: A Maturity Assessment Model”, March 2013
- #21 “Software development providers can’t deliver new services at the rate business leaders want” - Forrester Consulting “Continuous Delivery: A Maturity Assessment Model”, March 2013
- #22 “Software development providers can’t deliver new services at the rate business leaders want” - Forrester Consulting “Continuous Delivery: A Maturity Assessment Model”, March 2013
- #23 “Software development providers can’t deliver new services at the rate business leaders want” - Forrester Consulting “Continuous Delivery: A Maturity Assessment Model”, March 2013
- #27 Discuss – CIAgileQualityDevOps
- #31 Complex systems and change Distributed systems are inherently complex. The outcome of change in complex systems is hard to predict.The outcome of small, frequent, measurable changes are easier to predict, easier to recover from, and promote learning
- #32 CD is more difficult to achieve in large, enterprise organizations due to unique challenges; some of them are – - Scale of parallel activity- Complexity of software and environment - Variance in skills/experience of teams/individuals across the organization - Variance in the ability to integrate “work in progress” across the organization - Often no CI across team boundaries
- #34 Best Practices - Extreme Programming (XP)Fail a Build for Design BreachesFail a Build for Slow TestsFail a Build for Warnings & Code Style BreachesBuild Pipeline Practices –Build Once, Deploy ManyDeploy the Same Way to All EnvironmentsSmoke Test your DeploymentsDeploy into a Copy of ProductionEach Change should Propagate InstantlyIf any part fails, Stop the line
- #37 Use Appropriate Technology – In-House Vs. External Deployment automation productsApp deployment - Scripting Approaches Jenkins driven deployment Script logs (ssh) into each box and runs deployment commands Script runs locally, each remote machine has deployment agent to execute script Package app using platform’s packaging technology (rpm, gems) and use infrastructure management tools to push new versions App syncs-up with an online store and automatically pulls latest updates (artifacts, db, properties)Database DeploymentsVersion your DatabaseEvolve Your Database Incrementally41Environment ManagementVersion your Application ConfigurationVersion your Operating System42
- #38 CD is more difficult to achieve in large, enterprise organizations due to unique challenges; some of them are – - Scale of parallel activity- Complexity of software and environment - Variance in skills/experience of teams/individuals across the organization - Variance in the ability to integrate “work in progress” across the organization - Often no CI across team boundaries
- #41 Why should we gamify work? Adapt work for incoming, younger workforce Intrinsic rewards are renewable resource Develop leadership in teams More-satisfying work = better productivity Develops people by pointing them forward to clear goals Fosters teamwork and accountability Key to greater innovation (through imagination)
- #43 Dangers- You can’t just spawn a new project after failing Could depersonalize rather than personalize No one game can please all Gaming and misuse of metricsApproach-Take an agile approach (Increment, Iterate, Improve) Focus on the intrinsic first (extrinsic will come) Voluntary participation Give control and teams design their own games (and fail) Lightweight, both in implementation and tone (i.e., fun)
- #45 The Development Game
- #46 Jenkins CI Game Plugin –-10 points for breaking a build0 points for breaking a build that already was broken+1 points for doing a build with no failures (unstable builds gives no points)-1 points for each new test failures+1 points for each new test that passeshttp://www.badgeville.com/products/gamificationhttp://www.redcrittertracker.com/