This book is for software engineers who have been entrusted to lead their teams but haven’t received a guide on how to do this.
It’s perfect for engineering teams of 3-8 people in small startups, where the structure of startups is flat with at most 3 levels: developers, leads, and C-level executives.
Why this eBook?
In the book, I share the most useful knowledge, mistakes, tools, and techniques that I’ve acquired working as a Team Lead and Head of Department in a small consulting workshop, large telecom company, Hong Kong, and Silicon Valley startups.
We are given to lead a team in the hope that we will cope, but we do not always have answers to questions on how to motivate, arguing, build processes, and achieve goals. Being a leader means finding answers to many of these questions.
I did not have such answers when I started and was disappointed in myself because I didn't justify the expectations of the team leader assigned to me. I didn't understand what I was doing wrong.
This book is an attempt to answer all the basic questions that a novice team leader may have.
I put my efforts to disclose topics simply, short, and to the point, so you can acquire them in less time. This book is just 106 pages long and will take two evenings to read the book.
Read sample chapters. No email required.
Here’s what people have said about ‘Team Lead 101’"I have read only half of the book and already realized how sad it is that I didn't have it 4 years ago when I was told that I'm tech lead! ... This book is a must-have [for tech-leads] ... Exactly what you need in small startups."
"I like how the book is written. It is easy to read without complicated terminology. I think not only team leads find this book useful but SCRUM masters and agile coaches."
Table of Contents
1. Becoming a Team Lead
1.1 What a Good Team Lead Does and Doesn’t Do
1.2 How Much Does a Team Lead Code?
1.3 Macro- and Micro-Management
1.4 Importance of Routine
2.1 Teammate Cards
2.2 1:1 Meetings
2.4 Effective Meetings
2.5 Agile Board
2.7 Planning Poker
2.8 Pair Programming
2.9 Document Processes
2.10 Team Journaling
3.1 Five Stages of a Team
3.3 Nothing is Possible Without Belief
3.4 Clarity of Goals, Roles, and Values
3.5 How to Argue
3.6 Happiness Drives Success
3.7 Constructive Criticism and Influence
3.8 Strict but Fair
3.9 Purposeful Improvement
3.10 Healthy Stress
4. Achieving Goals
4.1 First Mistakes
4.2 Empower Developers
4.3 Code Review Time
4.4 Deep Work Time
4.5 Team Productivity
5. Increase Your Productivity
5.1 Establish a Base
5.2 Schedule Must-Do Activities
5.3 Schedule Productive Activities
5.4 Fix Broken-Up Days
5.5 Execute and Measure
5.6 Analyze and Repeat
6. Technical Interviews
6.1 Take-Home Challenge
6.2 Code Review Challenge
6.3 Pair Programming Challenge
6.4 Assess the Candidate Through Their Best Code
What if I didn't like the book?
No worries! If you didn’t like the book, reply to the download email within 30 days from the purchase, and you'll get a full refund. No questions asked.
Can I share this book with my team?
You cannot share an individual (single copy) purchase with others. However, you can buy a shareable team license version. The team license version can be shared with an unlimited number of people within a single team, class, or organization.
You've purchased this product
See it in your libraryView in Library
We charged your card and sent you a receipt
You'll need an account to access this in our app. Please create a password to continue.
Download from the App Store or text yourself a link to the app
Thank you for purchasing my book!
If you have questions about the book you can contact me at firstname.lastname@example.org
Or say Hi on Twitter https://twitter.com/iamdidev
Good news! Since you already have a Gumroad account, it's also been added to your library.