Matthew shares with us a story of a disaster hire, and why the regular hiring process is not likely to succeed. He finishes with a value bomb: he shares with us a tip that will help you hire the right person every time! Don’t believe me? Listen up!
About Matthew Heusser
Matthew Heusser is the co-author of Save our Scrum, co-chair of the enterprise track at Agile2015, And he is also an author at CIO.com. Matt Software is a delivery consultant/writer and Collaborative software geek since before it was cool.
You can find Matthew Heusser on LinkedIn, and connect with Matthew Heusser on Twitter.
In a recruiting interview many things get said, and sometimes it is easy to miss the subtle clues that illustrate the candidate’s thinking. In this episode we talk about how to practice active listening in recruiting interviews. Listen to the words being used as they give away a lot of the candidate’s personality and approach to the Scrum Master role.
About Natalie Warnert
As a developer turned Agile coach, Natalie Warnert understands and embraces what it takes to build great products. Natalie focuses teams on embracing Agile values to build the right product and build the product right. Natalie is currently coaching the Cart/Checkout teams for Best Buy Dotcom and recently earned her Master of Arts degree in Organizational Leadership and Strategic Management.
You can link with Natalie Warnert on LinkedIn, connect with Natalie Warnert on Twitter, read her blog at nataliewarnert.com, and visit her project page Women in Agile.
Team culture is affected by the organizational culture, as well as individual culture. It is therefore important for us, as Scrum Masters to realize that the way we allow work to be defined will directly affect the culture of the team. Jon explains how the deep gap between skills makes agile adoption harder, and affects how the team tackles the work they need to deliver.
About Jon Eversett
Former Business Analyst, Product Owner wannabe, currently a Scrum Master. Jon works with teams with different maturity levels and some relatively new Product Owners. You can find Jon Eversett on LinkedIn, or interact with Jon Eversett on Twitter. You can read Jon Eversett’s blog to find out more about his ideas on the role of the scrum master and all things agile.
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.
Recruiting is not easy, but when you are recruiting for an offshore team you face even more problems. How to select the right candidate? The role of language in the relationship with the client, and how to handle multiple cultures are also topics in this episode. Teams face cultural barriers, and remote stakeholders. In this offshore context recruiting is not easy.
Team dynamics are affected by many factors, including certain individual behaviors. Teams that exhibit some of the symptoms referred by Mario may be in trouble. We need to learn about those symptoms and have strategies to deal with those.
This story starts with an US based company acquiring a Latin American software development organization. Mario shares what happened after that, and what he learned from the experience, where distributed agile development was the main method of development.