How to Rescue Failing Software Projects: Practical Proven Methods That Work
My book is finally available as an eBook, on Amazon Kindle and on Amazon. I wrote this book to share my experience in how to rescue failing software projects. When I was going through such a situation, I had no one to turn to. My hope is that the information in this book will be useful to those in similar situations. Although the information in the book pertains to software projects, I have come to realize that the techniques can be used in many other situations. I have personally used these techniques in business and technical projects.
Monday, March 28, 2011
Deluge of Project Documentation
I have found that nothing can be further from the truth. Many of these documentation took a long time to create, edit and review...and never used again. What a waste of effort and time, time that could be have been put to better use.
However, I do agree that documentation is required. There has to be a balance as to what is essentially required, what is nice to have. Those that are essential to the project will always be referenced, used, corrected, modified to reflect the project's current status.
Documentation should be used as a means to record critical decision points, important design elements and motivation behind the through process.
I do not recommend going overboard with documentation. A careful selection of project documentation will serve the project well during its formative stages, through its operational phases and till it is retired from operation. Add in additional documentation only as needed to serve a critical specific purpose that can be used throughout the project's lifecycle.
Save This Page
Copyright © Bernard Ong, 2006-2011.
All Rights Reserved