This book is meant for software team leaders, architects and anyone with a leadership role in the software business.

• You can also SUBMIT YOUR OWN NOTE to appear inside this book.

Read advice from real team leaders, consultants and everyday gurus of management.

These include, among others, Johanna Rothman, Uncle Bob Martin, Patrik Kua and many others. Each with their own little story and reason to say just one thing that matters the most to them about leading teams.

See what it'll feel like if you do things wrong, and what you can do about things that might go wrong, before they happen.

• I Elastic Leadership
• 1 The Team Leader Manifesto
• 1.1 Why should you care?
• 1.2 Don’t be afraid to become management
• 1.3 The Team Leader Manifesto
• 1.4 Next Up
• 2 Elastic Leadership
• 2.1 The role of the team leader
• 2.2 Growth through challenge
• 2.3 What if it’s ‘Crunch Time’?
• 2.4 Sometimes, Challenges don’t make sense
• 2.5 Conflicting leadership styles
• 2.6 Command and control
• 2.7 Coach
• 2.8 Facilitator
• 2.9 The three team phases
• 2.10 When does a team move between phases?
• 2.11 Next Up
• II The Survival Phase
• 3 Survival Mode
• 3.1 Are you in survival mode?
• 4 Getting out of Survival Mode
• 4.1 Making Slack Time - Required Actions
• 4.2 Making Slack Time - Required Mindset
• 4.3 Command & Control leadership
• 4.4 During transformation you will likely need to..
• 4.5 Starting to learn
• III The Learning Phase
• 5 Learning To Learn
• 5.1 Embrace Ravines
• 5.2 Challenging your team into ravines
• 6 Commitment Language
• 6.1 What does non-commitment sound like?
• 6.2 What does commitment sound like?
• 6.3 What does commitment feel like?
• 6.4 Commit to things under your control
• 6.5 Turn an impossible commitment into a possible one
• 6.6 So how do I get them on board?
• 6.7 What if they fail their commitments?
• 6.8 Gotchas
• 6.9 Where to use this language
• 6.10 What’s next?
• 7 Growing People
• 7.1 What are you going to do about it?
• 7.2 When to use Problem Challenging
• 7.3 Don’t punish for failure
• 7.4 On the road to Personal Growth
• 7.5 Pace yourself and your team
• 7.6 Do you have enough learning time to make this mistake?
• 7.7 Are there situations where you should not grow people?
• 7.8 Next Steps
• IV The Self Organization Phase
• 8 Self Organization through Clearing
• 8.1 What is integrity again?
• 9 Influence Patterns
• V Notes to a software team leader
• 10 It’s probably not a technical problem - Bill Walters
• 11 Review the code - Robert C. Martin (Uncle Bob)
• 12 Document Your Air, Food, and Water - Travis Illig
• 13 Appraisals and Agile Don’t Play Nicely - Gary Reynolds
• 14 Leading Through Learning: The Responsibilities of a Team Leader - Cory Foy
• 15 Change your mind: your product is your team - Jose Ramón Diaz
• 16 Leadership and the mature team - Mike Burrows
• 17 Spread your workload - John Hill
• 18 Making your team manage their own work - Lior Friedman
• 19 Go see, ask why, show respect - Horia SluÅŸanschi
• 20 Keep developers happy, reap high-quality work - Derek Slawson
• 21 Stop doing their work - Brian Dishaw
• 22 Write code, but not too much - Patrick Kua
• 23 Evolving from manager to leader - Tricia Broderick
• 24 Affecting the pace of change - Tom Howlett
• 25 Proximity Management - Jurgen Appelo
• 26 Babel Fish - Gil Zilberfeld
• 27 Creating Team Trust - Johanna Rothman