How is Safe supposed to improve software development? What exactly is better with Safe? I am PO in a team that is currently very frustrated because of the amount of added bureaucracy, unnecessary ceremonies and countless meeetings that come with Safe, plus the fact of having to "unlearn" and learn someone else's way of doing things. Another thing I've noticed is that with Safe, many more people feel entitled to discuss software development without actually participating in the development process themselves.
Every practitioner, team and organization aspiring to succeed with Agile Delivery Transformation should watch this video. It can't get simpler than this... 1. Start small, 2. get support, 3. measure along the way! Beautiful ✌🏼🙂
I'll add to my backlog to create a video on metrics. In the meantime, you can use anything a team or organization wants to improve at. Things like number of defects, cycle time, etc. If you want to measure how a team is doing at agile you can also take the free assessment here and then repeat it for a team in 3 or 6 months and see how much they improve: www.mountaingoatsoftware.com/elements-of-agile
Great video Mike! I have a couple of questions for you. Can a Scrum Team conduct the Retrospective in the next sprint because the Sprint Review didn't happen on the last day of the Sprint? Can you also suggest some good Agile Metrics for a new Scrum Team?
Thanks. I guess if a sprint review gets delayed for some reason then it would be ok to postpone the retrospective. However, most of the times I can imagine, I think the retrospective could be held on the last day as planned even without having done the review. Most teams will have a good idea how the sprint went without hearing the specific feedback on their work. I've added it to my backlog to create a video on metrics.
