50 min
Build Better Products Faster by Embracing Continuous Delivery (with Dave Farley, Consultant & Co-author of ”Continuous Delivery”) One Knight in Product
-
- Business
Dave Farley is a consultant and renowned thought leader in the software development world, and a strong advocate for ensuring that our software is always releasable. He's co-authored a book and runs a popular YouTube channel, both called "Continuous Delivery". We spoke about what continuous delivery is, why it's important, the barriers to implementing it, and how product managers can help.
Episode highlights:
1. Continuous delivery is what the best software organisations in the world do
It's unambiguous. It's backed by data. It's the best way to build quality products. Applying these techniques means your software is always releasable, and every change is safe
2. But, this doesn't mean you need genius developers
Any team can adopt continuous delivery. It's not a factor of 10x "rock star" developers, but empowered teams of developers working together, collaborating and *talking* to each other.
3. You build quality software by going fast
Continuous feedback based on small changes, constantly validated, ensures high-quality products. You don't want to go back & fix it later. You can't inspect quality into a system at the end of a development cycle. Build it in upfront.
4. Just because you can release continuously doesn't mean you have to
What you release to customers is a business decision. This isn't about throwing half-finished features at users but having software that you know works. You can use feature flags to manage availability.
5. Many product managers need to check themselves
We need to move away from PMs giving developers human-language representations of code and telling them to convert it for a computer. The best devs are problem solvers and should be involved in working out the best solution.
Buy "Continuous Delivery"
"Getting software released to users is often a painful, risky, and time-consuming process.This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours―sometimes even minutes–no matter what the size of a project or the complexity of its code base."
Check it out on Amazon.
Check out Dave's course
Dave has a course out that helps people get good at all the stuff we talked about in the podcast. If you're interested, check the course out here.
Dave also mentioned a talk by his co-author Jez Humble. I'm not 100% sure if this is the one, but it looks pretty good anyway. Check it out.
Contact Dave
You can connect with Dave on Twitter. You can also check out the Continuous Delivery YouTube channel.
Dave Farley is a consultant and renowned thought leader in the software development world, and a strong advocate for ensuring that our software is always releasable. He's co-authored a book and runs a popular YouTube channel, both called "Continuous Delivery". We spoke about what continuous delivery is, why it's important, the barriers to implementing it, and how product managers can help.
Episode highlights:
1. Continuous delivery is what the best software organisations in the world do
It's unambiguous. It's backed by data. It's the best way to build quality products. Applying these techniques means your software is always releasable, and every change is safe
2. But, this doesn't mean you need genius developers
Any team can adopt continuous delivery. It's not a factor of 10x "rock star" developers, but empowered teams of developers working together, collaborating and *talking* to each other.
3. You build quality software by going fast
Continuous feedback based on small changes, constantly validated, ensures high-quality products. You don't want to go back & fix it later. You can't inspect quality into a system at the end of a development cycle. Build it in upfront.
4. Just because you can release continuously doesn't mean you have to
What you release to customers is a business decision. This isn't about throwing half-finished features at users but having software that you know works. You can use feature flags to manage availability.
5. Many product managers need to check themselves
We need to move away from PMs giving developers human-language representations of code and telling them to convert it for a computer. The best devs are problem solvers and should be involved in working out the best solution.
Buy "Continuous Delivery"
"Getting software released to users is often a painful, risky, and time-consuming process.This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours―sometimes even minutes–no matter what the size of a project or the complexity of its code base."
Check it out on Amazon.
Check out Dave's course
Dave has a course out that helps people get good at all the stuff we talked about in the podcast. If you're interested, check the course out here.
Dave also mentioned a talk by his co-author Jez Humble. I'm not 100% sure if this is the one, but it looks pretty good anyway. Check it out.
Contact Dave
You can connect with Dave on Twitter. You can also check out the Continuous Delivery YouTube channel.
50 min