
Beautiful Teams
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions

Content
- Intro
- Praise for Beautiful Teams
- Contents
- Why Beautiful Teams?
- Why These Contributors?
- Preface
- How This Book Is Organized
- Part I, People
- Part II, Goals
- Part III, Practices
- Part IV, Obstacles
- Part V, Music
- How to Contact Us
- Safari® Books Online
- Acknowledgments
- About the Editors
- Leadership
- Part One
- Why Ugly Teams Win
- Ugly Talent
- Ugly As Beautiful
- My Wabi-Sabi Team: Internet Explorer 4.0
- 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 . . .
- Epilogue
- Afterword
- Inner Source
- Part Two
- Creating Team Cultures
- Putting the "I" in Failure
- Planning
- 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
- Learning
- Requirements Versus On-Site Customer
- Trouble in River City
- Teams Are Made of People, Not Resources
- Companies Make Their Own Troubles
- Future Projects
- Collaboration Success Factors
- References
- Better Practices
- Memories of TRW's Software Productivity Project
- Background on the Software Productivity Project
- Making the Project a Reality
- Getting Started: Being Ready with Options When Management Calls
- Evaluating and Selecting Options: Applying the Spiral Model
- Getting Started: A Balanced Team, a Committed Pilot Project, and the Niceties of Unix
- Project Stories
- 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
- Standardization
- 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
- Champions
- The Challenges of the Rapid Change of Technology
- Learning and Assimilating Changes in User Behavior
- Conclusion
- References
- Acknowledgments
- Building Spaceships
- Succeeding with Requirements
- The Setting
- The Cast
- Prologue: Paul Is in a Pickle
- Act I: Girding Our Loins
- Expectation Management
- Classy Users
- Who Ya Gonna Call?
- Act II: Use Cases, Schmuse Cases
- The Case for Use Cases
- Working in the Shop
- Use Cases Aren't Enough
- Beyond Functionality
- The Rules of the Game
- Test Before Coding? Are You Mad?
- Act III: Look Over My Shoulder
- The Casual Style
- The Formal Style
- The Outcome
- Epilogue: Let's Eat!
- Coda: Then What Happened?
- Useful References
- Acknowledgments
- Development at Google
- Teams and Tools
- How Open Source Projects Work
- The Contribulyzer
- The Catch
- The Limits of the Contribulyzer
- Commit Emails and Gumption Sinks
- They're Staying Away in Droves: A Tale of Two Translation Interfaces
- What I Gave Them
- What I Should Have Given Them
- Conclusion
- Research Teams
- The HADS Team
- The Background
- The Initial Team
- Getting It Right
- Dealing with User Issues
- Epilogue
- 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
- Check-ins
- Builds
- Schedules
- 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
- Epilogue
- References
- 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
- A Gem from the Computing Past
- Rewiring
- Coping
- Coding
- Capitulating
- The Break
- Anticipating 21st-Century Management
- Final Notes
- Part Five
- Producing Music
- Contributors
- Index
System requirements
File format: ePUB
Copy protection: Adobe-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Install the free reader Adobe Digital Editions prior to download (see eBook Help).
- Tablet/smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook before downloading (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePub works well for novels and non-fiction books – i.e., „flowing” text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook uses Adobe-DRM, a „hard” copy protection. If the necessary requirements are not met, unfortunately you will not be able to open the eBook. You will therefore need to prepare your reading hardware before downloading.
Please note: We strongly recommend that you authorise using your personal Adobe ID after installation of any reading software.
For more information, see our ebook Help page.