Build a Continuous Delivery Practice One Brick at a Time: Techniques for Introducing Continuous Delivery Practices on Your Current Project
Have you heard a lot of discussion about Continuous Delivery and are wondering how to introduce these practices to your current project? Are you starting to feel like Continuous Delivery is a practice that'll have to wait until you start your next project?
Continuous Delivery is a broad concept which can be broken down into lots of smaller chunks. If Continuous Delivery is a brick wall, then the practices (Delivery Pipeline, Continuous Integration, Automated Deploy, Continuous Deployment) make up the individual blocks. And the secret to success is that you don't have to build the entire wall in one sitting.
In this talk, we'll explore this metaphor by examining one of the most fundamental "bricks" that teams can start with, automated deployments, and how organizations can introduce this one brick on their current projects. No need to wait for the next project; your team can use better practices now.
Outline/structure of the Session
- What is Continuous Delivery?
- a delivery practice that insists on continuous improvement and strives for ever shorter feedback loops
- What practices fall under the umbrella of Continuous Delivery (the bricks)?
- continuous delivery
- continuous integration
- automated testing
- automated deployment
- delivery pipeline
- infrastructure automation (DevOps)
- Get Started Now
- you don't have to wait for your next project to follow these practices
- Insist on continuous improvement
- Retrospectives that are focused on delivery
- Map out your feedback loops
- be sure to look for hidden feedback loops
- keep your eyes open; you'll likely uncover more later
- The first step in improving anything is taking an honest assessment of where you are now
- The Best Starting Point: Automate your deployment process
- Don't have a test suite? That's okay. You can still have an automated deployment, you'll just have to test it manually.
- Goals of deployment automation
- resilience - a failure during the deployment needs to not leave your system in an unusable state
- recoverable - make sure you can roll back
- availability - empower any member of your team to perform a deployment
- push button - keep it really simple - a single button (or command with no parameters) is the goal
- Rolling it out
- Create (or use) a production-like environment - use this environment as the test bed for the automation
- It's okay to run through a few deployment cycles before you roll this practice out to production
- What's next?
- let your retrospectives guide the process
Attendees will walk away knowing how to confidently start implementing continuous delivery practices on their current projects. Attendees will also have a very good guide for introducing automated deployment practices on their current projects.
Developers, Product Owners, Scrum Masters
schedule Submitted 11 months ago
People who liked this proposal, also liked:
Vulnerability: The Key To Successful Agile AdoptionAndrea Goulet
schedule 1 year agoSold Out!
Software development culture has been dominated by the hero. Rock stars, ninjas, and 10Xers have been the center of attention, giving the skewed perception that great software is the result of a single amazing developer. But this couldn't be further from the truth.
In this talk, Andrea Goulet, the CEO of Corgibytes, will share her experiences using vulnerability and empathy as drivers for Agile adoption and culture building.