\(
\def\WIPO{World Intellectual Property Organisation}
\)
Planning extreme programming / Kent Beck, Martin Fowler ; illustrated by Jennifer Kohnke ; [foreword by Tom DeMarco].
2000
D 73 BEC.P
Available at WIPO Library
Formatos
| Formato | |
|---|---|
| BibTeX | |
| MARCXML | |
| TextMARC | |
| MARC | |
| DataCite | |
| DublinCore | |
| EndNote | |
| NLM | |
| RefWorks | |
| RIS |
Items
Detalles
Title
Planning extreme programming / Kent Beck, Martin Fowler ; illustrated by Jennifer Kohnke ; [foreword by Tom DeMarco].
Descripción
xvii, 139 pages ; [28] cm.
ISBN
0201710919
9780201710915 paperback
9780201710915 paperback
Alternate Call Number
D 73 BEC.P
Resúmen
"Within this context of flexibility and rapid-fire changes, planning is critical; without it, software projects can quickly fall apart. Written by acknowledged XP authorities Kent Beck and Martin Fowler, Planning Extreme Programming presents the approaches, methods, discipline, and advice you need to plan and track a successful Extreme Programming project. The key XP philosophy: Planning is not a one-time event, but a constant process of reevaluation and course-correction throughout the life cycle of the project."
Nota
Angekündigt als: Beck, Kent: Steering & planning with extreme programming.
Indhold: Why plan? Fear. Dring software. Balancing power. Overviews. Too much to do. Four variables. Yesterday's weather. Scoping a project. Release planning. Writing stories. Estimation. Ordering te stories. Relaease planning events. The first plan. Release planning variations. Iteration plannning. Iteration planning meeting. Tracking an interation. Stand-up meetings. Visible graphs. Dealing with bugs. Changes to the team. Tools. Business contracts. Red flags. Your own process.
Indhold: Why plan? Fear. Dring software. Balancing power. Overviews. Too much to do. Four variables. Yesterday's weather. Scoping a project. Release planning. Writing stories. Estimation. Ordering te stories. Relaease planning events. The first plan. Release planning variations. Iteration plannning. Iteration planning meeting. Tracking an interation. Stand-up meetings. Visible graphs. Dealing with bugs. Changes to the team. Tools. Business contracts. Red flags. Your own process.
Serie
Serie
Xp Series.
Published
Boston : Addison-Wesley, 2000.
Lengua(s)
eng
El registro aparece en
Review
"Within this context of flexibility and rapid-fire changes, planning is critical; without it, software projects can quickly fall apart. Written by acknowledged XP authorities Kent Beck and Martin Fowler, Planning Extreme Programming presents the approaches, methods, discipline, and advice you need to plan and track a successful Extreme Programming project. The key XP philosophy: Planning is not a one-time event, but a constant process of reevaluation and course-correction throughout the life cycle of the project."