Roy Osherove - Elastic Leadership: Growing Self-Organizing Teams

For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact

2017 by Manning Publications Co. All rights reserved.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher.

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps.

Recognizing the importance of preserving what has been written, it is Mannings policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled and processed without the use of elemental chlorine.

Manning Publications Co.20 Baldwin RoadPO Box 761Shelter Island, NY 11964

ISBN 9781617293085

Printed in the United States of America

1 2 3 4 5 6 7 8 9 10 EBM 21 20 19 18 17 16

To Tal, Itamar, Aviv, and Ido: my family.

Youve taught me about listening, challenging, and growing.

There are no experts. There is only us.

These two simple sentences always make me feel lonely. They were uttered by Jeremy D. Miller, a software developer and architect Ive come to appreciate over the years. These sentences give me the feeling that theres nobody else to turn tothat I have to start trusting my own instincts, and that whoever tells you they are an expert is either lying or wrong.

During my career, which consists of almost two decades in the IT business as of the time of this writing, Ive come to realize that There are no experts. There is only us is very true. During one of my first jobs as a programmer, I joined a team working on a government project (the project was all in Visual Basic 6.0). The team, including my team leader, had no idea what they were doing, but because I also didnt know what I was doing, I assumed that whatever people were doing was the right way to do it.

As time went by, I began to read books about how software development could work, including The Mythical Man-Month by Fred Brooks (University of North Carolina at Chapel Hill, 1974) and Peopleware by Tom DeMarco and Timothy Lister (Dorset House Publishing, 1987). I looked around and recognized all the problems those books were talking about right there in front of me.

But nobody around me said anything about the crap we were building or the crap we were taking from our managers and customers, and certainly nobody said anything about the crap we were giving to our customers and managersthere was only silence. Nobody was talking about careless, helpless programmers. Everything was fine. To paraphrase (and counter) a famous saying by comedian Louis C.K., Everything was crappy, and nobody cared.

These were good people. Some were my friends, and they didnt intend to do any harm. We were doing our best, in the same way ants do their best to vanquish raindrops along their path to the anthill. But we werent looking up. We werent trying to understand and predict why the rain fell or where it falls from. We didnt plan better ways to get to the anthill, and we didnt get better raincoats to protect ourselves from the rain (OK, ant raincoats are a sign this analogy is breaking down, so Ill stop).

We were all just there, doing our ant-like jobs. Project late? Sure; thats life. Quality is lousy? Sure; thats life. Debugging until 3 a.m.? Sure; thats normal.

Was I the only one reading books? No. There werent many trade books, but there were some. But the books my coworkers were reading werent getting them anywhere; or if the books had the potential to help them, maybe they couldnt find the time to finish the books and get there.

There was no sense of craftsmanship. But there was also no sense of professionalism. There were just big downward spirals for every project, as far as the eye could see.

This workplace wasnt unique, by any means. I encountered many companies like this, with variations, over the years. I hate working at places like that; I always want to make a difference.

This book is about making a difference and getting other people to make a difference as well. Its the book for those who feel hopelessly trapped in their jobs, even though theyre architects, scrum masters, team leaders, or senior developers. Its the book I wish Id had when I first became a team leader.

The book started out as a passionate blog that I kept over several years at 5whys.com (now ElasticLeadership.com). At some point, I collected all the blog posts and published them in a self-published book at leanpub.com titled Notes to a Software Team Leader. When Manning offered to publish it a couple of years later, I jumped at the chance to revise and add content to the book and publish it with the same company that helped publish my first book, The Art of Unit Testing. Id like to thank Manning for helping me publish this new edition of Notes to a Software Team Leader, now titled Elastic Leadership and with a new format and new and updated content.

Id like to thank Kevlin Henney for coming up with the idea for the original title of this book, which was Notes to a Software Team Leader. Later I changed the title because the book now included more than just notes, but that spirit remains in the second part of the book. You can reach Kevlin at www.curbralan.com.

Thank you, early beta reviewers of this books original digital editionespecially Ofer Zelig, Leif Eric Fredheim, Mauricio Diazorlich, and Eric Potterfor providing many insightful and helpful ideas and corrections.

A big thank goes you to the early purchasers of this book when it was still in its infancy at leanpub.com, before it was picked up by Manning. They are the reason this book was finished. And thank you leanpub.com for showing another way to write a book in a lean/agile way.

Thank you, the people at Manning: publisher Marjan Bace and everyone on the editorial and production teams, including Janet Vail, Mary Piergies, Tiffany Taylor, Dottie Marsico, Sean Gillhoolley, Katie Tennant, and many others who worked behind the scenes.

Finally, thanks go to the amazing group of technical peer reviewers led by Ozren Harlovic: Matt Belanger, Jeroen Benckhuijsen, Art Bergquist, Ali Berkol, Alessandro Campeis, Maria Gemini, Karl Geoghegan, Christopher Haupt, Andy Kirsch, Edgar Knapp, Antti Koivisto, Shaun Lippy, Sune Lomholt, Ashwin Mhatre, Tim Moore, Ferdinando Santa-croce, Jonathan Sharley, Ivo timac, and Ian de Villiers.