774
agile (lemmy.blahaj.zone)
submitted 5 months ago by to c/programmer_humor@programming.dev
43 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 5 months ago (3 children)

The theory being that the team rushes to complete the prioritised items. Also in theory if you close all items before end of the sprint, you are free to not work, or work on pet project at your own pace.

Of course middle management hates the idea of others being idle so they asked to squeeze the last part. Efficiency, baby !

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 5 months ago (2 children)

    Sure, it might seem like a sprint compared to a Waterfall project where it's a marathon, where there might be months between points where you check in with the plan and try to figure out if the software is ready to ship yet.

    I still just object to the word "sprint". Any job where you're sprinting over and over, week after week, where that's the main thing you're doing, you're doing something wrong.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 5 months ago (1 child)

    Yea it's why I use the word cycle. In a meeting and the PM says "can we bring this in next sprint?" I reply "not sure about the next cycle, but after that one for sure.". So far I've been subtly nudging multiple people to shift away from using the word sprint

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •