My teammates and I have no trouble planning multiple quarters in advance. If something crops up like some company wide security initiative, or an impactful bug needing fixed, etc then the related work is planned and then gets inserted ahead of some of the previously planned things and that's fine because we're "agile".

I delivered a thing at the end of Q3 when we planned to deliver at the start of Q3? Nobody is surprised because when the interruptions came leadership had to choose which things get pushed back.

I love it. I get clear expectations set in regards to both the "when" and the "what", and every delay/reprioritization that isn't just someone slacking was chosen by management.

[–] PeriodicallyPedantic@lemmy.ca 8 points 3 months ago

That's not agile.

It's not bad, it's just not agile. Agile exists for projects where that simply isn't possible. Its sacrificing a bit of potential best-case productivity to ensure you don't get worst-case productivity.

load more comments (4 replies)