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