Lynoure Braakman and the case of the destructive Bonus System

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.

You can link with Lynoure Braakman on LinkedIn and connect with Lynoure Braakman on Twitter. You can also follow Lynoure Braakman’s blog at: Lynoure.net

Lynoure Braakman Delivering value as the key to Scrum Master success

Scrum Masters work and influence many aspects of an organization or project. However, there’s one overarching concern that we must have in mind at all times: “are we delivering real value to our customers and stakeholders?” Lynoure discusses the importance of focusing on value delivery.

In this episode we also talk about team dynamics and mention The 5 Dysfunctions of a Team by Patrick Lencioni.

Featured Retrospective Format for the Week: Good / Bad / What to change

Sometimes it is the simpler formats of the retrospective that work best. This week we review some of the classic formats (e.g. Good / Bad / What), and how variation in formats may negatively affect the teams we work with.

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.

You can link with Lynoure Braakman on LinkedIn and connect with Lynoure Braakman on Twitter. You can also follow Lynoure Braakman’s blog at: Lynoure.net

Lynoure Braakman on how organizational changes heavily affect team dynamics in software projects

Working with a team is hard enough when the organization is stable and not going through a major upheaval. But when an organization is in massive change, how can we keep teams motivated and engaged with the work? In this episode we discuss the story of a team that was “alone” in the middle of a major organizational change, and what they did to keep the motivation and even going far beyond the call of duty. An inspiring story of how, sometimes, change comes from the team itself!

In this episode we discuss the Agile Fluency Model and refer to Deming’s 14 points for management, a list of points to help transform the role and effectiveness of management.

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.

You can link with Lynoure Braakman on LinkedIn and connect with Lynoure Braakman on Twitter. You can also follow Lynoure Braakman’s blog at: Lynoure.net

Lynoure Braakman on Technical Debt and having the courage to say “no”

Software developers are often put in a position where they need to “enable” some other aspect of the business. After all, software is a tool for businesses. In those cases, developers may be pressured and encouraged to say “yes” without taking into account (or heavily discounting) the effect on the long term maintainability of the code. This need to please management, marketing, sales (wherever the requests might come from) will only be visible much later down the line. In this episode we discuss what we can do to help developers learn to say “no” also.

Featured Book for the Week: Peopleware by Tom DeMarco and Timothy Lister

Peopleware by DeMarco and Lister is one of the classics in the management of software projects niche. Originally published in 1987, the book focuses on the specific aspects that relate to successfully managing a software development team. In this episode we talk about how it helped Lynoure understand what are the factors that influence a team’s productivity.

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.

You can link with Lynoure Braakman on LinkedIn and connect with Lynoure Braakman on Twitter. You can also follow Lynoure Braakman’s blog at: Lynoure.net

Lynoure Braakman on the Scrum vs Kanban debate, and the problems with both

Scrum vs Kanban is a very common debate. Some teams will be adamant that only one of those applies to their context. Whichever you choose, you should be aware of the consequences. In this episode we explore one such process change, and the problems associated.

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.

You can link with Lynoure Braakman on LinkedIn and connect with Lynoure Braakman on Twitter. You can also follow Lynoure Braakman’s blog at: Lynoure.net