Highlighting issues that will slip as soon as possible
This is a continuation of the 11.4 retrospective.
@victorwu said:
I noticed these two issues went much pass the original estimation. (Both still not merged.) Assuming that at least poor estimation contributed to the problem, I think we should identify why we are doing a poor job estimating and brainstorm ways to improve together.
@jarka said:
We should try to avoid setting
due-22nd
label for too many dependent issues. We had 4 issues about closing epics, all of them withdue-22nd
label. Missing the deadline for one of them led to delaying the rest of them as well. #10 (comment 105779957) for more info
@pedroms said:
- If we notice that an issue might be too big to be implemented in a single milestone but the developers have not voiced any concerns, we should ask them directly and offer to break it down into smaller issues as soon as possible.