4 ms·

Did you bring it up with your management? The sibling comments about Kanban are spot on. Management probably is rightly worried about tracking and estimating,

Did you bring it up with your management? The sibling comments about Kanban are spot on. Management probably is rightly worried about tracking and estimating, if you can offer an alternative that can get them that they'll be on board. However, your description of "1-2 months for a couple developers" does ring warning bells for me. Having the adequate granularity is good. Also, many times "1-2 months" doesn't take into account everything needed. I absolutely agree that "wait for the end of the sprint and present" is not a good way to do it. If I were a manager, I'd try to minimize "unknowns" and "challenges", I understand what you're saying as a developer, there has to be a balance - where I am we agreed to have google-style 20% research time and us developers have a lot of agency and input into schedules and next steps.

sheepmullet 9y ago
> Management probably is rightly worried about tracking and estimating The real question is why are they worried about tracking and estimating? From there you can work out the granularity required. Unfortunately often when management shows interest in sprint level details it is because they don’t trust the team and tracking the numbers helps them feel in control. > If I were a manager, I'd try to minimize "unknowns" and "challenges" A senior dev should be looking across the project and trying to minimize unknowns and challenges. Then it aggregates up the chain. Scrum does have an unfortunate tendency of removing responsibility for the bigger picture from developers.