Customer Reviews

Discovering Real Business Requirements for Software Project Success (Computing Library S.)

5 star:		(4)
4 star:		(2)
3 star:		(0)
2 star:		(0)
1 star:		(0)

 

 

If you ever wanted to know if your requirements were accurate and complete, this book will help. As Robin says on p. 13, "...we're going to intermix discovery methods with techniques for testing the adequacy of requirements." Using his problem pyramid - which includes a way to measure the problem and the solution - Robin discusses several techniques to elicit and define requirements.

Robin defines 64 techniques to test requirements - throughout a project. For example, test method #17, "identify assumptions" is common sense that too few people remember. Test method #53 is "Defining acceptance criteria," a technique useful for any project if you want to know you've built what the customer wanted.

Between the problem pyramid emphasis on measurement and the various tests, the book can help you meet its promise of preventing too much requirements change throughout a project.

As a Software Developer and Consultant, I found this book to be a clear and practical guide that will be a valuable asset to all system development professionals.

I strongly recommend it to all systems professionals, and believe it is a MUST HAVE for systems analysts !

The book presents a step-by-step methodology that contrasts how things are "normally" done with how they should be done to achieve optimum results and satisfied customers.

In addition to analyzing why and how traditional approaches fail, the text provides a comprehensive checklist that can be followed to avoid common mistakes and improve the quality of the most significant aspect of develop: gathering and documenting requirements !

Presented in a easy-to-read format sprinkled with wry humor, you are likely to find it a more enjoyable read than most technical texts.

The 64 ways to test requirements are good and helpful, and you'll need to determine how many of these techniques (and with what rigor) could/should be applied to your project in your organizational context. The greatest benefit for me from reading this book was understanding the distinction Goldsmith makes between business problems and the solution design alternatives that might address them. I've witnessed problems on projects where this distinction was not understood, and I'm convinced that identifying the business problem(s) and business requirements first is critical before undertaking software requirements and solution alternatives.

Concise, addressing the essentials of discovering the 'real' business requirements of an organization. Effective and efficient testing methodologies that are readily applicable to requirements analysis. I found the "Problem Pyramid" tool to be particularly useful. Differentiation between the 'business requirements' vs 'system design requirements' was enlightening. Every technologist should be reading this book to ensure that the real business requirements are discovered before any coding begins. Excellent knowledge for account managers and business analysts as well. Strongly recommended.

I wanted to find a book that I could recommend to my requirements-challenged clients. This was the first I bought and the last I'll need. The author has a solid command of the subject and obvious real-world experience. Nestled among the chapters are over 60 "tests" to tell if you have real requirements.

I only gave it four stars because I was put off by the author's tilting at windmills in the first few chapters as he tries to stave off imagined criticism.

This book will be a great aid for me in helping Business Users to make better requests by outlining the business problems in such a way that technicians can meet their needs with fewer false starts.