Memoirs of a Software Team Leader
Minimum price
Suggested price

Memoirs of a Software Team Leader

About the Book

I've been working hard to create something that would help me to preserve my experience from being a software team leader. Quite naturally, I realized it's a good opportunity to share knowledge with other team leaders and developers. This is how my book came into existence.

What makes it interesting is that there are many IT management books available, yet most of them are tailored to match perspective other than technical team leader's. I decided to fill this gap.

Becoming a software team leader was both a pleasant and challenging experience. I had been trying to find a book that could help me to become a better leader, but all I found were excerpts. I had to extrapolate my experience as a team member, recall what had worked well and what hadn't and try to figure out my own leadership style. Luckily, I was cooperating with clever people, eager to try new things out; it was a perfect proving ground and I think I seized the opportunity well, though it took me a while to draw some of the conclusions. By reading the book, you can save yourself the trouble, learn my knowledge and begin putting it into practice within hours.

Are you a team leader? I think I can surprise you. Do you want to become a leader? Great, by learning from my experience you'll be better since the day one!

By reading the book, you'll learn how to:

  • Select the right iteration length
  • Deal with a problematic customer
  • Make sure that what the customer asks for is doable
  • Decompose requirements into small, comprehensible tasks
  • Visualize task dependencies
  • Do code review
  • Deliver working code at the end of each iteration
  • Make sure you did what the customer wanted
  • Learn by mistakes and improve
  • Become a good leader
  • Make the right decisions
  • Resolve conflicts
  • Form a balanced team
  • Keep your team in a good shape
  • Coordinate actions as to maximize parallelism
  • Communicate with people outside of your team
  • Deploy and maintain software
  • Hire the right developers
  • And more…

About the Author

Łukasz Wróbel
Łukasz Wróbel

Leader, manager and software architect. Interested in designing efficient and scalable web applications, creating high-quality software and exploring the motives of human actions.

Always in pursuit of knowledge, willingly sharing the results:

Table of Contents

  • 1. Introduction
    • Who is this book for?
    • Who wrote it?
    • My services
    • Chapter layout
    • Meet the team
    • Disclaimer
  • 2. The Circle of Life
    • The iterative and agile approaches
    • Iteration length
    • Steps
  • 3. Step I: Requirements Gathering
    • Meet the customer
    • Meeting
    • Loyal advisor
    • Problematic customer
    • The perfect customer
    • After the meeting
  • 4. Step II: Analysis
    • Technical questions
    • Conceptual questions
  • 5. Step III: Decomposition
    • Initial information
    • UML diagram
    • Separation
    • Task size
    • Task types
      • Controversy
    • Dependencies
      • Visualization
      • Raw order
  • 6. Step IV: Planning
    • Communication overhead
    • Iterative planning
    • Task management software
  • 7. Step V: Catching a Breath
    • Strategic thinking
    • We have a problem!
  • 8. Step VI: Integration
    • Quality assurance
    • Code review
      • Before or after tests?
      • Changesets
      • Complexity
      • Bottleneck
    • Troublesome tasks
  • 9. Step VII: Final Testing
  • 10. Step VIII: Verifying Requirements Are Met
    • Possible outcomes
  • 11. Step IX: Lessons Learned
    • Technical
    • Communication
    • Personal
    • Feedback processing
    • Higher level
    • The circle is now complete
  • 12. Leadership
    • In a nutshell
      • Know your stuff
      • Know your staff
      • Don’t be a jerk
      • Don’t be weak
    • Hands-on or hands-off?
    • Delegate!
    • Getting real
    • Decision making
    • Resolving conflicts
  • 13. Team
    • Versatility
    • Irreplaceable people
    • Time to say goodbye
    • New members
    • Team player’s traits
    • Good and mediocre developers
    • Motivation
    • Celebration
  • 14. Team Coordination
    • Daily meetings
    • Core hours
    • Version control
      • Relevant commit messages
      • Frequent committing
      • Frequent updating
      • Explicit changeset
      • Single change, single commit
      • Substantial changes only
    • Unit tests as a glue
      • Stubbing
      • Mocking
    • Outside the team
      • Half-witted code
      • Communication channels
      • The least surprise
  • 15. Product Life Cycle
    • Deployment
      • You need a plan
      • Premature deployment
      • Documentation
    • Maintenance
      • Bugs
      • Changes
      • Code quality
    • Continuous integration
  • 16. Developer Recruitment
    • My approach
    • Five common mistakes
      • Lack of self-confidence
      • Too much self-confidence
      • Lack of cooperation
      • Aura of mystery
      • I’ve read about it
    • Selection tests
  • 17. Final Thoughts
    • What should you do now?
    • My prize

The Leanpub 60 Day 100% Happiness Guarantee

Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.

You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!

So, there's no reason not to click the Add to Cart button, is there?

See full terms...

80% Royalties. Earn $16 on a $20 book.

We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.

(Yes, some authors have already earned much more than that on Leanpub.)

In fact, authors have earnedover $13 millionwriting, publishing and selling on Leanpub.

Learn more about writing on Leanpub

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

Learn more about writing on Leanpub