Exploring Government Contractor Experiences Assessing and Reporting Software Development Status

Exploring Government Contractor Experiences Assessing and Reporting Software Development Status by Putnam P. Texel MS, Fairleigh Dickinson University, 1968 BA, Fairleigh Dickinson University, 1967 Dissertation Submitted in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy Management Walden University February 2015 Abstract Reports from academic, commercial, and government organizations have documented software-intensive system cost and schedule overruns for decades. These reports have identified lack of management insight into the software development process as one of many contributing factors. Multiple management mechanisms exist. However, these mechanisms do not support the assessment, and subsequent reporting, of software completion status. Additionally, the conceptual framework, based on industry standards, is limited in its relevance to this study due to an emphasis on what is needed while deferring implementation details. The purpose of this phenomenological study was to explore U.S. government contractors’ lived experiences of assessing and reporting software completion status with current measurement mechanisms. Twenty program or project managers responded to interview questions targeting positive and challenging experiences with current measurement mechanisms. Qualitative analysis of the experiential data was based on open and axial coding conducted on interview transcripts. Analysis indicated that costly resources are applied to metrics that do not provide the required level of management insight into completion status. These findings have positive social change implications for program managers, project managers, and researchers by documenting the need to develop relevant and cost-efficient status metrics to provide the critical insight required by management to reduce overruns.Reports from academic, commercial, and government organizations have documented software-intensive system cost and schedule overruns for decades. These reports have identified lack of management insight into the software development process as one of many contributing factors. Multiple management mechanisms exist. However, these mechanisms do not support the assessment, and subsequent reporting, of software completion status. Additionally, the conceptual framework, based on industry standards, is limited in its relevance to this study due to an emphasis on what is needed while deferring implementation details. The purpose of this phenomenological study was to explore U.S. government contractors’ lived experiences of assessing and reporting software completion status with current measurement mechanisms. Twenty program or project managers responded to interview questions targeting positive and challenging experiences with current measurement mechanisms. Qualitative analysis of the experiential data was based on open and axial coding conducted on interview transcripts. Analysis indicated that costly resources are applied to metrics that do not provide the required level of management insight into completion status. These findings have positive social change implications for program managers, project managers, and researchers by documenting the need to develop relevant and cost-efficient status metrics to provide the critical insight required by management to reduce overruns. Exploring Government Contractor Experiences Assessing and Reporting Software Development Status by Putnam P. Texel MS, Fairleigh Dickinson University, 1968 BA, Fairleigh Dickinson University, 1967 Dissertation Submitted in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy Management Walden University February 2015 Dedication This dissertation is dedicated to my grandfather, Ruel Putnam Pope, who made this journey possible; my grandmother, Ruth Patillo Griffin Pope, who taught me grace and humility; and my grandchildren, Myles, Morgan, and Finn Texel, all of whom I hope will grow to treasure the continual gift of learning. Acknowledgments The following individuals created a team composed of different strengths and skills that, when taken as a whole, provided an A++ support system. • My sister, Penny Prichard, my soul mate, for her encouragement, support, inspiration, and, above all, never failing to answer the telephone and listen. • My friends and colleagues, Trisha-Marie Uhl, Linda May, Betsey Nohe, Cheryl Douthitt, Lori Larson, and Colleen Hanrahan, for being who they are—strong, intelligent women who never forget caring and compassion. • Dr. Mark Ellinger and Dr. William Tollefson, who supported me through this journey and were instrumental in the achievement of my goal. And last, but by no means least, to my chair, Dr. Branford McAllister, whose neverfailing optimism, encouragement, and focused input kept me continually striving to improve; to Dr. David Gould, for his encouragement and discussions that proved so beneficial; to Dr. Robert Kilmer, for his time and expertise in this problem domain as well as his knowledge of APA mechanics; to John Tripp of Academic Advising, for his help and knowledge of the PhD process; to the Writing Center and Library staff for their experience and professionalism; and to Student Technical Support for their help as we transitioned to Blackboard and Google mail. All these individuals contributed to the fulfillment of my dream, and I am deeply grateful to each and every one.