Kanban Metrics 📈 You Should Use To Make Scrum Sprint Retrospectives Effective

No video

Kanban Metrics 📈 You Should Use To Make Scrum Sprint Retrospectives Effective

Рет қаралды 2,305

Scrum Master In Black

Күн бұрын

Пікірлер: 15

@ELISASKomMBA 2 жыл бұрын

creative ❤️

@eliassantos1334 2 жыл бұрын

Thank you! You're doing an awesome Job 😜

@scrummasterinblack 2 жыл бұрын

Thank you for the kind words. I really appreciate it 🙏

@user-rt5ox9jg6z 6 ай бұрын

Amazing explanation. Thanks to your awesome I finally understood how to use the Jira Control Chart. Very Powerful tool.

@thiagopereiradossantos588 2 жыл бұрын

I love using metrics in my retrospective meetings

@scrummasterinblack 2 жыл бұрын

🙌

@biplab43 Жыл бұрын

Great video, Joshua. It was so interesting that I paused the video after every single sentence and consumed the content deeply ☺ Honestly speaking, I really liked the part about "Why Scrum Teams Skip Retrospectives" the most. One comment I have is that the leading indicator metrics of the Aging WIP chart give more value in the Daily Scrum event compared to retrospectives, as it really highlights the PBIs that may require some action/collaboration to meet the sprint goal. Thoughts?

@scrummasterinblack Жыл бұрын

Hi Biplap. Thank you for the feedback. Yes you are right, the Aging WIP Chart is useful during Daily Scrum too as I explained on this video -> kzfaq.info/get/bejne/mbKFjMt6qJfXkp8.html

@benjamincotrel8326 2 жыл бұрын

Another reason that makes teams quit doing retrospectives is always talking about the same problems because they are outside their influence zone. So after multiple retrospectives ending on "well there is not much we can do to fix this", they just stopped doing them.

@scrummasterinblack 2 жыл бұрын

Interesting. Thanks for sharing @Benjamin. Never seen it personally because I think the Scrum Master or the Product Owner should be the person who are within the stakeholders ring. What kind of Scrum team would work with stakeholders who are outside of their influence zone?

@benjamincotrel8326 2 жыл бұрын

@@scrummasterinblack In my experience, this pattern came with a misalignment between the team and the stakeholders. The Scrum team could not be self-organized because there was a lack of trust from the stakeholders. This resulted in the stakeholders telling the PO what needs to be delivered to customers.