Could removal of project-level knowledge flow obstacles contribute to software process improvement? A study of software engineer perceptions

详细信息    查看全文

• 作者：Susan M. Mitchell ; ^{susan.mitchell@comcast.net" class="auth_mail" title="E-mail the corresponding author} ; Carolyn B. Seaman¹ ; ^{cseaman@umbc.edu" class="auth_mail" title="E-mail the corresponding author}
• 关键词：Software process ; Software process improvement ; SPI ; Knowledge management ; Knowledge flow (K-flow) ; Software engineering
• 刊名：Information and Software Technology
• 出版年：2016
• 出版时间：April 2016
• 年：2016
• 卷：72
• 期：Complete
• 页码：151-170
• 全文大小：4037 K

文摘

Software process improvement (SPI) is one type of innovation often formulated to address problems such as uncontrollable costs, schedule overruns, and poor end product quality. This study investigates SPI through the application of knowledge management (KM) at the software project level, viewing KM, when applied in software development, as complementary to SPI.

Objective

This study advances the use of KM in SPI by investigating impediments to the use and flow of knowledge within an individual software development project. Our proposition is that the removal of obstacles to project-level knowledge flow (K-flow) will enhance SPI. We investigate this proposition by exploring the problems associated with project K-flows as seen by software project team members.

Method

We conducted a descriptive case study of an industrial software development project, in which we collected data concerning project knowledge sources and K-flows using semi-structured interviews. Using this data, we constructed a diagnostic project knowledge map (K-map). The K-map was analyzed to identify K-flow obstacles and potential solutions. Questionnaires based on these obstacles and solutions were formulated to probe software engineers’ perceptions of the effect of the solutions on SPI.

Results

Findings from participant questionnaires reveal that software engineers perceive that the removal or mitigation of project-level K-flow obstacles generally reduces the time to perform their work, helps them to meet their deadlines, and improves their work quality, thus resulting in SPI.

Conclusions

This study provides support for the usefulness of project-level K-flow obstacle removal for SPI. It provides a unique project-level perspective, using input from the project's software engineers. It also explains and supports the use of K-mapping for the identification of project-level K-flow obstacles. With this approach, practitioners gain insight into SPI in “real time” as a project is executed. These insights may help to enhance their current and future SPI efforts.