Software Projects Secrets: Why Projects Fail
Format: PDF / Kindle (mobi) / ePub
George Stepanek, "Software Projects Secrets: Why Projects Fail"
English | ISBN: 1430251018 | 2012 | Publisher: Apress | PDF | 184 pages | 3 MB
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
Why Software Is Different
Project Management Assumptions
Case Study: The Billing System Project
The New Agile Methodologies
Budgeting Agile Projects
Case Study: The Billing System Revisited
5505CH06.qxd 98 7/22/05 12:07 PM Page 98 Part II . . .And How to Make Them Succeed Each technique can be used individually, but they can also be used together. After discussing each technique in turn, we’ll consider how best to combine them for different types of software projects. Finally, we’ll take a brief look at the controversial subject of offshore outsourcing, to see whether it really can deliver its promised cost benefits, and whether it can be done in an agile way. In the next
beyond that there is even more functionality available from third-party software components. A single application would use only a few of these routines and components. Even when working on a variety of applications and systems, a developer will not be able to gain experience with more than a small proportion of the technologies that are available. NOTE Software development has far more technologies, and its technologies have far more complexity than a single individual can hope to gain expertise
www.computerworld.com/managementtopics/roi/story/0,10801,78529,00.html. A clear explanation of the term “payback period.” Auer, Ken and Roy Miller. Extreme Programming Applied: Playing to Win. Addison-Wesley, 2002. One of a raft of very similar books that have been published about XP. This one focuses on getting started with the various techniques, and is a good introduction. Bell, Stephen. Justice ministry begins fixing error-ridden Courts system. Computerworld, 27 April 2004.
97–113 combining techniques when budgeting, 109–112 importance of scoping studies in budgeting, 108–109 techniques to make estimation processes more accurate, 97–98 Agile Software Development (Addison-Wesley, 2002), by Alistair Cockburn, 144 agile software development, manifesto for, 133–134 Agile Software Development with SCRUM (Prentice Hall, 2001), by Ken Schwaber and Mike Beedle, 148 Agility with RUP (Cutter IT Journal, vol. 14, no. 12, December 2001), by Philippe Kruchten, 146 analogous
into a system that’s logically consistent and easy to use. The project will probably include software tools and components that are new or unfamiliar to the developers. New technology doesn’t always match up to the marketing claims that are made for it. The rate of change in technology has been accelerating, and products are often released before they’re mature, complete, or bug-free. The advantages of being first to the market can outweigh the drawbacks of proffering flawed software. For these