Continuous Improvement: Clarity Before Speed

February 22, 2017 0

Learn which building blocks help you to create the culture of systematic improvement in a software development organization and a Scrum team. This talk discusses how the Deming cycle – Plan-Do-Check-Act has been applied concretely in an R&D organization to ensure that the operational development is done systematically. The practices have been evolving during couple of years and the talk will also share the lessons learned from this journey.

Retrospective Anti-Patterns

December 19, 2016 0

Anti-Patterns are like patterns, only more informative. With anti-patterns you will first see what patterns reoccur in “bad” retrospectives and then you will see how to avoid, or remedy, the situation.

Real-Time Retrospectives & Agile Improvement

October 17, 2016 1

If the retrospectives are one of the main improvement tools for Agile teams, they can also be the subjects of improvement. In this article, Tom Monico explains how his team has adopted the starfish model to create a better retrospectives process where feedback is produced in real-time and not only at the end of a Scrum sprint.

Techniques for Improving Sprint Retrospectives – Part 2

September 21, 2016 0

After presenting some basic retrospective techniques in the first part of this article, Jesus Mendez provides in the second part some additional techniques that focuses on the facilitating part of the Scrum sprint retrospectives.

Techniques to Improve Sprint Retrospectives – Part 1

June 6, 2016 1

Sprint retrospectives are an important tool for Agile software development teams that want to implement continuous improvement and adjustment to their working context. In this article, Jesus Mendez provides some techniques that could help improving the outcome of your Sprint retrospectives.

Mastering Scrum Retrospectives

March 24, 2016 0

When I started with Agile and Scrum back at 2005, I was not much different from any other agile newbie, and I was complaining for having regular retrospective. “What for? We are already sitting together, we are a good team, we tell each other what should be said. It’s waste of time. Formal meeting…” Later I realized retrospective is quite useful and implemented it as one of the key Scrum practices.

Continuous Improvement Without Blame

March 7, 2016 0

The frontier is somewhat thin between analyzing things for continous improvement in Agile and blaming people for failure. In this blog post, John Allspaw discusses how Etsy wants to consider mistakes, errors, slips or lapses with a perspective of learning. he explains how having blameless post-mortems on outages and accidents are part of this approach.

1 2 3 4 8