×

Uh-oh, it looks like your Internet Explorer is out of date.

For a better shopping experience, please upgrade now.

Software Project Secrets: Why Software Projects Fail / Edition 1
     

Software Project Secrets: Why Software Projects Fail / Edition 1

by George Stepanek
 

ISBN-10: 1590595505

ISBN-13: 9781590595503

Pub. Date: 09/07/2005

Publisher: Apress

* 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

Overview

* 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.

Product Details

ISBN-13:
9781590595503
Publisher:
Apress
Publication date:
09/07/2005
Series:
Expert's Voice Series
Edition description:
2005
Pages:
192
Product dimensions:
7.00(w) x 9.25(h) x 0.50(d)

Table of Contents

About the Authorxiii
About the technical Reviewerxv
Acknowledgmentsxvii
Part IWhy Software Projects Fail
Chapter 1Introduction3
Chapter 2Why Software is Different7
1Software Is Complex8
2Software Is Abstract10
3Requirements Are Incomplete11
4Technology Changes Rapidly12
5Best Practices Are Not Mature13
6Technology Is a Vast Domain15
7Technology Experience Is Incomplete16
8Software Development Is Research16
9Repetitive Work Is Automated18
10Construction Is Actually Design19
11Change Is Considered Easy20
12Change Is Inevitable21
Summary22
Chapter 3Project Management Assumptions23
Hidden Assumptions24
The PMBOK24
Scope Management25
When Should Scope Definition Occur?27
Time Management28
Activity Definition28
Activity Sequencing30
Activity Duration Estimating34
Schedule Development36
Cost Management37
Resource Planning38
Software Documentation39
Developer Productivity42
Cost Estimating43
Quality Management44
Metrics44
Checklists45
Risk Management45
Risk Acceptance46
Risk Transference47
Risk Avoidance48
Risk Mitigation48
Summary49
Chapter 4Case Study: The Billing System Project51
Requirements51
Planning52
Design54
Construction54
Coding55
Integration55
Testing57
Death March58
Aftermath59
Summary60
Part II...And How to Make Them Succeed
Chapter 5The New Agile Methodologies65
Selected Methodologies66
Other Agile Methodologies66
Crystal67
1Frequent Delivery68
2Reflective Improvement69
3Close or Osmotic Communication70
4Personal Safety71
5Focus72
6Easy Access to Expert Users72
7Technical Environment with Automated Tests, Configuration Management, and Frequent Integration73
Using Crystal74
Extreme Programming75
1The Planning Game76
2Testing77
3Pair Programming78
4Refactoring78
5Simple Design79
6Collective Code Ownership80
7Continuous Integration80
8On-Site Customer81
9Small Releases81
1040-Hour Week81
11Coding Standards82
12System Metaphor82
Using XP83
The Rational Unified Process84
Phases86
Iterations87
Roles87
Artifacts87
Activities and Workflows88
Process Configuration88
Use Case-Driven Development89
Visual Modeling89
Using RUP90
Mitigating Risks with Agility91
1Incomplete Requirements and Scope Changes91
2Tools and Technologies Don't Work As Expected92
3Developers Lack Skills and Expertise92
4The New Software Has Defects and Requires Rework92
5Project Staff Turnover93
Summary94
Chapter 6Budgeting Agile Projects97
Budgeting for Software Development98
1Continuous Development100
2On-Demand Programming101
3SWAT Teams102
4Subteam Encapsulation104
5Feature Trade-off106
6Triage106
7Scoping Studies108
Combining These Techniques109
Major Legacy System110
Minor Legacy Application110
Major New System111
Minor New Application112
Agile Offshore Outsourcing112
Summary114
Chapter 7Case Study: The Billing System Revisited115
Methodology115
Inception116
Scoping Study117
Project Planning Meeting118
Elaboration121
Review Meeting122
Construction123
Construction Iteration 5124
Transition126
Deployment126
Aftermath127
Summary128
Chapter 8Afterword131
AppendixThe Agile Manifesto133
Manifesto for Agile Software Development133
Glossary135
Bibliography143
Index151

Customer Reviews

Average Review:

Post to your social network

     

Most Helpful Customer Reviews

See all customer reviews