10

"Here's the sprint, it's well defined. fullstackchris, can you do this in two weeks?"

"Hmmm... nice work, looks well defined. It'll be tough, but sure, I can do it two weeks!"

Two days before sprint ends:

"Can we quickly duplicate n number of features from apps with literal armies of devs like whatsapp, airbnb, and Instagram?!?!?! We NEED these features to be polished and work perfectly!"

Scope creep will be my ONLY feedback in this retro.

Comments
  • 5
    "Let's take a look! Bring it to the next sprint planning / backlog refinement meeting and we'll scope it out properly then schedule it in the next sprint."

    Seriously, anyone who thinks they can just add work to the current sprint because they feel like it has no clue what scrum is. Those people piss me off more than lazy crappy devs. It's not even hard, it's not a lot to learn, it's not complex - you just *don't* add stuff to the sprint without refining it, storypointing it and discussing it with everyone involved, it's that simple.
  • 0
    For me that has always come from the project managers every damn time.

    The product owners understand they’re jeopardising their own sprint so they’re cool with us talking about it and then planning it out.
    Generally they’ve been people working in an area of the business and nominated to own a product. They’ve had little to no training but done great jobs.

    Then we have the project managers. They’ve always been highly paid, have to or three project management certifications, one of them is something agile related.
    And yet they are always trying to derail their own projects by doing the complete opposite of what you should do.

    Honestly I just don’t understand them. I’ve been in the biz 20 years and only ever worked with 2 that were any good, rest were nice people who were shit at their jobs.
Add Comment