MARC details
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
|---|
| fixed length control field |
080306s2005 caua b 001 0 eng |
| 010 ## - LIBRARY OF CONGRESS CONTROL NUMBER |
|---|
| LC control number |
2005019810 |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
1590595505 |
| 035 ## - SYSTEM CONTROL NUMBER |
|---|
| System control number |
(Sirsi) u26 |
| 040 ## - CATALOGING SOURCE |
|---|
| Original cataloging agency |
EG-CaNU |
| Transcribing agency |
EG-CaNU |
| Modifying agency |
EG-CaNU |
| 042 ## - AUTHENTICATION CODE |
|---|
| Authentication code |
ncode |
| 082 00 - DEWEY DECIMAL CLASSIFICATION NUMBER |
|---|
| Classification number |
005.1 |
| Edition number |
22 |
| 100 1# - MAIN ENTRY--PERSONAL NAME |
|---|
| Personal name |
Marasco, Joe. |
| 9 (RLIN) |
4656 |
| 245 10 - TITLE STATEMENT |
|---|
| Title |
Software project secrets : |
| Remainder of title |
why software projects fail / |
| Statement of responsibility, etc. |
George Stepanek. |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. |
|---|
| Place of publication, distribution, etc. |
Berkeley : |
| Name of publisher, distributor, etc. |
Apress, |
| Date of publication, distribution, etc. |
2005. |
| 300 ## - PHYSICAL DESCRIPTION |
|---|
| Extent |
xvii, 166 p. : |
| Other physical details |
ill. ; |
| Dimensions |
23 cm. |
| 504 ## - BIBLIOGRAPHY, ETC. NOTE |
|---|
| Bibliography, etc. note |
Includes bibliographical references and index. |
| 505 ## - FORMATTED CONTENTS NOTE |
|---|
| Formatted contents note |
Part I. Why Software Projects Fail -- Introduction -- Why Software Is Different -- Project Management Assumptions -- Case Study: The Billing System Project.- Part II. And How To Make Them Succeed -- The New Agile Methodologies -- Making Software Projects Agile -- Case Study: The Billing System Revisited -- Afterword -- Glossary -- Further Reading -- Index |
| 520 ## - SUMMARY, ETC. |
|---|
| Summary, etc. |
Software Project Secrets: Why Software Projects Fail offers a new path to success in the software industry. This book reaches out to managers, developers, and customers who use industry-standard methodologies, but whose projects still struggle to succeed. Author -->George Stepanek--> analyzes the project management methodology itself, a critical factor that has thus far been overlooked. He explains why it creates problems for software development projects and begins by describing 12 ways in which software projects are different from other kinds of projects. He also analyzes the project management body of knowledge to discover 10 hidden assumptions that are invalid in the context of software projects.-->Table of Contents-->IntroductionWhy Software Is DifferentProject Management AssumptionsCase Study: The Billing System ProjectThe New Agile MethodologiesBudgeting Agile ProjectsCase Study: The Billing System RevisitedAfterword |
| 520 ## - SUMMARY, ETC. |
|---|
| Summary, etc. |
Software Project Secrets is the first book to analyze and address the problems that project management's best practices cause in software development projects. It shows how to integrate agile methodologies with project management to resolve these problems. The book is aimed at managers, developers and customers who use industry standard methodologies, but whose projects still struggle to succeed. In 2000, only 28% of software projects succeeded outright. 23% were cancelled, and the remainders were substantially late and over budget. (In contrast, 94% of construction projects succeed.) No-one has yet found a satisfactory explanation for why so many software projects fail so badly. The author analyzes a factor that has so far been overlooked-the project management methodology itself-to find out how it might create problems for software development projects. His experience has shown him that project management processes often take priority over software development best practices. The book begins by describing twelve ways in which software projects are different from other kinds of projects. It then analyses the Project Management Body Of Knowledge to discover ten hidden assumptions that are not valid in the context of software projects. It describes the problems caused by these invalid assumptions. One solution is to integrate project management with methodologies that do work for software development: the agile methodologies. The book describes and compares three of the most significant and widely-used agile methodologies: Crystal, Extreme Programming and the Rational Unified Process. It suggests new ways to combine these methodologies with project management to ensure that the best aspects of both are retained. |
| 596 ## - |
|---|
| -- |
1 |
| 630 00 - SUBJECT ADDED ENTRY--UNIFORM TITLE |
|---|
| Uniform title |
CIT. |
| 9 (RLIN) |
14 |
| 630 00 - SUBJECT ADDED ENTRY--UNIFORM TITLE |
|---|
| Uniform title |
MOT. |
| 9 (RLIN) |
4934 |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name entry element |
Computer software |
| General subdivision |
Development. |
| 9 (RLIN) |
4935 |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name entry element |
Project management. |
| 9 (RLIN) |
4936 |