Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
Notes to a Software Team Leader: Growing Self Organizing Teams Paperback – August 30, 2013
Frequently Bought Together
Customers Who Bought This Item Also Bought
Top Customer Reviews
The book is spot on when it says "Most of us weren't taught how to do this type of work." We want to be good at it. Our teams and our software are depending on us being able to lead. This book provides advice for ever team leader on how to become a better leader. It gives practical and useful ideas about how to manage your time and efforts as well as how to interact with others.
One of the key themes in the book is learning. As a team leader you need to learn to be better in your role. A key facet of that is facilitating ways for your team to grow. The book examines how you can improve in these areas.
The book concludes with a series of essays from thought leaders in the software industry. Each other tells what they would like to say to someone who is brand new in a software team leadership position.
I was very pleased with the book. The information was useful and applicable. I am better equipped to do my job for having read it.
The second part of the book consists of contributions by other authors. Instead of being directly related to the first part, their short notes take different, often thought provoking, aspects to the job of a team leader: usually presenting a potential issue and giving a suggestion how to solve it. They are a nice extension to the core book and give a lot of value on their own as well.
I can definitely recommend reading the book to any team leader, no matter how much experience he already has in his job. Even if you don't agree with everything, I'm pretty sure the book will act as an eye opener and make you more aware of stuff you already take for granted, although there might still be opportunities for improvement. You never know, it might even make you a better leader.
His style helped "Notes to a Software Team Leader" deliver its message very well. He wrote about his own experiences, and what worked for him. He wrote about real things that happened to real people.
"Notes to a Software Team Leader" provided a way of looking at how a team works by dividing the states of a team into phases. It then offered practical advice on how to identify those phases. Then it expanded by offering ideas on how a team leader can help a team transition from one phase to the next. This included advice on how a team leader would need to transition as well.
The section on commitment language was especially useful for me. It put into words some practices I was having a hard time conveying to other people. That alone made the book well worth the time to read.
There are few books I recommend to people. This book is joining that list.
The only reason I give it 4 and not 5 stars is that the second part of the book can get a little repetitive, since, as I said, apparently pretty much everyone has pretty much the same problems. It is interesting to see how different people approach them, though, so it's worth the read.
The one star is for filling the 2nd half of the book with dreck. The collected writings are blog post quality, thematically jump all over the place and some had a advertisement feel to them.
Notes to a Software Team Leader is about stepping up and leading your own team. Leading, not bossing. It's about understanding its strengths and weaknesses and getting its members to grow. It's about realizing what phase the team is in and taking the proper decisions in the short term, aiming, in the mid-long term, to grant it time to learn and get better.
The book is divided into two parts: in the first, the author shares with the readers his experiences and thoughts; the second is a collection of short advices written by other people, each providing a guideline, an insight.
Again, it's not that I do not agree with the author. I didn't get entertained. I didn't write down a single note (well, this is a lie. I've taken down one. See below). I didn't add it to my favorite books. I don't feel that reading this book resulted in adding value.
So, it was not completely true to say I did not write down anything from this title. This is the only sentence that got to my soul:
People who come across my path, even for a short time, will get the same amount of respect, expectations, and challenge from me as if they had been there forever. I try to always leave people whom I've led better off than they were... It's my personal integrity to do so.Read more ›
Most Recent Customer Reviews
The essays at the end are the best part, the rest is just basics and wasn't as worthwhile to me.Published 9 months ago by John Graham
Definitely recommend this book. Great set of real world examples, that I could totally relate to. At the end, the author has invited other writers who are experts on this topic -... Read morePublished 14 months ago by Rahul Thathoo
Great book with good management techniques and ideas. My only complaint is the poor editing (spelling errors etc.).Published 19 months ago by Ronald G. Ifferte
I was initially skeptical about the book - I was a fan of Roy’s Art of Unit Testing book, but wasn’t sure if his writing would translate to soft skills space. Read morePublished 20 months ago by Mark Pearl
Well written, easy read. Good content.
But, I somehow feel it represents a rather "old-style" leadership. Read more
I deeply inspired by Roy's ideas.Perfect book. Recommended for SW team leaders - both beginners and experienced one.Published 23 months ago by michael bogachek
This book is very inspiring. It gives so many useful recipes to let the team learn how to learn.
It will give you tips on how to move from the survival phase to the self... Read more
Put things into perspective for me at a time when I didn't know whether I was floundering, or if everyone was kicking butt.Published on May 4, 2014 by Angel Abundez