Corporate Software Project Management (Charles River Media Computer Engineering) 1st Edition
| Guy W. Lecky-Thompson (Author) Find all the books, read about the author, and more. See search results for this author |
Use the Amazon App to scan ISBNs and compare prices.
Editorial Reviews
About the Author
I'd like to read this book on Kindle
Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.
Product details
- Publisher : Charles River Media; 1st edition (January 31, 2005)
- Language : English
- Paperback : 376 pages
- ISBN-10 : 1584503858
- ISBN-13 : 978-1584503859
- Item Weight : 2.2 pounds
- Dimensions : 7.5 x 1.25 x 9.25 inches
- Customer Reviews:
About the author

Guy W. Lecky-Thompson is an experienced author in the field of video game design and software development, whose articles have been published in various places, including Gamasutra, Dr. Dobbs magazine and the seminal Game Programming Gems. He is also the author of Corporate Software Project Management, Infinite Game Universe: Mathematical Techniques, and Infinite Game Universe, Volume 2: Level Design, Terrain, and Sound.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on AmazonTop reviews from the United States
There was a problem filtering reviews right now. Please try again later.
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.
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.
