Heidi Helfand on the need to help teams change: Reteaming

We’ve often heard that teams should be long lived and stable. But what if the advantages or reteaming would be much larger than the disadvantages of changing team composition? In this episode we explore the topic of Reteaming and what Heidi has been developing and discovering that helps teams thrive when they change.

About Heidi Helfand

Heidi’s been in the software industry for 17 years and has a masters in teaching English. She has been a part of two successful startups. She was on the initial team that invented gotomeeting and gotowebinar at the first startup. She is currently Principal Agile Coach at AppFolio, Inc. where they create software for property management companies and law firms. She started there in 2007 hired as a Scrum Master – trained by Ken Schwaber and with Pivotal Labs for more than a year. She became a co-active coach along the way and is certified by the International Coach Federation and the Coaches Training Institute. She is currently writing and speaking about Reteaming – that is, how its valid and desirable to have changing teams as opposed to long running, unchanging teams.
You can link with Heidi Helfand on Linkedin, or connect with Heidi Helfand on Twitter.
You can also follow Heidi’s blog at: http://www.heidihelfand.com/writing/.

Ruben Sadoyan on starting bottom-up change in organizations

How do we start change? Ruben shares with us a story of how you can help start change where you are, at the team level, bottom-up. He shares with us some of the tools he uses to help teams progress and grow at help the change continue in the organization.

About Ruben Sadoyan

Ruben has played many different roles in his career. Agile Coach, Team Engineer, Scrum Master with IT Project Management and Software Development background are just some of those. He’s also been an Account executive with software/web development roots and business development, experienced in team and client relationship management.
He’s also launched a startup named Internet Company and has more than 15 years experience in IT. He describes himself as Focused on constant improvement and self-education. Result driven, able to lead in a Lean way, identify root causes and gradually improve teams to make results happen.

Oana Juncu shares how Design Thinking can help manage change

There are many possible techniques to support and amplify change. Oana shares how she uses Design Thinking to help teams and organizations support and amplify change.

About Oana Juncu

Oana likes to present herself as a Business DJ, mixing whatever practices, from Agile and Lean(Startup) to storytelling , User Experience and neuroscience. In her day to day Oana helps teams and organisations unfold creativity, become proud of their achievements, and delight their customers.
You can connect with Oana Juncu on LinkedIn, or follow Oana Juncu on Twitter.
Oana’s website can be seen at coemerge.com.

Woody Zuill discusses failed Agile adoptions

Agile is an approach to software development that asks us to look at the whole process differently. It asks us to consider different values, principles and perspectives that differ significantly from previous approaches. And it is because of that that it causes many to feel like their previous successes no longer matter. In such an environment it is very easy to feel rejected and that our experience does not count. This leads to problems in agile adoption. Woody talks about one such experience and what he learned from it.

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.

Zach Bonaker explains the role of narrative in change management

There are many tools that can help us in a process of change. The book Lean Change Management by Jason Little lists many of those in the context of a real story about change. In this episode Zach describes some of those tools and how to use then in our roles as Scrum Masters. We also mention the book Nonviolent Communication by Rosenberg.

About Zach Bonaker

Zach Bonaker is Benevolent Trouble-Maker from San Diego. He’s an agile coach who specializes in bringing lean thinking to organizations and teams over varying sizes across the country. Zach builds relationships to help transform people, systems, and structures towards safer and faster ways of delivering high quality software. When he isn’t thinking about next-generation agile ideas, Zach can be found enjoying the sunny west coast weather and connecting with people all around the world. Follow Zach Bonaker on Twitter, and connect with Zach Bonaker on Linkedin.

Dennis Mansell talks about two important parts of the system – System Health and System Productivity

In this episode Dennis explains the difference between two tools that he uses at the organizations he works with. He explains how he uses these tools to measure System Health and System Productivity.

About Dennis Mansell

Dennis did not start his working life as a developer, but as a sailing yacht skipper and owner of a sailing school and he still trains yacht-racing teams. He always supplemented his sailing job with application maintenance, web development and project management. He has since settled down: based in Amsterdam with his wife and son. Now he works as a full-time Scrum Master and Agile Coach for companies ranging from start-ups to the Dutch governmental institutions. His linkedin and twitter: @dennmans.

Dennis Mansell explains how happiness index can be a useful measure to define Scrum Master success

Dennis tells us how he uses a technique known by Henrik Kniberg – happiness index in his daily work. He also explains how important it is to understand what people inside of the team say; he believes that part of a Scrum Master role is to create a good environment within the team. If there are many things being said in a negative way the Scrum Master has a lot of things to do in order to improve the team performance.

About Dennis Mansell

Dennis did not start his working life as a developer, but as a sailing yacht skipper and owner of a sailing school and he still trains yacht-racing teams. He always supplemented his sailing job with application maintenance, web development and project management. He has since settled down: based in Amsterdam with his wife and son. Now he works as a full-time Scrum Master and Agile Coach for companies ranging from start-ups to the Dutch governmental institutions. His linkedin and twitter: @dennmans.

Dennis Mansell talks how it is important for a Scrum Master to create an environment where change happens even without the presence of the Scrum Master

Dennis tells us a very interesting story from his sailing activities. He explains to our audience how it is important to build an environment of collaboration and most importantly an environment where “things” happen even if the most important persons in the team are not present.

About Dennis Mansell

Dennis did not start his working life as a developer, but as a sailing yacht skipper and owner of a sailing school and he still trains yacht-racing teams. He always supplemented his sailing job with application maintenance, web development and project management. He has since settled down: based in Amsterdam with his wife and son. Now he works as a full-time Scrum Master and Agile Coach for companies ranging from start-ups to the Dutch governmental institutions. His linkedin and twitter: @dennmans.

Dmytro Orlyk talks how the systems that put pressure on software developers will not enable high quality deliveries.

In this episode Dmytro describes how the system impacts the teams and the software deliveries. He explains that in order for the teams to deliver a great quality they must be part of a system, which allows them to experiment and develop features without the daily pressure.

About Dmytro Orlyk

Dmytro have an overall 4 years of experience in PM. His latest project has been shown to the Google company. He is an Agile Expert with a strong knowledge of Scrum, Kanban and XP. Few of the engineers that inspire me are Martin Fowler and Chris MacConnell. He can be found in linkedin.

Dmytro Orlyk talks how being part of a team that is improving can be used as tool to measure Scrum Master success

Dmytro explains that being part of a successful team is part of a Scrum Master success. After all, it is his job to create successful teams. Dmytro also gives us some good tips: in order for Scrum Masters to continue improving, they should develop themselves in areas where they feel they are not so strong. They could take some time to analyze their weakness and take some training to tackle those areas.

About Dmytro Orlyk

Dmytro have an overall 4 years of experience in PM. His latest project has been shown to the Google company. He is an Agile Expert with a strong knowledge of Scrum, Kanban and XP. Few of the engineers that inspire me are Martin Fowler and Chris MacConnell. He can be found in linkedin.