July 2024
Intermediate to advanced
446 pages
12h 37m
English
Content preview from Continuous Deployment
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 6. Slicing Upcoming Work
Part II of the book takes a closer look at how the full software life cycle is affected by continuous deployment. This chapter starts at the beginning of that life cycle, focusing on what happens prior to the coding work: the construction and maintenance of a product backlog that works with continuous deployment rather than against it.
The product backlog should be the source of truth for all of the upcoming work on a product, including its desired features, enhancements, and fixes. A well-structured backlog will not only facilitate frequent deployments and allow meaningful and early testing in production, but it will also leverage the speed and granularity of continuous deployment to support frequent experimentation.
Slicing work in a product backlog is essential when dealing with initiatives (epics) that are too long to fit into a single iteration. Subdividing epics into smaller, well-thought-out pieces allows for better visibility of progress as well as incremental delivery. In this chapter, I will discuss two different ways to slice epics, highlighting in particular the one that is more effective in combination with continuous deployment. Then, I will introduce an example feature and show how it can be split into increments that can be independently deployed and/or released. This example will be used throughout the rest of the book, so pay attention!
Let’s start with the theory.
Horizontal Versus Vertical Slicing
Most valuable features often ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.