3 ms·
> Go mutilate your plan so that you have a Real Deliverable every five working days If we're talking about web development - yeah, pretty much. IME, most proje
by hbrn 4y ago
> Go mutilate your plan so that you have a Real Deliverable every five working days
If we're talking about web development - yeah, pretty much. IME, most projects where team lead was not willing to "mutilate" were a disaster.
> Neither of us know how long the entire project ran, so "A few weeks" could be a small overestimate
Are you saying changing state handling (whatever this means) in a young startup could take several months? If that's the case, they definitely should not be teaching how to move fast.
- simoncion 4y ago> ...most projects where team lead was not willing to "mutilate" were a disaster. It seems like you agree that my core statement ("sometimes the smallest unit of work cannot and can never fit into a one (or even two) week Sprint") is correct, but are unwilling to explicitly say so. > Are you saying changing state handling... I'm saying that neither you nor I have the details required to understand the minimum time required for the project. You've said yourself that you have experience with tasks that have justifiably run longer than a work-week. So, it's clear that -given more information about the task- you could be convinced that the time estimate is a reasonable estimate of the time required.