FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W20012019> ?p ?o ?g. }

• W20012019 abstract "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." @default.
• W20012019 created "2016-06-24" @default.
• W20012019 creator A5024910332 @default.
• W20012019 date "2015-01-01" @default.
• W20012019 modified "2023-09-27" @default.
• W20012019 title "Exploring Government Contractor Experiences Assessing and Reporting Software Development Status" @default.
• W20012019 cites W122154057 @default.
• W20012019 cites W1482052294 @default.
• W20012019 cites W1490646913 @default.
• W20012019 cites W1505535866 @default.
• W20012019 cites W1505648523 @default.
• W20012019 cites W1533707383 @default.
• W20012019 cites W1537033052 @default.
• W20012019 cites W1547450212 @default.
• W20012019 cites W1572092804 @default.
• W20012019 cites W1572121405 @default.
• W20012019 cites W1587738184 @default.
• W20012019 cites W1648883014 @default.
• W20012019 cites W1803273808 @default.
• W20012019 cites W1840884391 @default.
• W20012019 cites W1859502711 @default.
• W20012019 cites W1946080619 @default.
• W20012019 cites W1963521582 @default.
• W20012019 cites W1964962870 @default.
• W20012019 cites W1974383829 @default.
• W20012019 cites W1976534969 @default.
• W20012019 cites W1980797385 @default.
• W20012019 cites W1984314602 @default.
• W20012019 cites W1986585894 @default.
• W20012019 cites W1996600674 @default.
• W20012019 cites W2005331410 @default.
• W20012019 cites W2005875437 @default.
• W20012019 cites W2018828965 @default.
• W20012019 cites W2019015573 @default.
• W20012019 cites W2021730854 @default.
• W20012019 cites W2021811474 @default.
• W20012019 cites W2041628322 @default.
• W20012019 cites W2051893023 @default.
• W20012019 cites W2074636452 @default.
• W20012019 cites W2075858644 @default.
• W20012019 cites W2077242985 @default.
• W20012019 cites W2079666365 @default.
• W20012019 cites W2082744923 @default.
• W20012019 cites W2083566072 @default.
• W20012019 cites W2093234417 @default.
• W20012019 cites W2095996319 @default.
• W20012019 cites W2111562224 @default.
• W20012019 cites W2120525070 @default.
• W20012019 cites W2121057544 @default.
• W20012019 cites W2121111390 @default.
• W20012019 cites W2121866145 @default.
• W20012019 cites W2122519137 @default.
• W20012019 cites W2138661194 @default.
• W20012019 cites W2152458990 @default.
• W20012019 cites W2158335989 @default.
• W20012019 cites W2158864412 @default.
• W20012019 cites W2159765281 @default.
• W20012019 cites W2161477496 @default.
• W20012019 cites W2161842391 @default.
• W20012019 cites W2187508113 @default.
• W20012019 cites W2222439507 @default.
• W20012019 cites W2331802041 @default.
• W20012019 cites W2400818864 @default.
• W20012019 cites W2586801283 @default.
• W20012019 cites W2598063492 @default.
• W20012019 cites W2624972722 @default.
• W20012019 cites W2986348978 @default.
• W20012019 cites W3044165892 @default.
• W20012019 cites W41412440 @default.
• W20012019 cites W566408148 @default.
• W20012019 cites W596995053 @default.
• W20012019 cites W630309035 @default.
• W20012019 cites W630875085 @default.
• W20012019 cites W886883501 @default.
• W20012019 cites W2022933252 @default.
• W20012019 cites W2187457833 @default.
• W20012019 hasPublicationYear "2015" @default.
• W20012019 type Work @default.
• W20012019 sameAs 20012019 @default.
• W20012019 citedByCount "0" @default.
• W20012019 crossrefType "journal-article" @default.
• W20012019 hasAuthorship W20012019A5024910332 @default.
• W20012019 hasConcept C127413603 @default.
• W20012019 hasConcept C138885662 @default.
• W20012019 hasConcept C144133560 @default.
• W20012019 hasConcept C15952604 @default.
• W20012019 hasConcept C17744445 @default.
• W20012019 hasConcept C195094911 @default.
• W20012019 hasConcept C201995342 @default.
• W20012019 hasConcept C2778137410 @default.
• W20012019 hasConcept C39549134 @default.
• W20012019 hasConcept C41008148 @default.
• W20012019 hasConcept C41895202 @default.
• W20012019 hasConcept C56739046 @default.
• W20012019 hasConceptScore W20012019C127413603 @default.
• W20012019 hasConceptScore W20012019C138885662 @default.
• W20012019 hasConceptScore W20012019C144133560 @default.
• W20012019 hasConceptScore W20012019C15952604 @default.
• W20012019 hasConceptScore W20012019C17744445 @default.
• W20012019 hasConceptScore W20012019C195094911 @default.

• next