When teams are pressured or pushed to work harder, or longer hours, the easy solution is to just say yes, and carry with it. However, the role of Scrum Masters is to help teams understand and prevent those cases when the “work harder” mantra is disconnected from the goals of the company. In this episode, we discuss one such example, where the team was not able to say “no” to the PO, and was, therefore, pushed to do more, and more work and forgetting to focus on improving as a team.
Featured Book of the Week: Leading Teams by Richard Hackman
Pieter is a hands-on generalist with a background in software development. A passion for helping teams work together better. Agile aficionado since his first endeavors in Extreme Programming. Happened to be among Agile Manifesto authors when the discussion was hot. And he refuses to work the traditional way.
That there are projects where teams feel under pressure is no news. In fact, stress-related to pressure is a very common problem in software teams. However, sometimes the situation goes too far and turns into a toxic culture. In this episode, we explore what are the signs that the normal “pressure” teams feel is turning into a much more impactful and negative set of patterns.
Featured Book of the Week: Co-Active Coaching by Henry Kimsey-House et al.
As Rachel grew in the coaching role, she felt frustrated by the reactive mindset she saw in leadership. That led her to explore other approaches to help executives understand and benefit from Agile Values and principles.
Rachel is passionate about individual and team growth. She has fostered an environment of collaboration and continuous improvement in the manufacturing, biotech, and software industries. Currently, Rachel is focused on the power of an individual and recently acquired her Leadership and Performance Coaching certification.
Sometimes, the quickest way to get a product out the door is to create a team of contractors and focus on building a product quickly. Or is it? In this episode, we talk about the consequences that can come from building a team of contractors, focusing mostly on speed, but forgetting that a team is much more than a group of individuals. And teams, are really the secret sauce of Scrum
Featured Book of the Week: Scrum: A Pocket Guide by Gunther Verheyen
Simon helps teams effectively use Scrum and an agile mindset to deliver products and services that matter! As a Scrum Master and Professional Scrum Trainer, licensed by Scrum.org, he supports teams and organizations of varying sizes in a wide range of business domains, like automotive, home appliance, energy sector, federal government agency, and insurance.
When teams feel they are under pressure, they tend to focus on “just doing it”. When that happens, they might want to skip refinement, and other ceremonies (e.g. retrospectives), which then leads to problems. In this episode, we talk about those pressures, where they come from, and what Scrum Masters can do to help those teams.
Featured Book of the Week: Flow by Mihaly Csikszentmihalyi
Sometimes the perspective of the tester can be different from the team’s perspective when it comes to a bug or defect. When that difference of perspective exists, a conflict might arise. In this episode, we talk about how to bring the testers and developers to a common understanding on how to improve quality and avoid conflicts that escalate and can destroy a team.
Featured Book of the Week: Agile Testing by Janet Gregory, Lisa Crispin
In this segment, we refer to the concept of exploratory testing, a critical concept for Agile testers.
About Julio de Lima
Julio is a Principal QA Engineer working for Capco that believes in the Culture of QA. He has been sharing professional insights and experiences on a daily basis and has more than 4500 students in his 4 online courses. In 2020, he was elected the Brazilian Testing reference practitioner.
In this organization, each developer was assigned an application or component. The catch? Each of those applications was critical for the company’s business. Soon enough, this became a problem. Sjoerd shares with us how he tried to help this company eliminate their “bus factor”, and the important lessons he learned about how not to do it.
Featured Book of the Week: The Culture Code by Daniel Coyle
In The Culture Code by Daniel Coyle, Sjoerd learned how important non-work related aspects are for forming a great team. The book shares what are the aspects that are associated with great teams, and highlights how culture and team-culture are critical for the success of a team.
About Sjoerd Nijland
Sjoerd is a founder of Serious Scrum, and creator of the Road to Mastery co-creative online training. Previously E-commerce manager at Bugaboo, and then Manager of Operations at Digital Agency Triggerfish.
A team Oskar worked with, was complaining about the meetings and wanted to stop some of those. Over time, the team members started not showing up, or showing up and not participating actively in the meeting. As the team was delivering, no one else saw this was a problem, but Oskar knew that this was not a team, it was just a group of individuals. In this episode, we talk about how to motivate a team and the importance of having a Vision that brings the team members together.
Oskar is a former software developer who became a passionate agile coach and Scrum master. He did so mainly because he was better at helping teams working together than building software. He loves experiments and questioning the status quo. He is passionate about helping teams build digital products and deliver value continuously.
One of the worst anti-patterns to deal with as a Scrum Master is the disengaged team. And there are many possible reasons for that anti-pattern. One example is when a team is not allowed space for learning, and necessarily failing some times. Or if the team members are mostly introverts, and there’s no space for them to express their contribution.
Scrum Masters must learn to create space for those team members to express themselves and help the team.
Featured Book of the Week: Agile Estimating and Planning by Mike Cohn
Each Scrum Master journey is a path, and each step has a different focus and a different book that makes an impact. Stefania shares how Agile Estimating and Planning by Mike Cohn was one of those books, and how later she discovered and learned from the NoEstimates book when she was in a different phase of her journey.
About Stefania Marinelli
Stefania is an Agile Manager @Hotels.com (Expedia group) former Scrum Master, former team leader/project manager, former developer. Stefania is fascinated by people dynamics and works every day to create a collaborative and safe environment. NVC practitioner.
Sometimes, when team members leave the team, the ones that stay behind have a lot to deal with. The uncertainty caused by team members that leave can lead to negative anti-patterns. In this episode, we discuss some of the actions Scrum Masters can take to take care of the team, even when some of the team members are leaving.
Featured Book of the Week: Crucial Conversations by Patterson et al.
Anu is a software tester turned Scrum master. She worked as Software QA in India for 6 years and then moved to Berlin to complete her Masters in Business Administration. She has been working as a Scrum Master for 3 years in an agency and has learned, first hand, the challenges of working with Agile in an agency.
When we start out as a Scrum Master we might not yet be able to detect the anti-patterns that may develop in teams. That lack of experience can turn against us. One anti-pattern that emerges over and over again is that of the “hero”. In this episode, we explore what leads people to assume the “hero” role and how that negatively affects the team.