ArticleFinish lineReleaseFlow
Nothing floats: how to spot work with no finish line
· Ever Release
Floating work is any unit of work with no clear line back to why the product exists, what release it serves, or which outcomes it advances. In ReleaseFlow, nothing floats - every item traces to the finish line or it is triage.
Floating work is any unit of work with no clear line back to why the product exists, what release it serves, or which outcomes it advances. In ReleaseFlow, nothing floats - every item traces to the finish line or it is triage.
How do you spot floating work?
- No one can say which product goal it serves
- It entered the backlog because someone asked, not because the finish line required it
- It looks “important” but never appears on the critical path
- Stopping it would not change the release outcome - and starting it does not either
What do you do when work floats?
Do not pretend it is progress. Triage it against the product goal. If it does not serve the finish line, it does not enter the critical path as must-ship. That is how scope stays anchored without panic cuts at the end.
FAQ
- What is floating work in software delivery?
- Work with no clear traceability to product goal, release, or outcomes. It consumes capacity without defending the finish line.
- How does ReleaseFlow handle floating work?
- By requiring hierarchy and anchors: every unit of work links to the finish line, or it is triaged out of the critical path.