+612 9045 4394
 
CHECKOUT
Software Project Secrets : Why Software Projects Fail - George Stepanek

Software Project Secrets

Why Software Projects Fail

Hardcover

Published: 8th September 2005
Ships: 7 to 10 business days
7 to 10 business days
RRP $163.99
$124.90
24%
OFF
or 4 easy payments of $31.23 with Learn more

* No other writer on the popular topic of Agile methods and software development methods has identified project management's best practices as a cause of software project failure. The analysis clearly shows how these best practices can create problems for software development projects. * The book assumes no technical knowledge, and is accessible to businesspeople-project managers, executives and customers-who may know nothing about software development. This book is geared towards a wide group of IT professionals and decision makers working in 2005.





* This book is not just theoretical. The detailed case studies included make the material come to life. They illustrate how methodology choices influence the success or failure of software development projects.

About the Authorp. xiii
About the technical Reviewerp. xv
Acknowledgmentsp. xvii
Why Software Projects Fail
Introductionp. 3
Why Software is Differentp. 7
Software Is Complexp. 8
Software Is Abstractp. 10
Requirements Are Incompletep. 11
Technology Changes Rapidlyp. 12
Best Practices Are Not Maturep. 13
Technology Is a Vast Domainp. 15
Technology Experience Is Incompletep. 16
Software Development Is Researchp. 16
Repetitive Work Is Automatedp. 18
Construction Is Actually Designp. 19
Change Is Considered Easyp. 20
Change Is Inevitablep. 21
Summaryp. 22
Project Management Assumptionsp. 23
Hidden Assumptionsp. 24
The PMBOKp. 24
Scope Managementp. 25
When Should Scope Definition Occur?p. 27
Time Managementp. 28
Activity Definitionp. 28
Activity Sequencingp. 30
Activity Duration Estimatingp. 34
Schedule Developmentp. 36
Cost Managementp. 37
Resource Planningp. 38
Software Documentationp. 39
Developer Productivityp. 42
Cost Estimatingp. 43
Quality Managementp. 44
Metricsp. 44
Checklistsp. 45
Risk Managementp. 45
Risk Acceptancep. 46
Risk Transferencep. 47
Risk Avoidancep. 48
Risk Mitigationp. 48
Summaryp. 49
Case Study: The Billing System Projectp. 51
Requirementsp. 51
Planningp. 52
Designp. 54
Constructionp. 54
Codingp. 55
Integrationp. 55
Testingp. 57
Death Marchp. 58
Aftermathp. 59
Summaryp. 60
...And How to Make Them Succeed
The New Agile Methodologiesp. 65
Selected Methodologiesp. 66
Other Agile Methodologiesp. 66
Crystalp. 67
Frequent Deliveryp. 68
Reflective Improvementp. 69
Close or Osmotic Communicationp. 70
Personal Safetyp. 71
Focusp. 72
Easy Access to Expert Usersp. 72
Technical Environment with Automated Tests, Configuration Management, and Frequent Integrationp. 73
Using Crystalp. 74
Extreme Programmingp. 75
The Planning Gamep. 76
Testingp. 77
Pair Programmingp. 78
Refactoringp. 78
Simple Designp. 79
Collective Code Ownershipp. 80
Continuous Integrationp. 80
On-Site Customerp. 81
Small Releasesp. 81
40-Hour Weekp. 81
Coding Standardsp. 82
System Metaphorp. 82
Using XPp. 83
The Rational Unified Processp. 84
Phasesp. 86
Iterationsp. 87
Rolesp. 87
Artifactsp. 87
Activities and Workflowsp. 88
Process Configurationp. 88
Use Case-Driven Developmentp. 89
Visual Modelingp. 89
Using RUPp. 90
Mitigating Risks with Agilityp. 91
Incomplete Requirements and Scope Changesp. 91
Tools and Technologies Don't Work As Expectedp. 92
Developers Lack Skills and Expertisep. 92
The New Software Has Defects and Requires Reworkp. 92
Project Staff Turnoverp. 93
Summaryp. 94
Budgeting Agile Projectsp. 97
Budgeting for Software Developmentp. 98
Continuous Developmentp. 100
On-Demand Programmingp. 101
SWAT Teamsp. 102
Subteam Encapsulationp. 104
Feature Trade-offp. 106
Triagep. 106
Scoping Studiesp. 108
Combining These Techniquesp. 109
Major Legacy Systemp. 110
Minor Legacy Applicationp. 110
Major New Systemp. 111
Minor New Applicationp. 112
Agile Offshore Outsourcingp. 112
Summaryp. 114
Case Study: The Billing System Revisitedp. 115
Methodologyp. 115
Inceptionp. 116
Scoping Studyp. 117
Project Planning Meetingp. 118
Elaborationp. 121
Review Meetingp. 122
Constructionp. 123
Construction Iteration 5p. 124
Transitionp. 126
Deploymentp. 126
Aftermathp. 127
Summaryp. 128
Afterwordp. 131
The Agile Manifestop. 133
Manifesto for Agile Software Developmentp. 133
Glossaryp. 135
Bibliographyp. 143
Indexp. 151
Table of Contents provided by Ingram. All Rights Reserved.

ISBN: 9781590595503
ISBN-10: 1590595505
Series: Expert's Voice
Audience: General
Format: Hardcover
Language: English
Number Of Pages: 192
Published: 8th September 2005
Publisher: Apress
Country of Publication: US
Dimensions (cm): 23.5 x 17.8  x 2.54
Weight (kg): 0.49