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.

[–] EleventhHour@lemmy.world 17 points 4 months ago (1 children)

I think this may be less about Agile and more that you have a great management team that sets clear priorities and goals. Not every Agile environment is like that.

[–] korthrun@lemmy.sdf.org 14 points 4 months ago (2 children)

I do greatly appreciate my management and general company tech culture, they're great.

I agree with your stance here, because it's part of my point. I tend to see more people bitching about Agile itself and not management or their particular implementation.

The jobs where I was only given enough info to plan 2 - 4 weeks out were so stressful because I frequently felt like I was guessing at which work was important or even actually relevant. Hated it.

Turns out it's a skill issue ;p (on the management level to be clear). Folks, don't let your lazy managers ruin you on a system that can be perfectly fine if done right.

[–] EleventhHour@lemmy.world 5 points 4 months ago

Well said. I have nothing to add to that.

[–] korthrun@lemmy.sdf.org 2 points 4 months ago

I want to add: 2-3 sprints ahead is a GREAT begining goal for a team trying to get started with Agile.

Long term though let's set that bar higher :D

[–] PeriodicallyPedantic@lemmy.ca 9 points 4 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.