Software Project Management Methods and Techniques

The management of a software project has been shown to be the number one factor in determining a project’s success. It has been found that 53% of software projects failures are due to poor management. The book remedies this situation in two ways: explaining the discipline and providing fact-based resources on software project management.

The management of a software project has been shown to be the number one factor in determining a software development project’s success. It has been found that most software projects fail because of poor management. Not surprisingly, most software development managers have not been trained in project management. Software Project Management: Methods and Techniques aims to remedy this situation in two ways: familiarizing software developers with the elements of the project management discipline and providing fact-based resources on practicing software project management.

Much like the checklist pilots go through prior to a flight, this book provides a pre-project checklist which enables the software engineering team to review and evaluate an extensive set of technical and sociopolitical risks which will help the software project manager and the team determine the project team’s chances of success. This same list and the individual question responses can be used later as part of the project’s closeout process helping team members to improve their individual and collective abilities to assess risk.

Intended for both students and software project managers, the book is organized along the lines of the five major functions of a software project manager: planning; scheduling and costing; controlling; staffing; and motivating. The basics of each of these functions are presented in a single chapter. These are followed by a series of narrow topic presentations in the form of appendices that are intended to help solve specific problems that may occur during the conduct of a software project. As in the main portion of the text, the appendices include references that provide an avenue into further detail on the topic. Designed to promote project success, this approach has been taken because software projects are each unique undertakings such that providing a "one size fits all" approach will fail most of the time.