Roy describes the two parts of the book – elastic leadership and community contributions featuring notes from team leaders.
K Scott says that our industry often throws developers into leadership positions, and the transition can be difficult. Roy agrees, and says these are the notes he’d wished he had when he was a new leader. Back then he thought he was doing a good job, and was having fun, but wasn’t really doing his job.
Roy talks about how he got started, explaining how his passion is at the crossroads of where people and software meet. This book is coming out because it needs to come out – it’s a missing book.
Different team phases require different leadership types, describing his elastic leadership approach that deals with the three phases he’s observed:
Self organizing team
What are some common mistakes?
Not recognizing which phase your team is in
Being afraid of talking to people about difficult things
Not understanding how to influence behavior
That’s it! Scott runs off to tackle some more lightning round interviews.