The casual reader of HR websites and journals may think that bonuses, and their methods/systems are a very important part of keeping a workforce motivated. They do have an impact, but it is not always as we expect it to happen. In this episode we discuss the type of bonus systems that can easily destroy the productivity of a software organization, and how important it is to pay attention to the “unexpected consequences” that some bonus systems bring with them.
About Lynoure Braakman
Lynoure has worked in many roles in the IT, from operations, scrum mastering and requirements analysis to programming, even a little as a tester. She’s worked in agile teams since 2000 and loves being an adapter type, bringing in a wider perspective into her projects and to help different types of personalities to work together.
On Friday’s we usually discuss system conditions. This episode is no exception, however we also take a look at a method to identify those system conditions before they cause major problems for the teams. We discuss the Spotify Squad Health Check as a method to survey the teams and identify possible impacts that need to be further investigated and mapped to system conditions. This is especially important when companies are growing fast, and we need to keep an eye on what problems might emerge as a result.
About Kathy Andersen
Kathy works as a Scrum Master with a team implementing a billing management system for a company called Hudl. Hudl is headquartered in Lincoln, Nebraska and provides video review and performance analysis tools for coaches and athletes to review game footage and improve team play. Kathy took an uncommon route to the software world, and since then she has had the luck of working on a diverse set of projects and teams. You’ll find her speaking at conferences and participating in the agile community.
When working with teams, we often face bottlenecks. Points in the process that slow everything down. Those bottlenecks are where we should focus our attention if we want to help our team deliver more and faster. For that to happen we need to understand where those bottlenecks come from, and that’s why it is so important to understand the system conditions in play. Bottlenecks are caused by system conditions.
About Umer Saeed
Umer is a Scrum Master, joining us from London, UK, currently working for one of the largest TV broadcasters in the UK, ITV. He has 5 years experience working in Agile environments spanning across Sports, Broadcasting, Travel and Publishing.
Sometimes, with the best of intentions, we create policies that actively detract from the team’s ability to deliver. Jeff shares with us such a story, where the team was not able to deliver their product to production. They needed some other team in the loop. That created communication problems, delays and did not help the team deliver more, or better.
This happens when we solve symptoms, not problems. In this episode we explore this story, and how to avoid getting stuck in the symptoms. If we want to help teams we must focus on the real problem, the root causes!
About Jeff Maleski
Jeff is passionate about working with and building up both individuals and teams using ideas from Jurgen Appelo’s Management 3.0 and Dan Pink’s Drive. When leading project teams, Jeff strives for empirical based planning and forecasting, continuous learning, and delivering high quality software products that exceed expectations. Jeff believes in leading by actions and focusing on building relationships with others.
Nobody gets credit for solving problems that never happened is a paper that explores why the tools that are the reason for success in some companies are ineffective in other companies. And when that happens, people in those organizations have the tendency to work even harder. But is that enough?
In this episode we explore the idea that working harder may be an anti-pattern, and we explore the impact of a simple question: “why?” Go deeper, ask why.
About Lucas Smith
Lucas has been a developer, manager, and agile coach and trainer with Boeing. Currently works a Professional Scrum Trainer with Scrum.org and is the owner of LitheWorks. Lucas enjoys helping people and organizations improve the way they work to be more creative, effective, and efficient.
One of the least spoken about system conditions is the deep belief that “more is better”. Many organisations make decisions and organize their work based on that model: more features = more success for the product. But is it really like that?
Looking at the system conditions also means understanding what are the deeply held beliefs that the organisation acts on, and shape its ways working.
About Jeff Bubolz
Jeff is a speaker, trainer, and agile coach. He has been a Product Owner, Scrum Master and Development Team member. Jeff has worked with enterprise companies to small start-ups. His goal is to end human suffering in organizations, by nudging people to be the change they want to see in the world.
In many organizations, especially late majority companies, the Agile adoption is often overwhelmed with a tool change. Instead of adoption Agile, we adopt JIRA or SAFe, or Scrum, or Kanban. All of those are forms of tools (entities we use to achieve something else).
When we work with organizations, we need to keep an eye out for this anti-pattern, as it detracts from the real adoption of Agile as a way of working, a mindset and a set of orienting values and principles.
In this episode we talk about how to overcome the tool-fetish anti-pattern that many organizations enter when they start their Agile adoption.
About Daniel Hooman
Agile coach from Scrum Data since 2010. Daniel comes from a strong Business intelligence background. He is passionate about large scale product development, organisational structure and culture, being idealistic pragmatist, framework agnostic.
No surprise in that title, hein? I guess not. But this is an aspect very often ignored by manager, team members and, unfortunately, also by us, the Scrum Masters. In this episode we discuss anti-patterns (estimation as an anti-pattern, with references to #NoEstimates hashtag on twitter and the #NoEstimates book), but also dive deeper into what Systems Thinking is, and how it can help us navigate the complex organizational anti-patterns we need to be aware of, and deal with.
Chad’s first experience with Scrum was in 2005 on a global team responsible for consolidating financial software. After some dark days of death march projects, he left his traditional business analyst and project manager roles behind. He is now consulting organizations as an external change agent and organizational agility advisor.
Systems, the collection of all the stakeholders and actors, that we work within are not always aligned. A common anti-pattern is when only part of the company is on board with Agile. What happens then? We need to be aware of our supporters, our detractors and the “on-the-fence” stakeholders we need to work with.
In this episode we discuss such a story, and how we – Scrum Masters – can understand and react to those challenges.
About Heidi Araya
Heidi is an Agile coach who has been working with remote teams since 1999. She aims to show teams and enterprises the value of a cohesive vision and mission, systems thinking, and self-organizing teams. An active member of the Agile community, she trains and speaks at events and conferences worldwide.
When teams, and organizations grow in size they suffer from totally different problems from when they were smaller. That’s to be expected. However, we often react by “doubling down” on what worked before, even if that is not the best approach. Felix shares a story of a growing organization, and the struggles they went through to be able to cope with that growth.
Felix likes to bring out the best in as many people as possible by providing an environment in which people can sustainably thrive. After his Bachelor in Computer Science he wanted to develop people rather than software. He also is part of 12min.me, a movement for inspiring people.