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.
Matt tells us how he defines success for the Scrum Master role. The key characteristics and how to link it all up to business value. He also mentions the technique he uses as a “barometer” of his success as a Scrum Master.
How can you find if a person you are recruiting is a “team player”. Matt explains his experience in one situation where he missed that aspect, and what he learned from that. He gives a recipe of how you can screen for team fit when recruiting Scrum Masters.
Matt explains how the focus on the negative can emerge from the harmless need for “venting” your frustration. Too much venting can have disastrous consequences on the team’s morale and motivation. He also offers an antidote for that negativity in this episode.