Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
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
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top customer reviews
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.
I would recommend this book to any developer who has been pushed into a leadership no matter what the size of the team.
But, I somehow feel it represents a rather "old-style" leadership. That might be all good, but I found reading Ed Catmull's Creativity Inc. and David Marquet's Turn the Ship Around more inspirational. Go read those instead :-)
The book is split into two parts: The book and the articles or blog posts. Half of the book is the actual book (only about 100 pages) and the other half is articles or blog posts collected by the author. The articles cover a very wide range of topics. Part #1 of the book consists of 4 sections: 1) Elastic Leadership, 2) The Survival Phase, 3) The Learning Phase, and 4) The Self-Organizing Phase.
The Elastic Leadership section sets the tone and structure of the book by stating that leadership is situational and that it depends on the state of the team. The experience of the author is that teams go through 3 different phases, unsurprisingly: 1) Survival, 2) Learning, 3) Self-organizing, each having a section with one or more chapters related to the leaders role when the team is in that phase. The survival phase is when there is panic and no time to learn. The learning phase is when the team gradually learns to solve their own problems and the self-organizing phase is where the team is able to solve problems without your help. The author state that maybe 5% of the teams are in the self-organizing phase and the majority in the survival.
He then goes on to explain the kind of leadership style you ought to use for each of these phases. For the survival phase the main leadership style is command control, for learning phase it is more a coaching style, and for self-organizing more a facilitation style (not black/white). Each chapter explains a couple of techniques and ideas for teams in that phase. Though, the majority of the book (almost 40%) focuses on the learning phase.
Roy has some great ideas and some good stories to share, yet I was uncomfortable with some of his advise and the tone of the book. I've experienced a lot of teams, but the 3 phases do not really match my experience. Neither does the style link well to the describes phases. If you have a team in survival then there might not be time for learning, but if you can get them goal and purpose then I don't believe you must survive by applying command control management. But I was most uncomfortable with the commitment language. Adding precision in language when there is often no precision in the task doesn't feel right to me. And most organizations don't need more focus on commitments, but more focus on delivery. Anyways.
All in all, the book is not bad, yet I wouldn't recommend it. It is small and doesn't contain a huge amount of new information. I'd probably do 3 stars for the book itself, but will reduce a start because of the random collection of articles towards the end of the book. 2 stars.
Most recent customer reviews
It will give you tips on how to move from the survival phase to the self...Read more