So our scrum team was talking this morning about some mega screw ups that one team continues to make but could apply in any situation and how we could bring transparency and accountability for the ...
Obviously if the product owner judges solely based on whether the committed stories were done, it wouldn't be good, because then the team will just commit to fewer stories next Sprint. On the other ...
As a result of a retrospective we were uncovering worse ways of developing software. We had a idea we though was great and tried it. We stayed with it during the development of a major update which ...
How do you run a sprint retrospective to maximize participation and honesty? And what about follow up on action items? [closed]
I've seen it done as a free-for-all where the scrum master just asks everyone to throw out comments. Or a time-boxed session where "anonymous" comments are posted on the walls bucketed by category. My ...
I am a Junior at workplace and I have been to a number of our retrospectives over the last year. I have been asked to facilitate a retrospective of my own. So far, we have done "hats (red, green, ...
We currently drive changes to our process through the following mechanisms: Weekly wrap-up meeting Project postmortem We discuss what isn't working, what is working, etc. I use these settings to ...