Drishtikon: A Management Journal

Open Access Open Access  Restricted Access Subscription Access
Open Access Open Access Open Access  Restricted Access Restricted Access Subscription Access

Scope Creep, Scrap & churn are not Sins in Requirements Engineering


Affiliations
1 Senior Project Manager, HCL Technologies Ltd
2 Professor, Department of Management Studies, AMET University, Chennai
     

   Subscribe/Renew Journal


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.
Subscription Login to verify subscription
User
Notifications
Font Size


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

  • Chaos Report on Project Failure, published by http://blog.standishgroup.com

  • Daniela E. Damian and Didar Zowghi, “Requirements engineering challenges in multi-site software development organizations”, Requirements Enginnering Journal, 2003, pages 149-160

  • G.P. Kulk, C. Verhoef, “Quantifying requirements volatility effects”, VU University Amsterdam, Department of Computer Science, de Boelelaan 1081a, 1081 HV Amsterdam, The Netherlands, pages 136-150

  • Gerald M. Weinberg, “Exploring Requirements: Quality before Design” 2011, Dorset House Publishing

  • Linda Westfall, “Software requirements engineering: What, Why, Who, When and How”, 2006, pages 8-14, www.westfallteam.com

  • Wiegers, K. E, “In search of excellent requirements. Process Impact Web site”, 2004, http://www.processimpact.com

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


Abstract Views: 335

PDF Views: 2




  • Scope Creep, Scrap & churn are not Sins in Requirements Engineering

Abstract Views: 335  |  PDF Views: 2

Authors

S P Rahmesh
Senior Project Manager, HCL Technologies Ltd
B Madhavan
Professor, Department of Management Studies, AMET University, Chennai

Abstract


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.

References