3

PO: "Remember guys, protect your scope!"
.. moments later, after the PO meeting..
PO: "I want you to do user story x but I want it changed this way"
me: "Ok"
*pling* notification: PO changed jira story
*I work on it for a few hours*
me: "Is this what you wanted?"
PO: "Yeah, actually I made up my mind. I want you to implement it totally different and scrap what you added now"
me: "Thanks for wasting my time bro"
me: *codes*
.. a few hours later, mid-coding..
PO: "Uh, yeah, changed my mind. The way you did it now is ok, but I want something else added"
*3 iterations of the same crap later*

me: "Sigh, make up your minds!"

Comments
  • 3
    Git is a life-saver in this scenario.
  • 2
    @GMR516 Did you read the story? This is using git. No amount of git will save your time from bad management.
  • 2
    @CaptainRant Actually, I did read the story. Just went over it again right now, as well. Unless I'm blind, I see no mention of git at all. Still annoying management, but it's not hard to revert back to a previous commit, is it? I suppose if you're not getting paid or something it could be infuriating.
  • 0
    @GMR516 I wonder where in this world there is Scrum without git and jira. And no, we don't have a revert policy. The point is that Scrum shouldn't be this way. You shouldn't have to revert commits on a story the whole time. You make a story and you stick to its general scope; you don't go and add features all the time. If you want that, you make other jira tickets.
  • 1
Add Comment