Evaluating Project Decisions: Case Studies in Software Engineering Review

Average Reviews:

(More customer reviews)Carl L. Hoover, Mel Rosso-Llopart and Gil Taran's EVALUATING PROJECT DECISIONS is a powerful survey of software project managers introducing an innovative design model to help evaluate decisions. From project stages and objectives to proper product definition and business decision impacts on stakeholders and global development, this is a key for both software and business libraries alike.

Click Here to see more reviews about: Evaluating Project Decisions: Case Studies in Software Engineering

Product Description:

Effective decisions are crucial to the success of any software project, but to make better decisions you need a better decision-making process. In Evaluating Project Decisions, leading project management experts introduce an innovative decision model that helps you tailor your decision-making process to systematically evaluate all of your decisions and avoid the bad choices that lead to project failure.Using a real-world, case study approach, the authors show how to evaluate software project problems and situations more effectively, thoughtfully assess your alternatives, and improve the decisions you make. Drawing on their own extensive research and experience, the authors bridge software engineering theory and practice, offering guidance that is both well-grounded and actionable. They present dozens of detailed examples from both successful and unsuccessful projects, illustrating what to do and what not to do.Evaluating Project Decisions will help you to analyze your options and ultimately make better decisions at every stage in your project, including:

Requirements–Elicitation, description, verification, validation, negotiation, contracting, and management over the software life cycle
Estimates–Conceptual solution design, decomposition, resource and overhead allocation, estimate construction, and change management
Planning–Defining objectives, policies, and scope; planning tasks, milestones, schedules, budgets, staff and other resources; and managing projects against plans
Product–Proper product definition, development process management, QA, configuration management, delivery, installation, training, and field service
Process–Defining, selecting, understanding, teaching, and measuring processes; evaluating process performance; and process improvement or optimization

In addition, you will see how to evaluate decisions related to risk, people, stakeholder expectations, and global development. Simply put, you'll use what you learn here on every project, in any industry, whatever your goals, and for projects of any duration, size, or type.

Get 19% OFF

Want to read more honest consumer review about Evaluating Project Decisions: Case Studies in Software Engineering now ?

Software Project Management: A Unified Framework Review

Average Reviews:

(More customer reviews)If you aren't versed in advanced project management techniques this book will be overwhelming.More important you may pick up misleading information.However, if you are a battle-scared veteran of software development projects and have a full understanding of earned value project management, estimating techniques and development life cycles you'll learn much from this book.
The highlights are:
* A project life cycle and process framework that is [obviously] closely aligned to the Rational Unified Process (RUP), and can be fitted to any rapid development or iterative approach.
* An excellent tutorial on effective project controls, with an emphasis on earned value project management.
* In-depth coverage of estimating techniques, with a lot of material on the constructive cost model (CoCoMo), and current gaps in estimating techniques and to where the craft and science of estimating and software economics needs to evolve in the discussion of next-generation cost models.I especially like his distinction between the use of source lines of code metrics for size and function points for scale.There is middle ground.The treasure trove of metrics, including core project metrics, and the change metrics that are given in Appendix C.
There is one glaring flaw in this book and an experienced project manager will quickly spot it:the proposed approach to basing work breakdown structures on project phases instead of the decomposition of the system to be delivered will not work.Using Royce's approach there is no clear way of integrating the work breakdown structure with the organizational breakdown structure.Using earned value techniques (which is well covered elsewhere in the book) Royce's approach will not align control accounts (sometimes called cost accounts), making his recommendations contrived and unworkable.
This book is better suited for an architecture-centric approach to project management, which means that it's more applicable to product development instead of internal IT projects. However, all seasoned PMs will learn much from it.

Click Here to see more reviews about: Software Project Management: A Unified Framework

Get 15% OFF

Want to read more honest consumer review about Software Project Management: A Unified Framework now ?