The best techniques and guidelines to deliver IT projects on schedule and within budget With all the pitfalls and cost overruns that can cause a software project to come in late and over budget, managers must know the best practices in the field and how to implement them. This comprehensive guide provides you with all the tools you’ll need to deliver successful IT projects, including proven techniques, guidelines, and checklists. The hands-on tutorial will teach you how to implement these techniques using Microsoft Project 2000. Armed with this book, you’ll be able to build software that meets user requirements. Inside, you’ll find a survival framework that shows you how to achieve the best possible results with your project. The framework presents all the methods, tools, and approaches for you to consider when implementing projects. You will also be introduced to the Iterative Project Development Methodology (IPDM), which you can use on a broad range of projects, including n-tier architecture, legacy applications, open systems, Web-based applications, and e-business solutions.
Review By: Diane C. Albert 07/09/2010This book discusses people-issues in project management as well as task-issues. For someone completely new to the topic of project management, this is a text that builds from the ground up, much like an introductory course. The first few chapters approach an overview of how the typical corporate ladder is structured and how involved each level of management might be when dealing with a software project. The text presents details that might need to be accomplished by a project manager in an enlightening fashion, especially for those having no previous experience. It gives the nonmanager insight into the difficulties that might arise and how the project manager could handle them. Tool strategies available to the project manager are detailed for more effective management of any size project.
In addition, the text discusses the different types of leadership roles one might find in a project manager and how that style can strengthen or weaken the project. There is extensive detail on the human element of why projects succeed and why projects fail. Some of these issues cannot readily be changed, so they must be planned for in advance. Others deal with the group dynamics by using scenarios and case studies. The text provides creative analogies to project management by using common ideas, such as purchasing a vehicle; then relating that same methodology to working on a software project.
The text also provides managerial surveys, templates, and a tutorial for Microsoft Project 2000.
The book covers a lot of material very efficiently. As a former computer instructor, I clearly appreciated the initial references to something outside the software world for those who have never experienced project management. The readability of the text was great—both font and white space made it easy on the eyes. I can recommend this book to someone who is truly interested in project management; however, I do not find it a suitable text for those who are interested in testing or in furthering their QA department. The level of inference to software testing or how to structure testing within the project is not the focus.
Because of the tutorials for MS Project, I do believe this would make a good instructional manual for a project management course in a college setting. The writing and layout are geared for the student of project management. One downside to the layout of the book is for those who like to refer back to specific elements. While the chapters are subsectioned, the organization does not make it easy to spot read to find a certain area or subtopic.