Ricardo Fiel explains how a culture of blame leads teams to failure and self destruction

Ricardo tell us a story of a company where he worked where blame was part of their job. He explain us how that culture drove teams to self destroy.

About Ricardo Fiel

Ricardo has 12 years experience in software teams, He had multiple roles from developer to architect to CTO, working in both startups and global corporations. He led teams from 4 to 30 members. Currently, he leads product development (SaaS) teams at Rupeal. You can find Ricardo in linkedin or twitter.

Ricardo Fiel tells us the biggest learning comes from trying out new and not be afraid of failing

Ricardo explains how he failed with one of his previous teams, and how this failure led him to understand that trying out new approaches is a key factor for leaning and improvement.

About Ricardo Fiel

Ricardo has 12 years experience in software teams, He had multiple roles from developer to architect to CTO, working in both startups and global corporations. He led teams from 4 to 30 members. Currently, he leads product development (SaaS) teams at Rupeal. You can find Ricardo in linkedin or twitter.

Zach Bonaker on the 3 successful outcomes for Scrum Masters

In this episode, Zach Bonaker explains the three outcomes he thinks are critical for Scrum Masters.

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.

Zach Bonaker on Apprenticeship for Scrum Masters

Zach shares his journey as a Scrum Master and how important it is to get a pair in your own journey. Apprenticeship for Scrum Masters is not a new idea, but it is an important part in our toolbox for learning as Scrum Masters.

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.

Dennis Mansell talks how a semi destructive team is even worse than a complete destructive team

Dennis discusses that most of the times when we start to work as a team, we simply put people together expecting that everything will work. We even forget to ask if people do actually want to work together. In this episode he explains how that can go wrong.

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 tells us how you can be fired for not spending all the project budget

Dennis explains us how most of his learnings came from failures. In his story he explains how he lost a project because he spent only 10% of the total budget. As an outcome, spending just this small part of the budget led Dennis to loose his job.

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.