Commencez à lire Beautiful Teams sur votre Kindle dans moins d'une minute. Vous n'avez pas encore de Kindle ? Achetez-le ici Ou commencez à lire dès maintenant avec l'une de nos applications de lecture Kindle gratuites.

Envoyer sur votre Kindle ou un autre appareil

 
 
 

Essai gratuit

Découvrez gratuitement un extrait de ce titre

Envoyer sur votre Kindle ou un autre appareil

Tout le monde peut lire les livres Kindle, même sans un appareil Kindle, grâce à l'appli Kindle GRATUITE pour les smartphones, les tablettes et les ordinateurs.
Beautiful Teams: Inspiring and Cautionary Tales from Veteran Team Leaders
 
Agrandissez cette image
 

Beautiful Teams: Inspiring and Cautionary Tales from Veteran Team Leaders [Format Kindle]

Andrew Stellman , Jennifer Greene
4.0 étoiles sur 5  Voir tous les commentaires (1 commentaire client)

Prix conseillé : EUR 24,71 De quoi s'agit-il ?
Prix éditeur - format imprimé : EUR 41,20
Prix Kindle : EUR 17,30 TTC & envoi gratuit via réseau sans fil par Amazon Whispernet
Économisez : EUR 23,90 (58%)

Formats

Prix Amazon Neuf à partir de Occasion à partir de
Format Kindle EUR 17,30  
Broché EUR 38,66  

Descriptions du produit

Présentation de l'éditeur

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:

  • Tim O'Reilly
  • Scott Berkun
  • Mark Healey
  • Bill DiPierre
  • Andy Lester
  • Keoki Andrus
  • Tom Tarka
  • Auke Jilderda
  • Grady Booch
  • Jennifer Greene
  • Mike Cohn
  • Cory Doctorow
  • Neil Siegel
  • Trevor Field
  • James Grenning
  • Steve McConnell
  • Barry Boehm and Maria H. Penedo
  • Peter Gluck
  • Karl E. Wiegers
  • Alex Martelli
  • Karl Fogel
  • Michael Collins
  • Karl Rehmer
  • Andrew Stellman
  • Ned Robinson
  • Scott Ambler
  • Johanna Rothman
  • Mark Denovich and Eric Renkey
  • Patricia Ensworth
  • Andy Oram
  • Tony Visconti

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#.


Détails sur le produit

  • Format : Format Kindle
  • Taille du fichier : 4393 KB
  • Nombre de pages de l'édition imprimée : 510 pages
  • Pagination - ISBN de l'édition imprimée de référence : 0596518021
  • Utilisation simultanée de l'appareil : Illimité
  • Editeur : O'Reilly Media; Édition : 1 (21 mars 2009)
  • Vendu par : Amazon Media EU S.à r.l.
  • Langue : Anglais
  • ASIN: B0043D2E36
  • Synthèse vocale : Activée
  • X-Ray :
  • Moyenne des commentaires client : 4.0 étoiles sur 5  Voir tous les commentaires (1 commentaire client)
  • Classement des meilleures ventes d'Amazon: n°221.894 dans la Boutique Kindle (Voir le Top 100 dans la Boutique Kindle)
  •  Souhaitez-vous faire modifier les images ?


En savoir plus sur l'auteur

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Commentaires en ligne

5 étoiles
0
3 étoiles
0
2 étoiles
0
1 étoiles
0
4.0 étoiles sur 5
4.0 étoiles sur 5
Commentaires client les plus utiles
Format:Broché|Achat vérifié
Un recueil d'interview, récits de très nombreux auteurs, tournant autour du même sujet : la notion d'équipe.
Certaines histoires sont très émouvantes.
Toutes sont instructives.
Une lecture saine pour un jeune chef d'équipe ou chef de projet qui se cherche.
Peut-être un peu long, mais ca se lit bien.
Avez-vous trouvé ce commentaire utile ?
Commentaires client les plus utiles sur Amazon.com (beta)
Amazon.com: 4.2 étoiles sur 5  16 commentaires
7 internautes sur 7 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Something for absolutely everyone 29 juin 2009
Par Jim Brosseau - Publié sur Amazon.com
Format:Broché
This is a brilliant book, capped off with an excellent interview with record producer Tony Visconti, who reveals that the principles behind great teams transcend the genre of software development. From the value of knowing his people to diligent tracking of work charts built by everyone and collaboration in general, it is no surprise that that Tony's experience with musicians sounds a lot like a great software project. He admonishes that we should all devote our downtime to learning new stuff, and this book provides plenty of insights for any of us.

