Scrum joke
I wrote an Agile joke to poke fun at my PO<->Team interface.
PO: How many Scrum members does it take to change a lightbulb?
I can’t believe you are even asking us that question.
First, you are effectively asking us to estimate something in engineer days, and you know we work in story points.
Second, and we’ve talked about this before, you are encoding the solution into the story. What we need are stories with requirements. Your requirements are something like you can make the room light or dark with the flick of a switch. Please sort this out with the stakeholders.
Third, you haven’t, in any way, defined the exit criteria. For example what are we doing with testing and documentation?
Fourth, we clearly have a solution that requires regular manual intervention. This is unacceptable for a truly agile team. We need to invest in automation of the bulb changing, or whatever solution we come up with. This will make the story more than 100 points, so say goodbye to velocity for three months.
Er, hold on, maybe it’s actually an impediment that the team can’t see what it’s doing….. there you go, bulb changed.
Third, you haven’t, in any way, defined the exit criteria. For example what are we doing with testing and documentation?
How is it the PO's resposibility to define the Definition of Done? :P
And, since this is supposed to be a humorous thread, here is the shortest Scrum joke ever:
A Scrum Master without sticky notes.
A fun thing I sometimes come up with, when a team starts getting a little sloppy when it comes to fulfilling their DoD is the DoAD ;-)
Another one describes pretty good what's wrong with management interfering with a team's estimation :)
I love Dilbert!
