I am a big believer in continuous improvement, weather that be in the form of Retrospectives, a Kaizen approach, or something else that helps the team reflect regularly. But for the earlier years of my career as a Scrum Master I found myself frustrated by a lack of improvement despite all this reflection (retrospectives that have no impact…).
Often,what I was seeing was that we talked about the problems the team was facing, and then didn’t follow-through with the actions we agreed to take.
When we tried to change our behavior. We might have succeeded for a day or two and then would forget about it. This isn’t continuous improvement this is just continuous discussion!
We need a good way to make sure we are actually making the change we set out to make!
Woody Zuill discusses systems, and tools to help us understand the system. We also discuss how important retrospectives are, and how to go about increasing the amount, and value of your retrospectives: Just-In-Time retrospectives.
About Woody Zuill
Woody Zuill, an independent Agile Consultant, Trainer, Coach, and Guide and has been programming computers for 30+ years. As a pioneer of the Mob Programming approach of teamwork for software development he has been sharing presentations and workshops on Mob Programming for conferences, user groups, and companies all over the world. He is considered one of the founders of the “#NoEstimates” discussion on Twitter.
You can connect with Woody Zuill on LinkedIn or contact Woody Zuill on Twitter.
If you are interested, check the MobProgramming conference.
Retrospectives are both important and hard to get right. There are many teams that stop having retrospectives and feel lost as to how to run them effectively. Niko shares with us his own view of how to run effective retrospectives, filled with tips and advice, this is a must listen episode about retrospectives.
When a team faces a problem they have a choice between blaming someone else (“them”), or taking ownership and making it happen even if that improvement looks beyond their reach. We as Scrum Masters can help teams take ownership, even when they need to involve other people in the resolution of the problem. Alex explains the problem, and some of the possible techniques to get the team to understand that they own the results of their work.
About Alex Fürstenau
When he was 12, his father bought him his first computer, a C64. The moment he saw characters appearing on the television was the moment when he knew he would do something with computers. Several years and a computer science study later that “dream” became true.
Alex quickly realized that the customers were not happy with our product. The first approach was to fix more of the requirements but it made things worse. During that time (around 2002) he thought “There has to be a better way” and he found several, among which was Agile.
It is hard to help teams take steps that move them to the next level. It is human nature to seek comfort and safety. Cliff developed an approach to get teams out of the rut, by helping them want to take their game to the next level. He uses some very simple tools that he explains in this episode.
About Cliff Hazel
Cliff Hazel is a coach at Spotify who is trying to learn about how to build effective teams, and how we can create the conditions for them to thrive. His main interests are: Complexity and Systems, Visualisation and Information Radiators, Curiosity and Continuous Learning
You can link with Cliff Hazel on LinkedIn, connect with Cliff Hazel on Twitter and catch him in some conference near you.
Many teams get stuck in a bad place, but there are some teams that also get stuck, but because they think they already are “good enough”. Listen in to learn how Zuzi learned to work with teams that already think they are “good enough”.
About Zuzi Sochova
Zuzi help companies and individuals to be more successful. She teaches teams and their managers how to be more efficient, how to provide better quality and how to communicate and organize teams so that people have fun, they are motivated and have high commitment. Zuzi helps teams and managers find out how to handle customer relationship to help them improve customer satisfaction.
You can visit Zuzi’s website at: http://sochova.cz/, and link with Zuzi Sochova on LinkedIn, or connect with Zuzi Sochova on twitter, or your favorite conferece.
We’ve all done it in one way or another. We spend time in a retrospective criticizing what is wrong, and assigning blame to others. Jeff Campbell has been there as well, and in this episode he explains how you can get teams to stop spending their valuable time whining, and start taking action.
About Jeff Campbell
Jeff is an Agile Coach who considers the discovery of Agile and Lean to be one of the most defining moments of his life, and considers helping others to improve their working life not to simply be a job, but a social responsibility. As an Agile Coach, he has worked with driving Agile transformations in organisations both small and large. He is one of the founding members of www.scrumbeers.com and an organiser of www.brewingagile.org in his spare time. He is also the author of an open source book called Actionable Agile Tools, where he explains how he uses 15 of the tools he uses in his daily work as a scrum master and agile coach.
You can link with Jeff Campbell on LinkedIn, and connect with Jeff Campbell on Twitter.
We can sometimes overwhelm the teams we work with by introducing too many methods. Anton explains how he likes to introduce methods to the team, by running experiments with the team to see if the method fits the team, and solves the problem they want to tackle. He also gives a critical advice on one of the most common anti-patterns for Scrum Masters: wanting to help too much.
When we introduce visualization methods in an already dysfunctional organization, there’s a tendency to see problems and point at the guilty parts. However, our dysfunctional processes are the result of the system conditions, not the people in the system. Marcus reminds us of that fact and asks us to hate the sin, not the sinner. He also shares a great tip to get started with visualizing the work in progress.
Marcus shared with us a discount code for all that purchase his book until October 14th, 2015. Don’t miss it, purchase the book at http://bit.ly/theKanbanBook, and use the code scrumkan.
Marcus is the author of Salvation:The Bungsu Story, a fascinating account of a real-life crisis, and how Agile, Lean and Kanban saved the Hospital from bankruptcy! Twice! Get ready for the journey, it’s going to be a bumpy ride!
Technology enthusiast. Change artist. Culture hacker. People focused. Helping organizations provide their employees with the most meaningful and fulfilling experience they could have while delivering solutions that change the world. Ebenezer is also a Tech Director at Mannheim.
You can link with Ebenezer Ikonne on LinkedIn, and contact Ebenezer Ikonne on Twitter. You can also read his thoughts on Agile on his blog.