3 ms·
>don't start any new stories, wait until they next sprint officially started I think there's room for this kind of thinking, if the end of sprint is tied to a
by rgblambda 3y ago
>don't start any new stories, wait until they next sprint officially started
I think there's room for this kind of thinking, if the end of sprint is tied to a release, and spare capacity gets redirected to helping complete existing stories (both those things need to be true). I've never been in a team that did that though so I don't know how well that would work in practice.
- philomath_mn 3y agoYou can start on new work even if it doesn't get merged that sprint. Especially thorny tickets where 90% of the work happens before any code is written. But I agree with your point about assisting others on existing stories (if help can be given).