We’ll Finish That Later
You have a done product increment that you could potentially release, but it requires some manual intervention to release it into production. The remaining undone work will perhaps take another day or two or three to complete.
This situation often leads to teams doing the remaining work at the end of the sprint or creating a sprint specifically for completing that work. When that happens, feedback loops and cycles get way too large. You can’t release this untested, unchecked software to production. Without a release, you aren’t getting feedback, which means you can’t validate the value of your product. Similarly, the further you move away from the partially completed work, the harder it is to switch contexts, hop back ...
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