8

Product owner and scrum master prioritized a not important user story. We are just new to the assigned team without proper turn over, KT, vague user story(one sentence) and no time to prepare our local environments. Then after sprint 1 the client wants a demo by next month but the PO and SM had prioritized the wrong user story so now they are pressuring the developers on finishing fast the other correct important user story. They mismanaged it and now they say the development was slow thus blaming us?! WTF. We hit the deadline of the first user story with unpaid overtimes.

The other PO was always asking us on how to fast track the development lol.

I'll tell them all their faults in the next meeting. As usual we are just high paid corporate slaves with golden hand cuffs trying to escape the rat race.

Comments
  • 1
    @rutee07 well it is very common. That's why I'm always making my skills up to date always so if something bad happens they I'll just apply somewhere else as a high paid slave again lol.

    I badly want to escape this rat race and be my own boss. Build a business but it is hard.
  • 1
    If I had a cent for every single line user story formated as a:

    "Add crap to unimportant screen"
  • 3
    I’ve never seen a scrum team working without those problems in the last 10 years.
  • 0
    Why wait till next meeting? Fire an email away
  • 2
    No overtime, no work. If they balk, see if they can get the feature on time with no devs.
Add Comment