The many contributors step back from advancing their usual prescriptions to celebrate their own successes (and yes, challenges) within teams. In this celebration, they provide some of the best insights that we can carry forward into our own careers.

Whether Jennifer Greene draws wondrous team memories from the ashes of a dot-com failure, Keoki Andrus' shares a healthy respect for innovation and creative play to inspire a team, or engaging stories by Karl Wiegers and many others capture great team experiences, the variety in Beautiful Teams will keep you rapt like few other technical books.
6 internautes sur 6 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Brilliant Collection! 13 juillet 2009
Par Tanya Bhasin - Publié sur Amazon.com
Format:Broché
This book is great! It's a very quick read, and it was actually fun! I've been looking for insight into teamwork and software teams, and I was definitely not disappointed. To be honest, going into it I wasn't really sure what to expect. It dives straight into an interview with Tim O'Reilly about leadership, and he immediately starts talking about teams, creativity, design, open source, but in a way that all tied together and made sense. Then came an essay called "Why Ugly Teams Win," by Scott Berkun, who wrote about his experience on a team at Microsoft. I thought the combination of "higher" ideas and practical, real-world experience, right next to each other, worked extremely well.

The book is divided into sections called People, Goals, Practices, Obstacles and Music. When I first saw that, I was surprised by the last section. But it turned out to be one of my favorite parts of the book. It's got an interview with Tony Visconti, and what he says about working with musicians actually made a lot of sense, and I could see exactly why it made sense as the last chapter in the book. All of the chapters stand on their own, and they all make different points about teams. It's easy to just go right through them, from front to end. It's a unique collection, and in my opinion it's definitely worth your time.
5 internautes sur 5 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 A wonderful collection of stories about beautiful teams 8 juillet 2009
Par Abby Fichtner - Publié sur Amazon.com
Format:Broché
Beautiful Teams is a wonderful collection of stories by great names in software about their experiences with teams. From Mike Cohn, Scott Ambler, Grady Booch, Steve McConnell, Scott Berkun, Johanna Rothman, James Grenning... And even a few non-software folks who make the stories that much more compelling because they transcend discipline.

The book is broken into 4 main sections - one each for the primary themes that come up when talking about beautiful teams: People, Goals, Practices, and Obstacles. One of my favorites is Scott Berkun's Why Ugly Teams Win, which proclaims "real heroes are ugly. They are misfits." Citing as examples The Ramones, The Dirty Dozen, and The Bad News Bears. "Once the members of an ugly team have earned each others' trust, they will outperform the rest of any organization."

It's a book that can't help but make you smile as you think of your own experiences with great teams and what makes them so awesome to be part of. I don't know that there's the answer to how to build a beautiful team in here, it is more a book of tales. But it is definitely a topic we will do well to be thinking more about in software development and a fun book to read.

And, again, I love Scott Berkun's advice, "Stop complaining about your coworkers. Instead, get your team and your boss to read Beautiful Teams." Indeed!
7 internautes sur 8 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 Uneven writing, great content 8 juin 2009
Par James Holmes - Publié sur Amazon.com
Format:Broché
This book's a good read and a nice addition to your bookshelf, although its uneven writing style and fractured voice detract from some great tidbits.

Beautiful Teams is a collection of interviews and essays by various folks in and around the software industry. Each chapter is a great interview with folks like Steve McConnell or Scott Ambler, or an essay-like article from Mike Cohn or Corey Doctorow. Chapters are slotted into broad sections dealing with individuals, goals, practices, obstacles, and music - as in how parallels can be drawn between musicians in a band and members of software teams.

The uneven writing style and fractured voice can be somewhat expected since each author wrote their own articles, but tighter editing could have really polished up the chapters and made the book more cohesive. The tone of many of the articles made it seem they were drawn directly from the authors' blogs - another point for having had some tighter editing. I also wished that each chapter had an introduction/bio about the author. While these people are supposed industry leaders, there were quite a few authors I wasn't familiar with, so I was left wondering what their accomplishments were that made them a target to get in the book.

