Inspiring and Cautionary Tales from Veteran Team Leaders
Please login to add notes
- Praise for Beautiful Teams
- + Why Beautiful Teams?
- + Preface
- Part One
- + Why Ugly Teams Win
- Building Video Games
- Building the Perfect Team
- What Makes Developers Tick
- Inspiring People
Bringing the Music Industry into the 21st Century
- A New Project, A New Team
- A Calculated Risk...
- Gentlemen, Start Your Rippers…
- The Final Month
- I Am So Smart: S-M-R-T...S-M-A-R-T
- Engineering Department Smokes a Collective Cigarette
- Intermission: The Founding of a Panda Preserve
- “You Realists Can Stay the Hell Out of Our Office!”
- Not with a Bang, But with a Whimper...
- Inner Source
- Part Two
- Creating Team Cultures
- Putting the “I” in Failure
- The Copyfighters Take Mordor
- Defending the Free World
- Saving Lives
- Part Three
Building a Team with Collaboration and Learning
- Selling Management
- Getting Started
- Growing the Team
- Pressing the Envelope and the Process Police
- Requirements Versus On-Site Customer
- + Trouble in River City
- Companies Make Their Own Troubles
- Future Projects
- Collaboration Success Factors
- Better Practices
Memories of TRW’s Software Productivity Project
- Background on the Software Productivity Project
- + Making the Project a Reality
- The Team
- The Challenge
- Educating the Boss
- Can We Have a Private Office?
- Choice in Technologies: The Importance of Trade Studies
- Converting the “Guinea Pig” Project
- Users Should Be Part of the Team
- Making All Inclusive
- Training Managers, Not Your Usual Student
- Tasting Our Own Cooking
- Is Email a Boost or a Hindrance?
- Becoming Word Processors
- The Difficulties of Innovation, Timing, and Commercialization
- The Iron Law of Software Maintenance
- The Challenges of the Rapid Change of Technology
- Learning and Assimilating Changes in User Behavior
- Building Spaceships
Succeeding with Requirements
- The Setting
- The Cast
- Prologue: Paul Is in a Pickle
- + Act I: Girding Our Loins
- + Act II: Use Cases, Schmuse Cases
- + Act III: Look Over My Shoulder
- Epilogue: Let’s Eat!
- Coda: Then What Happened?
- Useful References
- Development at Google
Teams and Tools
- Research Teams
- + The HADS Team
- Part Four
- Bad Boss
- Welcome to the Process
- Getting Past Obstacles
Speed Versus Quality
- How Did We Get Here?
- About the Team
- Becoming Part of the Team
- Starting Off Right
- Solving Problems As a Team
- What Code Review Looked Like
- Unit Tests
- Status Reports
- Go Faster Now!
- Looking for More Speed
- Losing a Week at a Time
- What to Do Next
- Retaining Integrity
- The Rubber Meets the Road
- Success at Last
Tight, Isn’t It?
- Only Pawn...in Game of Life, or “What’s a Dazzling Urbanite Like You Doing in a Rustic Settin...
- CMM Level Subzero, or “Processes, We Don’t Need No Stinking Processes!”
- The Brown Hole, or “I’d Say You’ve Had Enough”
- Some of These Envelopes Contain Stock Options, or “I’m Through Being Mr. Goodbar, the Time Has Co...
- The Blitz, or “Break’s Over, Boys, Don’t Just Lie There Gettin’ a Suntan...”
- Our Invite to the Number Six Dance, or “What Is It That’s Not Exactly Water and It Ain’t Exactly ...
- Epilogue, or “Nowhere Special...I Always Wanted to Go There”
- Inside and Outside the Box
- + Compiling the Voice of a Team
- Part Five
- Producing Music
What's it like to work on a great software development team facing an impossible problem? How do you build an effective team? Can a group of people who don't get along still build good software? How does a team leader keep everyone on track when the stakes are high and the schedule is tight?
Beautiful Teams takes you behind the scenes with some of the most interesting teams in software engineering history. You'll learn from veteran team leaders' successes and failures, told through a series of engaging personal stories -- and interviews -- by leading programmers, architects, project managers, and thought leaders.
This book includes contributions from:
Barry Boehm and Maria H. Penedo
Karl E. Wiegers
Mark Denovich and Eric Renkey
Beautiful Teams is edited by Andrew Stellman and Jennifer Greene, veteran software engineers and project managers who have been writing bestselling books for O'Reilly since 2005, including Applied Software Project Management, Head First PMP, and Head First C#.
Test the closed alpha on paperc.com