What Is a Requirement, Really?

Advisor

What Is a Requirement, Really?

Posted September 9, 2010 | Leadership |

Requirements define things that a product or service are supposed to do to satisfy the needs of the client. A more formal definition is given by the International Institute of Business Analysis in "A Guide to the Business Analysis Body of Knowledge" (PDF):

About The Author

Robert Wysocki

Robert K. Wysocki, Ph.D. is a Senior Consultant with Cutter Consortium's Agile Product & Project Management Practice. Bob is recognized throughout the industry as a strategic leader in project management. Among his many outstanding accomplishments, he is the author, or co-author, of numerous books, including Effective Project Management: Traditional, Agile, Extreme, Effective Project Management, 5-Phase Project Management, Effective and… Read More

Don’t have a login? Make one! It’s free and gives you access to all Cutter research.

	Digitally Disrupted! Decision Making and the Connected Architecture
	Five-Stage Strategy Execution, Fast Feedback Processes, Production Line IT
	A Million-Dollar Question: Will Companies Use AI to Extend Their RPA Platforms?
	Bouncing Back from COVID-19, Part II: Telecom, Equipment Vendors, and Internet Services
	A Look at Mitigating Risk in 2020
	Value Stream Mapping: 8 Steps to Get You Started

What Is a Requirement, Really?

Subscribe to free newsletters

Contact us