Shipping Greatness Practical lessons – nursing homework essays
Shipping Greatness Practical lessons
Shipping Greatness Practical lessons
Shipping Greatness Practical lessons on building and launching outstanding software, learned on the job at Google and Amazon. Shipping Greatness Practical lessons
Chris Vander Mey
Beijing · CamBridge · Farnham · Köln · SeBaStopol · toKyo
Shipping greatneSS by Chris Vander Mey
Copyright © 2012 Chris Vander Mey. All rights reserved. Printed in the United States of America.
Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472.
O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (safari.oreilly.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or corporate@oreilly .com.
ORDER NOW FOR CUSTOMIZED AND ORIGINAL ESSAY PAPERS
Editor: Andy Oram
Production Editors: Iris Febres and Holly Bauer
Copyeditor: Rachel Monaghan
Proofreader: Kiel Van Horn
Cover Designer: Mark Paglietti
Interior Designer: Monica Kamsvaag
Illustrator: Rebecca Demarest
Printing History: August 2012 First Edition.
2012-08-17 First Release.
See http://oreilly.com/catalog/errata.csp?isbn=0636920026341 for release details.
Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Shipping Greatness and related trade dress are trade- marks of O’Reilly Media, Inc.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps.
While every precaution has been taken in the preparation of this book, the publisher and author(s) assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.
preface | v
Part One | the Shipping greatness process 1
1 | How to Build a Great Mission and Strategy 5
2 | How to Define a Great Product 13
3 | How to Build a Great User Experience 41
4 | How to Achieve Project Management Greatness on a Budget 63
5 | How to Do a Great Job Testing 71
6 | How to Measure Greatness 85
7 | How to Have a Great Launch 93
Shipping Greatness Practical lessons
iv | contentS
Part t wO | the Shipping greatness Skills 113
8 | How to Build a Shipping-Ready Team 115
9 | How to Build Great, Shippable Technology 137
10 | How to Be a Great Shipping Communicator 149
11 | How to Make Great Decisions 179
12 | How to Stay a Great Person While Shipping 195
13 | That Was Great; Let’s Do It Again 205
aPPendix a | 10 Principles of Shipping 209
aPPendix B | Essential Artifacts Your Team Needs 211
aPPendix C | References and Further Reading 213
how to Contact Us | 215
Shipping Is greatness Designing, building, and launching the right software is referred to as shipping in the software industry. Shipping software is not packing boxes and it’s not only hosting launch parties. Shipping is finding the right prod- uct, working through a complex and ever-changing process, and doing it quickly. Shipping is one of the few truly new crafts of our century. It’s newer than management because managers have been managing people for a long time. Business execs have been waving their hands at strategy for just as long, if you count stockpiling mammoth bones as inventory control. And marketers have been trying to sell another sprocket or cog since before sprockets and cogs existed. But shipping? Shipping software didn’t exist when you and I were born. Heck, it barely existed when your kids were born, and there are no classes you can take in school that will teach you how to do it.
Shipping software is new, but it’s also incredibly meaningful because it solves many problems. Shipping solves money problems, because your investors are always looking for results before they give you more money. It solves customer problems because the features and fixes your customers need are tied up in your ability to ship. It solves team problems because nothing is better for morale than making progress. If fame, fortune, and the pursuit of happiness are the question, shipping great software is the answer.
If you can ship, you can make nearly any software business success- ful, and you can compete with businesses that have deeper pockets be- cause you can get to market faster. But if you screw it up—by missing your date, by launching a product nobody cares about, or by building a beautiful product that nobody hears about—your team will be grumpy, customers will write to the Big Boss, and best case, you don’t get promoted. Worst case, the next project on which you and your team work will involve résumé polishing. Or maybe polishing cars.
vi | preface
So, if you can ship, you’ll be personally and professionally successful. But it’s damn hard for teams to ship, which is where you come in.
This book is your shortcut to a degree in shipping. Think about it like this: McKinsey and Company, the world-famous, hyperexpensive, fancy- pants management consulting company, hires a new crop of science PhDs each year and puts them in a two-week “mini MBA” program. They then expect these PhDs to do pretty much what the MBAs do, even though the PhDs have two weeks of training to the MBAs’ two years. The goal of this book is to provide you with the same simplified, no-BS approach to doing your job—or understanding your team lead’s job.
This book exists because I needed it when I started trying to ship soft- ware, and I see product managers, test leads, engineering managers, and team leads of all types who are struggling, just as I did. I see them going through the same special torture that I underwent when I entered this industry—but I had the good fortune to have great teachers attendant at my hazing: Dartmouth, Amazon, Google, and my own mistaken ventures.
My first teacher was my own company—I was arrogant enough to think that since I could write software I could do everything else required to ship it. You know, define the minimum viable product, manage the project, iterate, release, market, and so on. I learned many valuable les- sons, hubris among them. I then joined another startup as the chief tech- nology officer, and spent years trying to make it big. I learned (mostly) different lessons there, but repeated the class in hubris. Abashed, I went to Dartmouth, and studied at the Thayer School of Engineering and the Tuck School of Business, earning a master’s of engineering management degree.
I left Dartmouth and joined Amazon, where I was a technical product program manager and an engineering manager (a.k.a. two-pizza team leader). On projects like customer reviews, identity, and fraud-fighting in- frastructure, I saw how Jeff Bezos and his lieutenants worked and learned to mimic how some of the best in the business did the job.
I eventually went to Google, and as a senior product manager I spent over five years focusing on scalability, business strategy, and the interper- sonal dynamics inherent in software teams. I grew Google Pack, shipped the Google Update service used in dozens of products, and helped build the Google Apps program through mobile sync services, connectors for Microsoft Outlook, and data import tools. I launched Google’s innova- tive multiway video products, now featured as Google Hangouts. I even worked on Maps for a while. I saw the company grow and change, but
preface | vii
more important, I saw successes and failures and learned more lessons about the best ways to ship software.
The best leaders at Amazon and Google have a lot to teach. Remember, this business is new, so the techniques, processes, and tricks you need to ship software weren’t developed until after Windows became dominant. Microsoft’s old approach to shipping software came out of large-scale hard-goods engineering processes. The Internet made three-year develop- ment cycles, shrink-wrapped floppy disk distribution, and Microsoft’s old way obsolete. The rapid iteration, deployment, and adoption afforded by the Internet enabled engineers to develop rapid application development frameworks, usability studies, and new process frameworks like scrum. As a result, most of us are making this stuff up as we go along, and the guidance you can glean from the relatively few executives who are part of the success of Amazon and Google is critical.
The lessons I’ve learned and distilled in this book cover the entire soft- ware life cycle because as you try to ship software you will face challenges in product, program, project, and engineering management. Shipping is not just project management and convincing engineers to work faster. If your job is shipping software, you must have an extremely broad skill set that ranges from deeply technical to highly creative, and along the way you must provide cogent business insight. You’ll probably do everything from managing people to writing test cases to making mocks in Photoshop. If you’re up for a challenge that’s second to none, this is your gig.
To put this in perspective, shipping is a painful, confusing, and dif- ficult job that’s generally only rewarding if you’re really good at it. The job is like playing golf on gravel fairways—if you suck at it, you’ll spend all day grinding your clubs to bits and wandering around in the pounding sun trying to find your ball, which will be hopelessly unidentifiable amidst the rocks. But if you’re a great golfer, you’ll hit those sweet shots that put you onto the soft green and when you look around, surrounded by sweating, confused duffers, you’ll know what it’s about. It’s glorious.
Get a 10 % discount on an order above $ 100
Use the following coupon code :