carnevalemanfredonia.it
» » On Time, Within Budget: Software Project Management Practices and Techniques

eBook On Time, Within Budget: Software Project Management Practices and Techniques download

by E. M Bennatan

eBook On Time, Within Budget: Software Project Management Practices and Techniques download ISBN: 0894354086
Author: E. M Bennatan
Publisher: QED Pub. Group; First Edition edition (1992)
Language: English
Pages: 206
ePub: 1989 kb
Fb2: 1679 kb
Rating: 4.7
Other formats: lrf doc lit azw
Category: Technologies
Subcategory: Programming

A project manager's survival guide-Tells you everything you need to know to develop software on time, within budget, and to your clients' complete satisfaction. For every exhausted project manager, here is something that's guaranteed to save you many a sleepless night.

A project manager's survival guide-Tells you everything you need to know to develop software on time, within budget, and to your clients' complete satisfaction. It's a unique survival guide packed with expert advice, guidelines, and tips and tricks that make it easier than ever to develop software on schedule, within budget, and to your clients' total satisfaction

Bennatan, E. M. (Edwin . Publication date.

Bennatan, E. Books for People with Print Disabilities. Internet Archive Books.

On Time, Within Budget book.

On Time, Within Budget Software Project Management Practices and Techniques.

Together, let's build an Open Library for the World. July 28, 2014 History. found in the catalog. On Time, Within Budget Software Project Management Practices and Techn.

Find many great new & used options and get the best deals for On Time 3E: Software Project Management Practices and . Author: E. Bennatan ISBN 10: 0471376442. Publisher: John Wiley & Sons ISBN 13: 9780471376446

Find many great new & used options and get the best deals for On Time 3E: Software Project Management Practices and Techniques,E. Publisher: John Wiley & Sons ISBN 13: 9780471376446. Published On: 2000-05-24 SKU: 8765-9780471376446.

Conventional project management techniques won’t save these projects: there are no standard rescue processes to. .Drawing on in-depth data from hundreds of development organizations, .

Conventional project management techniques won’t save these projects: there are no standard rescue processes to follow. You need something radically different: Catastrophe Disentanglement. Bennatan presents a proven, 10-step program for rescuing any project that’s worth saving. You’ll find specific guidance for addressing massive budget overruns, schedule slippage, poor quality-or all three at once.

A developer's survival guide packed with real-life case studies, tips, techniques, and best practices for completing software projects on time and within budget Whether you work at a large or small company, this book will provide you with expert, tips, techniques, and strategies to deliver a software project in a cost-effective and timely way. Real-life case studies let you learn from the mistakes as well as the successes of others.

Statistical PERT is an estimation technique that project professionals use to align expectations and . Bennatan.

Statistical PERT is an estimation technique that project professionals use to align expectations and make better business decisions. Use Statistical PERT to create a probabilistic forecast for many project uncertainties, such as how much the project will cost, or how long the project will take to deliver. This book will help you Activate your project Principles of Managing Software Engineers: Are They Really Any Different?, pg. 97. This book will help you Control your project Project Support Functions, pg.

On Time, Within Budget: Software Project Management Practices and Techniques. From the Publisher: A developer's survival guide packed with tips, tricks, and best practices for getting software projects in on time and within budget While there are plenty of books offering t. More). Catastrophe Disentanglement: Getting Software Projects Back on Track.

Comments: (7)
Centrizius
I had considered using this book in my Software Project Management class but have decided to have my students read others and stay away from it. On Time Within Budget positions managers as handling mostly technical decisions. Alas, many of these issues (to give just one example, selecting a client-server environment, section 7.4) have little to do with people and should be handled by the chief architect. Most projects where the manager has marginalized the architect or has been trying to wear the architect's hat fail miserably. If you want to become a good manager, look for books that tell you how to deal with peopleware. Get the right people, make sure that they can work at their best, and leave the technical decisions to the ones who can handle them best.
Falya
I don't usually write reviews but I was prompted to do this one because I strongly disagree with a preceding review. I am an EE senior manager and software development had always been a mystery to me until I got hold of On Time, Within Budget. I particularly found the following chapters helpful: Chapter 1 which includes reasons for project success and failure, Chapter 2 on risk management and how to reduce the cost of risk events, Chapter 5 on the management of software engineers, and most especially the Epilogue on pulling it all together, which provides a great overall perspective.
This book is full of real-life examples; it was clearly written by someone who has been down in the trenches. This adds credibility to the methods described.
I have learned a lot from the book and I use it as a reference regularly.
Dangerous
We (26 person team) just finished a 2+ year project using On Time Within Budget as our process guide. Bottom line: the project came in 7 weeks late -- not bad for a company used to 6 to 12 month schedule overruns. We'll do better next time with more experience on the methods described in the book. Advice to others: the chapters on estimation, standards, and risk analysis are great. The chapters on software teams, quality assurance and testing are good pointers to what we needed to know, but we also used other books on these subjects to fill in more details that we needed. Most everyone liked the epilogue (pulling it all together). This book helped to pull us out of the dark ages into modern software project management. Strongly recommended!
Gagas
If you have never been a project manager, and suddenly you need to learn rules of the game, this is a book I would recommend you to use as a reference material. It is easy to read, has real life examples and various templates related to project management are presented in this book. Highly recommended.
Wymefw
The author is definitely not as witty as, say, Grady Booch or Steve McConnell and the book is not as glamorous as theirs. To be fair, it does not provide the same insight into the software development process, either. However, I did use a couple of suggestions from this book. In particular, I used the layout of the Technical Proposal and the cost estimation formulas, which is more than I can say of most books I have read on the subject (e.g., Object Solutions : Managing the Object-Oriented Project, which is nevertheless much more interesting). Not the ultimate book on project management, but the author does not claim he found the much-coveted silver bullet.
Haralem
This is a great reference book -- I look up examples and methods regularly. I have been managing software development for several years and this is the first real project management book I have found that isn't full of sky-high theories. There are many down-to-earth ideas that I have implemented successfully. Risk Analysis (chapter 2) is a must, and Organizational Excellence (Chapter 10) should be read by every software organization (especially the opening anecdote). I really like the common sense epilogue -- If you don't do anything else do this. A classic.
Tehn
I think this book is a QUICK reference for any software professional working in a team or independent, ofcourse, in management perspective. This could have been had focus on certain important concepts instead of just introducing the names. I often refer to this book for a quick reference at work as I am involved in / leading a development team.
I was forced to buy this book for college course work. I found it boring, and I spent a lot of time trying to read the small print.