Open Access Open Access  Restricted Access Subscription or Fee Access

Scope Creep, Scrap & Churn are NOT SINS in Requirements Engineering

S.P. Rahmesh, Dr B. Madhavan


This article covers the entire spectrum of requirement gathering process and how it should function to handle creep, scrap or churn of the scope of the project requirements. Requirements engineering is a discipline that builds the foundation for any project to get implemented successfully. Organizations with very good processes, people and tools along with good experience, too fail when scope creep, scrap or churn takes place in the project. What’s the impact on cost, schedule, resources and to business? How to efficiently handle such scenarios? Volatility of requirements is a factor should be measured and controlled using benchmark values.


Requirements Engineering, Churn, Creep, Scrap, Tools, Software Requirements Specifications (SRS).

Full Text:



Exploring Requirements: Quality before Design by Gerald M. Weinberg

Quantifying requirements volatility effects By G.P. Kulk, C. Verhoef, VU University Amsterdam, Department of Computer Science, de Boelelaan 1081a, 1081 HV Amsterdam, The Netherlands

A.J. Albrecht, Measuring application development productivity, in: Proceedings of the Joint SHARE/GUIDE/IBM Application Development Symposium, 1979, pp. 83—92

Wiegers, K. E. 2003. Software requirements, 2nd Edition. Redmond, Wash.: Microsoft Press.

Wiegers, K. E. 2004. In search of excellent requirements. Process Impact Web site. See URL:


  • There are currently no refbacks.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.