Scrum masters help teams when they create an environment where teams can, and are willing to take ownership and responsibility for what they deliver. Teams that take ownership are then ready to start solving their problems.
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.
The worst enemy of this particular team, according to Jeff Kosciejew, was the pattern of avoidance. Avoiding problems is one of the pitfalls that our teams deal with.
Jeff also refers to #MobProgramming, an innovative practice originally promoted by Woody Zuill.
About Jeff Kosciejew
Jeff is a consummate generalist, with experience in a wide variety of industries in a wide variety of roles. Throughout all of his experience, Jeff has had enjoyed success through a single focus on enabling and empowering those he works with, even before being introduced to Agile and Scrum.
You can find Jeff Kosciejew on twitter, and reach Jeff on LinkedIn.
Product Owners are often given that role because of what they know, but Scrum requires that Product Owners be available to the team. If they are not available that will create problems for the team.
Assigning a Business Analyst as a Product Owner may not be the right choice, especially if that Business Analyst is used to writing requirements “the old way”.
Listen to the podcast for Peter’s experience and insights on the problem.
About Peter Hilton
Peter is a software developer and technical project manager who has experienced every point on the agility spectrum, in the course of 18 years of development projects. Peter has performed several variations of the Scrum Master role, and learned what the books dont tell you: whats easy and whats hard.
You can reach Peter Hilton on twitter and read his blog at Hilton.org.uk.