Measuring Software Development Waste in Open-Source Software Projects
Dhiraj SM Varanasi, Divij D, Sai Anirudh Karre, Y Raghu Reddy

TL;DR
This paper introduces five novel measures to quantify and manage Software Development Waste in open-source projects, aiming to improve efficiency and reduce resource waste.
Contribution
It proposes specific, measurable indicators for SDW and demonstrates their application on real open-source projects to aid waste management.
Findings
Identified key SDW indicators in open-source projects
Demonstrated the measures' applicability in real-world scenarios
Provided insights for better SDW management practices
Abstract
Software Development Waste (SDW) is defined as any resource-consuming activity that does not add value to the client or the organization developing the software. SDW impacts the overall efficiency and productivity of a software project as the scale and size of the project grows. Although engineering leaders usually put in effort to minimize waste, the lack of definitive measures to track and manage SDW is a cause of concern. To address this gap, we propose five measures, namely Stale Forks, Project Diversification Index, PR Rejection Rate, Backlog Inversion Index, and Feature Fulfillment Rate to potentially identify unused artifacts, building the wrong feature/product, mismanagement of backlog types of SDW. We apply these measures on ten open-source projects and share our observations to apply them in practice for managing SDW.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
