Abstract
Software projects today are often characterized by poor quality, schedule overruns and high costs. One of the reasons for this failure is the lack of management visibility or metrics for making the right decisions at the right time for corrective actions. But most of the software metrics proposed are theoretical and have little relevance in real-world projects. Given that software engineering is essentially a cognitive activity, an effective measurement framework which is validated empirically is needed to control the project and give directions to accomplish the project goals of the stakeholders. However, defining and implementing the right measurement framework is extremely challenging requiring a cross pollination of systems development and project management streams. This paper examines how a stakeholder driven Goal-Question-Metric (GQM) measurement framework was derived and empirically validated with a survey from seasoned software professionals.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
