Requirements-Led Project Management: Discovering David's Slingshot (Hardcover)

by Suzanne Robertson (Author), James C. Robertson (Author)

Editorial Reviews

Product Description
Requirements are a crucial ingredient of any successful project. This is true for any product--software, hardware, consumer appliance, or large-scale construction. You have to understand its requirements--what is needed and desired--if you are to build the right product. Most developers recognize the truth in this statement, even if they don't always live up to it. Far less obvious, however, is the contribution that the requirements activity makes to project management. Requirements, along with other outputs from the requirements activity, are potent project management tools. In Requirements-Led Project Management, Suzanne and James Robertson show how to use requirements to manage the development lifecycle.They show program managers, product and project managers, team leaders, and business analysts specifically how to: *Use requirements as input to project planning and decision-making *Determine whether to invest in a project *Deliver more appropriate products with a quick cycle time *Measure and estimate the requirements effort *Define the most effective requirements process for a project *Manage stakeholder involvement and expectations *Set requirements priorities *Manage requirements across multiple domains and technologies *Use requirements to communicate across business and technological boundaries In their previous book, Mastering the Requirements Process, the Robertsons defined Volere--their groundbreaking and now widely adopted requirements process. In this second book, they look at the outputs from the requirements process and demonstrate how you can take advantage of the all-important links between requirements and project success.

From the Back Cover

Requirements are a crucial ingredient of any successful project. This is true for any product--software, hardware, consumer appliance, or large-scale construction. You have to understand its requirements--what is needed and desired--if you are to build the right product. Most developers recognize the truth in this statement, even if they don't always live up to it.

Far less obvious, however, is the contribution that the requirements activity makes to project management. Requirements, along with other outputs from the requirements activity, are potent project management tools.

In Requirements-Led Project Management, Suzanne and James Robertson show how to use requirements to manage the development lifecycle. They show program managers, product and project managers, team leaders, and business analysts specifically how to:

• Use requirements as input to project planning and decision-making
• Determine whether to invest in a project
• Deliver more appropriate products with a quick cycle time
• Measure and estimate the requirements effort
• Define the most effective requirements process for a project
• Manage stakeholder involvement and expectations
• Set requirements priorities
• Manage requirements across multiple domains and technologies
• Use requirements to communicate across business and technological boundaries

In their previous book, Mastering the Requirements Process, the Robertsons defined Volere--their groundbreaking and now widely adopted requirements process. In this second book, they look at the outputs from the requirements process and demonstrate how you can take advantage of the all-important links between requirements and project success.

See all Editorial Reviews

Product Details

• Hardcover: 352 pages
• Publisher: Addison-Wesley Professional (August 30, 2004)
• Language: English
• ISBN-10: 0321180623
• ISBN-13: 978-0321180629
• Product Dimensions: 9.5 x 7.7 x 1.1 inches
• Shipping Weight: 2.1 pounds
• Average Customer Review: 3.5 out of 5 stars See all reviews (6 customer reviews)
• Amazon.com Sales Rank: #717,753 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

17 of 17 people found the following review helpful:

3.0 out of 5 stars Not Bad but Not Great, September 21, 2004

By	Earl Beede (Maltby, WA USA) - See all my reviews (REAL NAME)

This is a decent book on using software requirements to help center and guide the running software projects. The Robertsons break no new ground here that wasn't probably better explained in their "Mastering the Requirements Process" for the requirements aspects of the book. As a project management book, I think that requirements are important but so are many things in running a project. I have found the Robertsons approach a bit too simplistic and I think that shows on the project management side as well.
The key message here is that if you get the requirements right, the project will fall into place and run much better. Requirements are key to getting good estimates, scheduling, aligning stakeholders, testing, etc. Well this is true, but hard. The Robertsons talk Agile talk but don't do the Agile walk. One of the keys to Agile is that full, complete, or even mostly complete requirements are a myth. Learn a little, build a little. The Robertsons change that to learn a lot, build a little. Not quite the same. I personally agree that we should learn more about the problem space of a software project than what some Agile methods call for. Then again, I don't reference Beck and Folwer as much as the Robertsons do.
What I personally am having difficulty doing is agreeing to the Robertsons advice to "invent" requirements. To me this is a slippery slope not worth going down. I think the requirements analyst's job is to fully understand the business problem space, perhaps better than the stakeholders themselves. I would like to leave it to the designers to invent the solutions. Sometimes that is the same person and that is OK by me. However, I think as an activity list, they should be different categories.
So, if you have read "Mastering the Requirements Process" and you are primarily interested in requirements techniques, there isn't much need to buy this book. If you are into project management and want a different viewpoint from many of the PM books out there, this may work for you.

7 of 8 people found the following review helpful:

3.0 out of 5 stars Somewhat Misleading Title, February 24, 2005

By	Tezza "Tezza" (USA) - See all my reviews

The title suggests that you will understand how a project can be managed from a requirements perspective. In actual fact the book is a treatise on how to create and manage software requirements during the requirements gathering phase of a project.

The book touches on important aspects of creating and managing software requirements such as writing testable requirements, creating use cases, drawing context diagrams, etc.

Some of the statements within the book are questionable. For instance (I'm paraphrasing), a requirement is not a requirement if you can't afford to build it. I've found that prejudicing requirements sessions with early budget and technical constraints is, at best, counter-productive.

Also, the discussion of the change control over requirements (and it's impact on the design, test plans, construction deliverables) is given short shrift within this text. The suggestion is made that if requirements were well done to begin with, there wouldn't be changes. Surely better requirements provide better requirements stability, but any project would benefit by a fairly robust requirements-led change control process.

The bottom line is this is a good text on software requirements and related practices, but not a classic text. For that you may have to look elsewhere.

4 of 4 people found the following review helpful:

4.0 out of 5 stars Usefull resources on a dry topic, May 11, 2005

By	Jean-Charles (NYC) - See all my reviews

The process of aquiring and implementing the requirements for any project can be difficult. To read a book on the subject can be worse. This title succeeds where others fail. It is full of usefull resources and practical examples.

Project management and development is more an exercise is psychology than architecture. The Robertsons are aware of this and build their methods around human interaction.

I'm glad I read it. I learned quite a bit. The other books reccomended throughout this title are a great find and the recipe for the perfect dry martini is in fact quite accurate.

Jean-Charles
www.FlashCodersNY.org