Sooner or later we will be in a situation where someone has committed to a goal that the team did not co-create. A schedule the team did not work on. A plan that the team wasn’t aware of. These are normal anti-patterns that we will deal with in our role as Scrum Masters. And while, in some cases, it is better to run away, we also must be prepared and help our teams and stakeholders to deal with those anti-patterns. In this episode, we discuss those anti-patterns, how they can affect the teams we work with and also what we can do to avoid the common pitfalls that come with them.
About Jac Hughes
Jac is a scrum master who has a passion to help teams become empowered, autonomous bust mostly importantly productive. Jac has served 7 years in the Royal Navy before moving into the world of IT.
Blockers are our most common obstacle. We face them, the team faces them. In fact, most of our time is spent on either solving or helping team and stakeholders solve the most critical blockers to progress. In this show Balazs gives us some tips on how we can get the teams to crush the blockers. Help the team crush their blockers and you will see them blossom and progress faster than you could imagine.
About Balazs Tátár
Balazs is a technical project manager, working for the European Commission in Brussels, Belgium. Currently, he plays the Scrum Master role in a support team of one of the biggest web project at the European Commission. He is a former technical lead and fan of open source technologies.
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)