13

sprint started two weeks ago, it's due today.

yesterday, most tasks for the sprint were done, but was still waiting that whole two weeks for updates on two new tickets, guess they'll be in the next sprint...

project leaders yesterday: oh here are those updates for the sprint! (not to mention the meeting was at 5 PM yesterday, not even the BEGINNING of the work day)

project leaders today: what's the status of the sprint?!

...it's a joke, right? do you think I'm a fucking magician?

its always the same no matter where you go, slowly starting to realize...

tl;dr; adding new feature requests the day before a sprint ends and then having the nerve of asking the "status" of the sprint the following day.

Comments
  • 1
    I feel you buddy.
    Not everywhere is the same, my last place in retrospect was very very agile, and I mean agile done right.
    But because no one in the company had done agile before I think we assumed everywhere was probably doing it better than us, or at least the same.

    Oh how wrong we were. Fast forward a few years and we’ve all moved into other places, some good some not so good.

    Since then I’ve been on a project where the exact same scenario you described happened to us but with the extra caveat that if we didn’t deliver feature x by Monday the company wouldn’t be paid and would probably be fined.
    Well if it was that important it wouldn’t be ignored until past the last minute but everyone in the place.

    It didn’t get done, I’d rather see the place burn down that bend the knee to that scummy project manager.

    (And on Monday there was no mention of that feature not being done, of fines or not being paid. It was as if it never happened)
  • 0
    @TrevorTheRat "fined" for not completing a feature in time?! what kind of hell hole dystopia is this?!
Add Comment