Is there a difference between Slices and Scopes?
Problem at hand:
We are trying to come up with integrated slices for every project. Slices need to be deployable, integrated (frontend+backend), and bring us closer to delivering value of the Pitch.
Since it is hard for engineers to think in terms of business value, they consider delivering some tech staff to be valuable for the Pitch.
So, the process gradually evolved into this: a slice is deliverable, short, deployable, integrated, and when shipped can provide value to the user. If the project is closed and no more work is done on it, this slice is still usable and valuable to customers.
The problem, however, was not solved, since now these slices are in no way short. They feel like an MVP.
In THE BOOK:) there is a difference between slice and scopes, but it is not evident how you can manage scope of project is some of the scopes don’t fit the timeline, and it is found out only in the middle.
Scope as is does not deliver value separately from other scopes. So, until the end of the cycle, we cannot be sure whether we are on track.
So, my questions:
- Difference between slice and scope
- should all slices and scopes be shippable separately?
- should all slices and scopes deliver value to end user separately?