Outcome-Based Development With Bryan Finster
Dev Interrupted on DZone features 5-minute DevOps author Bryan Finster answering my question about outcome-based development.
Join the DZone community and get the full member experience.
Join For Free"A developer is a business expert who solves problems with code." Bryan Finster
Continuous Delivery isn’t about how fast you can deliver, it’s about the outcome your delivery achieves. On our first episode of the new year I talk with Bryan Finster, author of 5-minute DevOps, about outcome-based development and why failing small is better than failing fast.
Bryan has been helping dev teams improve the processes they use to develop and deliver software for decades. He brought all of that experience to this episode of the Dev Interrupted podcast to help answer:
- What is Outcome-based Development?
- What is the true goal of Continuous Delivery?
- Why failing small is better than failing fast.
- The most common pitfalls dev teams find when trying to optimizing their delivery process.
Did we just have the best live AMA ever?
The Dev Interrupted discord community hosts weekly AMA's with industry experts every Friday. Join our community of dev leaders free here: https://discord.gg/tpkmwM6c3g
Interested in Improving Your Dev Team?
Check out the Engineering Manager's Runbook for Team-based Metrics
Topics:
continuous delivery,
devops,
leadership,
agile metrics
Published at DZone with permission of Dan Lines, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments