Corporate Software Project Management

Basically this is one of many books on software project management. However, it does have a few features that make it a standout in this category. One of the things that differentiate this book is the included software tools like Open Work Bench and version control software. While many project management books cover just management of the project from an internal perspective, this one includes management of the external factors with the client. For example they discuss the importance of setting up a liaison center as a primary contact point for the client and dealing with client dissatisfaction. It is obvious that the author has had some experience with project management from gathering client expectations through delivering the final product. Some of the areas discussed include setting standards and guidelines, project specifications, development and testing, and requirements definition. He details some of the things that need to be captured up front for a successful project such as system context, operating environment, end-user services, supporting services, documentation, and maintenance. I've seen a lot of software projects go awry for various reasons and this book details the steps to be taken to prevent those problems right from the start. Because it takes a complete view and deals not only with the coding and the internal perspective of project management but also with client relations and setting up a framework within which to work with the client, Corporate Software Project Management is highly recommended and superior to most other project management books.

I'm reminded of the old saying regarding software (or probably any other technical project), "You can have it on time, within budget, or working -- Pick any two. Actually, of course, techniques have been developed which assist in all three of these areas. The first key is to spend more time in the definition or requirements phase. This means establishing communications channels, standards and guidelines, and a detailed set of specifications that are agreed upon by all. Finally there is testing. Often left until it is the last item on the schedule, testing needs to be moved closer to the front. Catching bugs earlier means that they aren't there in the finished project. The second key is to establish the project management structure. This includes breaking the project down into a set of requirements that meets the agreed upon specifications. This can then be used to establish a critical path for the development. Corporate software engineering principles can be used to produce code that is easy to maintain, read, and extend to additional requirements. There are a number of management tools that have been developed to assist in this phase. Several of the more common tools are included on the CD furnished with the book, some of them trial versions with time limitations that can be examined to see if they fit your needs.