Incomplete or missed requirements, omissions, ambiguous product features, lack of user involvement, unrealistic customer expectations, and the proverbial scope creep can result in cost overruns, missed deadlines, poor product quality, and can very well ruin a project. This book explains how to elicit, document, and manage requirements to control project scope creep. It also describes how to manage project stakeholders to minimize the risk of an ever-growing list of user requirements. The book examines five different projects and traces their development from a project scope management perspective.
