Many organizations look carefully at where their people spend their time. This is, in general, a good thing. Problems start when we don’t give our people the chance to succeed. A very common anti-pattern in this context is the part-time Scrum Master temptation. We believe that a good Scrum Master can handle more than 1 team. But do we know the problems that come from that? Can we recognize the anti-patterns that result in time to avoid bigger problems? In this episode, we discuss the anti-patterns that result from part-time Scrum Master assignments so that we can detect those in time and avoid them if possible!
About Samantha Webb
Samantha is a Scrum Master based in London where she works with clients in a number of different industries. In her spare time, she is a game writer and designer and uses Scrum to work on game projects.
It is very common that teams stay in the cycle of no improvement. They go through the motions, even have retrospectives every sprint. But nothing happens. This can be very de-moralizing. How can we help our teams get out of the rut and start making a real impact in their results? Listen in for Karthik’s 3 suggestions to make your retrospectives more effective.
About Karthik Nagarajan
Karthik has worked as a Product Manager, Scrum Master and QA Manager across a variety of domains, including: Fintech, Travel, Human Capital Management, CRM, Recruitment, Insurance, Banking and Financial Services. He loves tackling complex business challenges and being a positive bridge between Product, Design, Engineering, Quality Assurance, Customers and Business Teams.
Teams need to care about their work. If teams are the only ones that care, that can’t last for long. In this story Adrian talks about the role of stakeholder engagement and how critical it is to learn to engage the stakeholders. When that engagement dies out, bad things start to happen.
About Adrian Kerry
A Scrum Master who specialises in Mobile and User Centred Design based approaches, Adrian comes from a testing background and he still finds that he champions making testing easier for the teams he works with. Due to that Adrian is also a strong advocate of XP practices (and, from that, BDD)
Conway’s Law is a little known observation that organizations seem to mimic the architecture of the software they develop, and vice-versa. So what does that insight mean for us Scrum Masters? Jacopo shares with us his story of a team that was living proof of Conway’s Law, and how he used his understanding of team dynamics and Conway’s Law to help the team evolve and get out of the self-destructive pattern they found themselves in.
About Jacopo Romei
Agile practitioner since 2003, entrepreneur more than once, he has been agile coach in eBay Italia, co-founder of the ALE Network and a former member in Cocoon Projects, an open governance based company. His main focus now are contracts and lean-thinking-compatible agreements.