Nicolas Umiastowski on how the blame culture can destroy a team

The fear of losing your job can drive a blame culture and a lot of other dysfunctional behaviors in teams. When that fear sets in, defensiveness, silos, lack of cooperation are just some of the symptoms you should expect to see.
Nicolas also mentions how important it is for teams to learn how to deal with failure without falling prey to the blame culture.

About Nicolas Umiastowski

Nicolas is 40 year old. He is a a French agile coach, specialized in Scrum and Kanban with a strong experiences in Digital and web projects.
He likes Design thinking, storyboarding (especially paper prototypes), getting real feedback from real users, and helping the team to reach symbiosis, and to find meaning in what they do. He is absolutely passionate about agility, but aware that depending on the context (as a consultant), agility can be different from one company to another.
You can find Nicolas Umiatowski on twitter, and follow his blog in french: Nicolas Umiatowski in french.

Nicolas Umiastowski shares his ideas on how to help organizations improve

Help organizations improve, is what Nicolas decided to do after having started his career in IT as a self-taught programmer, and later as a project manager. From looking for bottlenecks to helping organizations adopt Continuous delivery, these are just some of the lessons Nicolas learned from his experience and applies today in his work as an agile coach.
Nicolas also refers to the podcast This Agile Life, which we believe is a great addition to your podcast library if you like the Scrum Master Toolbox Podcast.

About Nicolas Umiastowski

Nicolas is 40 year old. He is a a French agile coach, specialized in Scrum and Kanban with a strong experiences in Digital and web projects.
He likes Design thinking, storyboarding (especially paper prototypes), getting real feedback from real users, and helping the team to reach symbiosis, and to find meaning in what they do. He is absolutely passionate about agility, but aware that depending on the context (as a consultant), agility can be different from one company to another.
You can find Nicolas Umiatowski on twitter, and follow his blog in french: Nicolas Umiatowski in french.

Andy Deighton on how Retrospectives can make a critical difference in the team’s evolution

Why not share the results of the retrospectives with the rest of the organization? That’s one very effective way to make the current team’s obstacles visible to the rest of the organization.
Start with something simple, like the Check-in from the Core protocols, and share what you find with the organization. Help the organization help the team using the retrospective output.

About Andy Deighton

scrum_master_toolbox_podcast_Andy_Deighton Andy has over 20 years of development experience in Smalltalk and Java, and is now a Scrum Master at Bright Interactive, based in Brighton on the south coast of the UK. He’s a former professional photographer and budding songwriter. You can find Andy Deighton on twitter. Connect with Andy Deighton in LinkedIn.

In case you are interested in Agile Retrospectives we are at the moment preparing a 10 DAYS FREE AGILE RETROSPECTIVES PROGRAM. This is a complete self-study program where you will learn anything that you need to become a great Agile Retrospectives facilitator.

Andy Deighton discusses Agile outside software work

Agile outside software work is one of the topics that Andy discusses in the context of defining the success of the Scrum Master. As Scrum Masters we work with everybody in the organization, not just the team. Helping others is an effective way to help the teams as well!
Andy also shares his views on how we should NOT measure success of a Scrum Master.

About Andy Deighton

scrum_master_toolbox_podcast_Andy_Deighton Andy has over 20 years of development experience in Smalltalk and Java, and is now a Scrum Master at Bright Interactive, based in Brighton on the south coast of the UK. He’s a former professional photographer and budding songwriter. You can find Andy Deighton on twitter. Connect with Andy Deighton in LinkedIn.

Andy Deighton on how to help Scrum Masters grow

Andy discusses how hard it is to hire, and how we must constantly help Scrum Masters grow in their practice. Even if the Scrum Master is doing a good job (and also because of it), the teams will evolve. The style of the Scrum Master must then match that team evolution.

About Andy Deighton

scrum_master_toolbox_podcast_Andy_Deighton Andy has over 20 years of development experience in Smalltalk and Java, and is now a Scrum Master at Bright Interactive, based in Brighton on the south coast of the UK. He’s a former professional photographer and budding songwriter. You can find Andy Deighton on twitter. Connect with Andy Deighton in LinkedIn.

Andy Deighton shares how the communication inside the team can affect communication with stakeholders

Communication inside the team is a key indicator of whether they are performing or not. But the quality of communication in the team will also directly affect the communication with the stakeholders. Andy shares his insights into how to enable teams to improve the way they communicate, and work on the group dynamic.

About Andy Deighton

scrum_master_toolbox_podcast_Andy_Deighton Andy has over 20 years of development experience in Smalltalk and Java, and is now a Scrum Master at Bright Interactive, based in Brighton on the south coast of the UK. He’s a former professional photographer and budding songwriter. You can find Andy Deighton on twitter. Connect with Andy Deighton in LinkedIn.

Andy Deighton’s key learning from failure: Always be Brave, Experiment, Listen and Learn

Andy starts by defining a great team: happy people building great software. A team that is focused on outcomes, rather than outputs. He explains how he learned to be a better Scrum Master through his experience, and what he changed in his own approach to the role of scrum master.

About Andy Deighton

scrum_master_toolbox_podcast_Andy_Deighton Andy has over 20 years of development experience in Smalltalk and Java, and is now a Scrum Master at Bright Interactive, based in Brighton on the south coast of the UK. He’s a former professional photographer and budding songwriter. You can find Andy Deighton on twitter. Connect with Andy Deighton in LinkedIn.

Stephen Thomas shares his recipe to help the organization adopt scrum and engage with the scrum team

How do we help organizations to recognize the value that scrum teams can bring, and the obstacles they face in the process? Stephen Thomas shares his recipe and describes a few ideas of how the retrospectives can be an effective practice to help organizations evolve and get better.
Stephen’s recipe for organization improvement:

  1. Help the teams understand their progress with a physical (as opposed to digital) and visual burndown (colorful if possible).
  2. Write the principles on the wall and make sure people see them regularly. Point to them when needed.
  3. Have lots of wall space for teams to use and create their shared view of their work.
  4. Help start and facilitate organization-level retrospectives, because improving one team is not enough for lasting change.
  5. Make the team independent

Before implementing all of this, make sure that the organization has the necessary knowledge to work in an agile manner, helping organize training if needed, and working with stakeholders regularly.

About Stephen Thomas

Stephen Thomas Scrum Master toolbox podcast Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.

Stephen Thomas defines success for Scrum Masters and how he came up with the definition

Defining success for scrum masters is not easy, but it is necessary for us to achieve it. Does it have to do with reaching the sprint goal? Or a regular daily goal? Can a scrum master be successful when the team does not release software regularly? And how about the customer’s view? How can the customer help us define and assess success as Scrum Masters?
Stephen shares how he struggled to define success for him as Scrum Master, and why that was hard.

About Stephen Thomas

Stephen Thomas Scrum Master toolbox podcast Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.

Stephen Thomas on why the recruiting interview is not a good idea

What should we do to help choose the best people for our teams and organizations? Especially if we already believe the recruiting interview is not the best possible, or even most effective method to bring out the best in people. Stephen has a few ideas on how to prepare for the recruiting process, and how to setup a way to watch the candidates in action before finalizing the recruitment process.

About Stephen Thomas

Stephen Thomas Scrum Master toolbox podcast Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.