|
|
XP, ça marche vraiment ? - Part II
Si l'on vous parle de méthodes agiles, à quoi pensez-vous spontanément ? Bien sur, à l'eXtreme Programming. Partant de l'idée que certaines pratiques pouvaient expliquer le succès ou l'échec des projets, Kent Beck a voulu "pousser tous les curseurs" soit au minimum soit au maximum.
Le test permet de détecter les anomalies ? Testons en permanence dès le début du projet et pilotons le projet par les tests !
La documentation est pléthorique et souvent inutile ? Réduisons-la au maximum !
Le coût de correction des défauts est supérieur lorsqu'il intervient tard ? Corrigeons-les à la source en pratiquant le pair-programming !
Tout ça parait bien illusoire, voire irréaliste. Et pourtant, certains l'ont mis en œuvre, et pas seulement aux Etats-Unis ! Ils peuvent témoigner du succès de la méthode.
(Wednesday, May 17, 2006 1:00 AM)
Visualiser
Tagged as :
|
History and Evidence Iterative, Evolutionary & Agile vs the waterfall - Part I
Although iterative, incremental, and evolutionary agile development in software is in the ascendance as the modern or agile approach to replace ad hoc or waterfall (sequential lifecycle) development, its practiced and published roots go back surprisingly far.In this presentation, I share the fascinating history of iterative development for software projects. I will also demonstrate that the software engineering thought leaders of the past four decades have consistently promoted iterative development in their work and writings, and vigorously advocated avoiding the waterfall model. And finally, in light of this, I?ll explore the interesting reasons and historical accidents of why the sequential document-driven waterfall model was promoted in academic texts and among various project management groups, in contradiction to the research, history, and expert advice.
(Friday, April 14, 2006 1:00 AM)
Visualiser
Tagged as :
|
History and Evidence Iterative, Evolutionary & Agile vs the waterfall - Part II
Although iterative, incremental, and evolutionary agile development in software is in the ascendance as the modern or agile approach to replace ad hoc or waterfall (sequential lifecycle) development, its practiced and published roots go back surprisingly far.In this presentation, I share the fascinating history of iterative development for software projects. I will also demonstrate that the software engineering thought leaders of the past four decades have consistently promoted iterative development in their work and writings, and vigorously advocated avoiding the waterfall model. And finally, in light of this, I?ll explore the interesting reasons and historical accidents of why the sequential document-driven waterfall model was promoted in academic texts and among various project management groups, in contradiction to the research, history, and expert advice.
(Friday, May 05, 2006 1:00 AM)
Visualiser
Tagged as :
|
|
|
|
|
|
 |