This story on HackerNoon has a decentralized backup on Sia.
Transaction ID: h1YIqiuCPHwnShw8Yv7MtmuTHVh1_q017sjmMmnJoCk
Cover

How Metrics Lead to Effective Sprint Retrospectives

Written by @george-guimaraes | Published on 2020/9/17

TL;DR
Atlassian playbook states that Sprint Retrospective’s goal is to identify how to improve teamwork by reflecting on what worked, what didn’t, and why. Using pull request lead time and throughput in Sprint Retrospectives can truly help teams to understand how they are performing. The data bring valuable insights and allow teams to question their decisions, says George Guimarães Guimaraes. He suggests that managers should promote a culture in which people raise their hands when the problems occur.

[story continues]


Written by
@george-guimaraes
CEO at SourceLevel

Topics and
tags
agile-software-development|agile-scrum|sprint-retrospective|metrics|software-engineering|software-engineering-metrics|engineering-management|agile-leadership
This story on HackerNoon has a decentralized backup on Sia.
Transaction ID: h1YIqiuCPHwnShw8Yv7MtmuTHVh1_q017sjmMmnJoCk