Your code can compile while you’re in a retro, retrospectively looking back at the action items raised in a previous retro but not assigned any sprint time in the current sprint so you just raised a “what went wrong” about it not being planned and now you have more non-sprint work to do because every problem should be presented with a solution and if you could have that for the next retro they’ll review this retro’s action items and see if you have a proposal for fixing retro action items
This is my workday now
https://xkcd.com/303/
Nowadays they will tell you to work on something else in the meantime.
Your code can compile while you’re in a retro, retrospectively looking back at the action items raised in a previous retro but not assigned any sprint time in the current sprint so you just raised a “what went wrong” about it not being planned and now you have more non-sprint work to do because every problem should be presented with a solution and if you could have that for the next retro they’ll review this retro’s action items and see if you have a proposal for fixing retro action items
This is why I call scrum masters scrumlords.
Thankfully my boss is hands off so I took a walk and then worked on an internal tooling side project that really only I will appreciate.
Scrumlords I love it
As someone who hasn’t worked anywhere with a profit-motive in over a decade, I don’t know how you guys do it. Truly…
Yep