Complaints aside, I got very good value from reading the book. The wisdom in several articles around dealing with team dynamics was exceedingly useful, and I also found it good backup to read industry leaders pointing out it's important to move poor performers or negative influences off teams.

Several chapters really stood out for me: Grady Booch's interview on creating team cultures, James Grenning's article on implementing extreme programming (XP) in a heavily bureaucratic shop during XP's early days, and Steve McConnell's interview about improving team skills, morale, and practices.

Booch's interview really struck home due to his discussion of working on geographically distributed teams. I'm a remote worker and am far away from everyone I work with at Telligent, so this was particularly interesting to me. Booch's comments on the importance of trust between team members and dealing with cultural issues really struck home - he emphasized that technology isn't the limiting factor on poor-performing distributed teams.

Greening's experience pushing for change was a great read. The tone and style are clunky, but the content's gold. Greening was learning XP in its earliest days and worked hard to get an XP team going on a project in a very tight-laced, policy-ridden company. The number one takeaway from me from this article was something I'm already a huge believer in: culture change will utterly fail if you don't have management and leadership that actively supports the change.

I've yet to read anything from Steve McConnell that wasn't ridden with great wisdom, and his interview in this book certainly kept that tradition. His points on helping establish a team identity were highly useful. I loved his commentary on the asinine failure (my words) of companies to budget funds for team and morale building. It makes no sense that companies will spend millions on payroll, yet do nothing to build and grow team morale.

Overall I've really enjoyed reading this book. It's one of the few I'll keep around on my bookshelf.
4 internautes sur 4 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 "[Excellent] book... but it's a different one than you're imagining" * 8 juillet 2009
Par Ethan Schartman - Publié sur Amazon.com
Format:Broché
The very first chapter I read concerned a software team which morphed into an improv comedy troupe which also wrote successful (for some definition of success) code. This narrative was so funny that I was nearly in tears by the end. I would not be surprised to see the "turducken" software model or theoretical scatology enter the geek lexicon as a result. It alone is worth the price of the book, though it is also worth noting that proceeds from about every 3000 copies sold will be used to purchase a PlayPump to provide clean drinking water to a developing area.

My impression of this book is that it is the one that Andrew Stellman wishes he had read prior to turning down that project management promotion the first time. A pithy variant on that sentence would be a more appropriate title for the book. But as it is part of O'Reilly's "Beautiful <noun>: <descriptive keywords>" brand, that was clearly not possible. Stellman and Greene both include first hand vignettes from their early careers and contribute to the interviews. But in the interviews, Greene's questions are fashioned in a more mainstream interviewer-subject style. Stellman's questions often employ a more personal style as though you were witness to selected conversations he'd had since transitioning to project management.

The interview format is less than 50% of the book, with the balance being vignettes and essays from the contributors told from a first person perspective about particularly memorable teams they worked with. Many of the authors are not "famous", some have not previously been published and at least one was not a "leader". I can't think of a single one that was not worth reading. In some cases the contributions tend toward tranche de vie, rather than an abstracted discussion of the operation of the team. Because these lack a strict "how we did/didn't do it" format, you might suspect they'd detract from a "how to build a better team" format.

You'd be wrong on two counts, however. The first is that they break up the structure of the standard business literature, making the book overall very easy to read. In fact, the first day I read one chapter at random and then skipped around and read a "few" more. The next day, when I inventoried what I had read, I found that I had actually consumed more than a third of the entire book! The second count is that taken in aggregate, these tranches de vie allow you to start picking out patterns that are not necessarily apparent in any single contribution. In this way the book successfully "creates a context in which other people can think**"

The editing is a little lax, but I did not find it too intrusive, though there are a couple of missing transition paragraphs which ought to be included in future editions.

*Quote from the interview with Tim O'Reilly.
** Tim O'Reilly quoting Edwin Schlossberg
Ces commentaires ont-ils été utiles ?   Dites-le-nous
Rechercher des commentaires
Rechercher uniquement parmi les commentaires portant sur ce produit

Discussions entre clients

Le forum concernant ce produit
Discussion Réponses Message le plus récent
Pas de discussions pour l'instant

Posez des questions, partagez votre opinion, gagnez en compréhension
Démarrer une nouvelle discussion
Thème:
Première publication:
Aller s'identifier
 

Rechercher parmi les discussions des clients
Rechercher dans toutes les discussions Amazon
   


Rechercher des articles similaires par rubrique