Project Scope Management: A Practical Guide to Requirements for Engineering, Product, Construction, IT and Enterprise Projects (Best Practices in Portfolio, Program, and Project Management)

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. **Project Scope Management: A Practical Guide to Requirements for Engineering, Product, Construction, IT and Enterprise Projects** describes how to elicit, document, and manage requirements to control project scope creep. It also explains how to manage project stakeholders to minimize the risk of an ever-growing list of user requirements. The book begins by discussing how to collect project requirements and define the project scope. Next, it considers the creation of work breakdown structures and examines the verification and control of the scope. Most of the book is dedicated to explaining how to collect requirements and how to define product and project scope inasmuch as they represent the bulk of the project scope management work undertaken on any project regardless of the industry or the nature of the work involved. The book maintains a focus on practical and sensible tools and techniques rather than academic theories. It examines five different projects and traces their development from a project scope management perspective—from project initiation to the end of the execution and control phases. The types of projects considered include CRM system implementation, mobile number portability, port upgrade, energy-efficient house design, and airport check-in kiosk software. After reading this book, you will learn how to create project charters, high-level scope, detailed requirements specifications, requirements management plans, traceability matrices, and a work breakdown structure for the projects covered. Front Cover 1 Contents 8 Foreword 16 Preface 20 About the Author 28 Chapter 1: Introduction to Scope Management Who? What? Why? 30 Chapter 2: History of Scope Management 46 Chapter 3: Writing Project Charters 64 Chapter 4: Requirements,Customers, Users 84 Chapter 5: High-Level Scope Eli citation 114 Chapter 6: Detailed Requirements Eli citation 146 Chapter 7: Documenting Requirements Information Technology and Software Development Projects 182 Chapter 8: Documenting Requirements Engineering and Product Development Projects 204 Chapter 9: Documenting Requirements Multidisciplinary Projects 218 Chapter 10: Creating the Requirements Management Plan and Requirements Traceability Matrix 232 Chapter 11: Final Product Design 244 Chapter 12: Creating Work Breakdown Structures and WBS Dictionaries 266 Chapter 13: TroubleshootingScope Problems 288 Chapter 14: Scope Verification 306 Chapter 15: Controlling Project Scope 320 References and Additional Reading 340 Back Cover 344 "Moustafaev,Jamal" 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. Foreword Preface About the author Introduction to scope management : who? History of scope management Writing project charters Requirements, customers, users High-level scope elicitation Detailed requirements elicitation Documenting requirements : information technology and software development projects Final product design Creating work breakdown structures and WBS dictionaries Troubleshooting scope problems Scope verification Controlling project scope.