AccueilGroupesDiscussionsPlusTendances
Site de recherche
Ce site utilise des cookies pour fournir nos services, optimiser les performances, pour les analyses, et (si vous n'êtes pas connecté) pour les publicités. En utilisant Librarything, vous reconnaissez avoir lu et compris nos conditions générales d'utilisation et de services. Votre utilisation du site et de ses services vaut acceptation de ces conditions et termes.

Résultats trouvés sur Google Books

Cliquer sur une vignette pour aller sur Google Books.

Chargement...

Questioning Extreme Programming

par Pete McBreen

MembresCritiquesPopularitéÉvaluation moyenneDiscussions
41Aucun605,442 (3.86)Aucun
Extreme Programming (XP) has been the subject of heated debate since its arrival on the programming scene in 1998—understandably so, as it contradicts many traditional software development beliefs. We¿ve heard success stories about sweeping changes made to organizations as a result of XP. We’ve read books about how this approach can work for our teams. However, are there times when XP isn’t appropriate? There are certainly instances when making the leap to XP could potentially jeopardize a whole project. What’s missing from all of this rhetoric? Witness Pete McBreen, software craftsman, examine the issue from both sides. In Questioning Extreme Programming , the author helps you examine and answer the following questions: Is the cost of change really low? Does XP allow proper testing? Does XP make sense? Is XP a return to the dark ages? Can we adopt XP practices for other approaches? Do you need process improvement or process change? Why are developers so zealous about adopting XP? Is XP suitable for your projects? What is the next step after Extreme Programming? After reading this thought-provoking book, software developers can make informed decisions about Extreme Programming, and whether it is suitable for their organization. Readers will also be able to determine whether Extreme Programming is inappropriate for a particular project. The author challenges you to look past the hype and start asking the hard questions about how software is built. Discover for yourself. 0201844575B07092002… (plus d'informations)
Aucun
Chargement...

Inscrivez-vous à LibraryThing pour découvrir si vous aimerez ce livre

Actuellement, il n'y a pas de discussions au sujet de ce livre.

Aucune critique
aucune critique | ajouter une critique

Appartient à la série

Vous devez vous identifier pour modifier le Partage des connaissances.
Pour plus d'aide, voir la page Aide sur le Partage des connaissances [en anglais].
Titre canonique
Titre original
Titres alternatifs
Date de première publication
Personnes ou personnages
Lieux importants
Évènements importants
Films connexes
Épigraphe
Dédicace
Premiers mots
Citations
Derniers mots
Notice de désambigüisation
Directeur de publication
Courtes éloges de critiques
Langue d'origine
DDC/MDS canonique
LCC canonique

Références à cette œuvre sur des ressources externes.

Wikipédia en anglais (1)

Extreme Programming (XP) has been the subject of heated debate since its arrival on the programming scene in 1998—understandably so, as it contradicts many traditional software development beliefs. We¿ve heard success stories about sweeping changes made to organizations as a result of XP. We’ve read books about how this approach can work for our teams. However, are there times when XP isn’t appropriate? There are certainly instances when making the leap to XP could potentially jeopardize a whole project. What’s missing from all of this rhetoric? Witness Pete McBreen, software craftsman, examine the issue from both sides. In Questioning Extreme Programming , the author helps you examine and answer the following questions: Is the cost of change really low? Does XP allow proper testing? Does XP make sense? Is XP a return to the dark ages? Can we adopt XP practices for other approaches? Do you need process improvement or process change? Why are developers so zealous about adopting XP? Is XP suitable for your projects? What is the next step after Extreme Programming? After reading this thought-provoking book, software developers can make informed decisions about Extreme Programming, and whether it is suitable for their organization. Readers will also be able to determine whether Extreme Programming is inappropriate for a particular project. The author challenges you to look past the hype and start asking the hard questions about how software is built. Discover for yourself. 0201844575B07092002

Aucune description trouvée dans une bibliothèque

Description du livre
Résumé sous forme de haïku

Discussion en cours

Aucun

Couvertures populaires

Vos raccourcis

Évaluation

Moyenne: (3.86)
0.5
1
1.5
2 1
2.5
3 1
3.5
4 3
4.5
5 2

Est-ce vous ?

Devenez un(e) auteur LibraryThing.

 

À propos | Contact | LibraryThing.com | Respect de la vie privée et règles d'utilisation | Aide/FAQ | Blog | Boutique | APIs | TinyCat | Bibliothèques historiques | Critiques en avant-première | Partage des connaissances | 203,233,456 livres! | Barre supérieure: Toujours visible