Practice Selection Framework

Knowledge management (KM) in software engineering and software process improvement (SPI) are challenging. Most existing KM and SPI frameworks are too expensive to deploy or do not take an organization's specific needs or knowledge into consideration. There is thus a need for scalable improvement approaches that leverage knowledge already residing in the organizations. This paper presents the Practice Selection Framework (PSF), an Experience Factory approach, enabling lightweight experience capture and use by utilizing postmortem reviews. Experiences gathered concern performance and applicability of practices used in the organization, gained from concluded projects. Project managers use these as decision support for selecting practices to use in future projects, enabling explicit knowledge transfer across projects and the development organization as a whole. Process managers use the experiences to determine if there is potential for improvement of practices used in the organization. This framework was developed and subsequently validated in industry to get feedback on usability and usefulness from practitioners. The validation consisted of tailoring and testing the framework using real data from the organization and comparing it to current practices used in the organization to ensure that the approach meets industry needs. The results from the validation are encouraging and the participants' assessment of PSF and particularly the tailoring developed was positive.

[1]  Tony Gorschek,et al.  Industry evaluation of the Requirements Abstraction Model , 2007, Requirements Engineering.

[2]  Claes Wohlin,et al.  Experimentation in Software Engineering , 2000, The Kluwer International Series in Software Engineering.

[3]  Tony Gorschek,et al.  A Lightweight Innovation Process for Software-Intensive Product Development , 2010, IEEE Software.

[4]  Robert L. Glass,et al.  Loyal Opposition - Frequently Forgotten Fundamental Facts about Software Engineering , 2001, IEEE Softw..

[5]  Johan Malmqvist,et al.  Requirements management in practice: findings from an empirical study in the automotive industry , 2006 .

[6]  Marvin V. Zelkowitz,et al.  Culture Conflicts in Software Engineering Technology Transfer , 1998 .

[7]  Fredrik Törner,et al.  An Empirical Quality Assessment of Automotive Use Cases , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[8]  Tony Gorschek,et al.  Test-Case Driven Inspection of Pre-Project Requirements : Process Proposal and Industry Experience Report , 2005 .

[9]  Tony Gorschek,et al.  Handshaking Between Software Projects and Stakeholders Using Implementation Proposals , 2007, REFSQ.

[10]  James D. Herbsleb,et al.  Modelling the Likelihood of Software Process Improvement: An Exploratory Study , 2004, Empirical Software Engineering.

[11]  Victor R. Basili,et al.  Experience in Implementing a Learning Software Organization , 2002, IEEE Softw..

[12]  Reidar Conradi,et al.  A Survey of Case Studies of the Use of Knowledge Management in Software Engineering , 2002, Int. J. Softw. Eng. Knowl. Eng..

[13]  Andy J. Nolan,et al.  Learning from Success , 1999, IEEE Softw..

[14]  Reidar Conradi,et al.  Improving Software Process Improvement , 2002, IEEE Softw..

[15]  M. Zedtwitz Organizational Learning through Post-project Reviews in R&D , 2002 .

[16]  Jacky Swan,et al.  Knowledge Management - The Next Fad to Forget People? , 1999, ECIS.

[17]  Tony Gorschek,et al.  Goal-Oriented Requirements Communication in New Product Development , 2008, 2008 Second International Workshop on Software Product Management.

[18]  Ivan Aaen,et al.  Software Process Improvement: Blueprints versus Recipes , 2003, IEEE Softw..

[19]  James D. Herbsleb,et al.  Software quality and the Capability Maturity Model , 1997, CACM.

[20]  Tony Gorschek,et al.  Technology transfer decision support in requirements engineering research: a systematic review of REj , 2009, Requirements Engineering.

[21]  Patrick A. V. Hall,et al.  "Talk to Paula and Peter - They Are Experienced" - The Experience Engine in a Nutshell , 1999, SEKE.

[22]  Frank Maurer,et al.  PROCESS-ORIENTED KNOWLEDGE MANAGEMENT FOR LEARNING SOFTWARE ORGANIZATIONS , 1999 .

[23]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[24]  Dennis R. Goldenson,et al.  A systematic survey of CMM experience and results , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[25]  Torgeir Dingsøyr,et al.  Postmortem reviews: purpose and approaches in software engineering , 2005, Inf. Softw. Technol..

[26]  Tony Gorschek,et al.  A practitioner's guide to light weight software process assessment and improvement planning , 2008, J. Syst. Softw..

[27]  Robert L. Glass Extreme programming: the good, the bad, and the bottom line , 2001, IEEE Software.

[28]  June M. Verner,et al.  In-house software development: what project management practices lead to success? , 2005, IEEE Software.

[29]  Kurt Schneider What to Expect from Software Experience Exploitation , 2002, J. Univers. Comput. Sci..

[30]  Manuel Pérez Cota,et al.  Experiences in the Application of Software Process Improvement in SMES , 2004, Software Quality Journal.

[31]  Jean-Pierre Kuilboer,et al.  Software process and product improvement: an empirical assessment , 2000, Inf. Softw. Technol..

[32]  Tony Gorschek,et al.  Packaging software process improvement issues: a method and a case study , 2004, Softw. Pract. Exp..

[33]  Tore Dybå Improvisation in Small Software Organizations , 2000, IEEE Software.

[34]  Austen Rainer,et al.  A quantitative and qualitative analysis of factors affecting software processes , 2003, J. Syst. Softw..

[35]  Wasif Afzal,et al.  Incorporating Metrics in an Organizational Test Strategy , 2008, 2008 IEEE International Conference on Software Testing Verification and Validation Workshop.

[36]  Tony Gorschek,et al.  Requirements Abstraction Model , 2005, Requirements Engineering.

[37]  Assessment Method Integrated Team,et al.  Standard CMMI Appraisal Method for Process Improvement (SCAMPI), Version 1.1: Method Definition Document , 2001 .

[38]  Torgeir Dingsøyr An Evaluation of Research on Experience Factory , 2001 .

[39]  Stuart E. Madnick,et al.  Software Project Dynamics: An Integrated Approach , 1991 .

[40]  M. Lindvall,et al.  Knowledge management in software engineering , 2002, IEEE Software.

[41]  Robert L. Glass Searching for the holy grail of software engineering , 2002, CACM.

[42]  Torgeir Dingsøyr,et al.  Organizational Learning Through Project Postmortem Reviews - An Explorative Case Study , 2007, EuroSPI.

[43]  Victor R. Basili,et al.  Software process evolution at the SEL , 1994, IEEE Software.

[44]  R. McDermott Why Information Technology Inspired but Cannot Deliver Knowledge Management , 1999 .

[45]  Alan M. Davis,et al.  Good requirements practices are neither necessary nor sufficient , 2005, Requirements Engineering.

[46]  Marvin V. Zelkowitz,et al.  Lessons learned from 25 years of process improvement: the rise and fall of the NASA software engineering laboratory , 2002, Proceedings of the 24th International Conference on Software Engineering. ICSE 2002.

[47]  Robert L. Glass,et al.  Project retrospectives, and why they never happen , 2002, IEEE Software.

[48]  Tony Gorschek,et al.  Requirements Engineering Supporting Technical Product Management , 2006 .

[49]  Donald J Reifer The CMMI: it's formidable , 2000, J. Syst. Softw..

[50]  Sami Zahran Software process improvement - practical guidelines for business success , 1998 .

[51]  Torgeir Dingsøyr,et al.  Postmortem: Never Leave a Project without It , 2002, IEEE Softw..

[52]  John J. Marciniak,et al.  Encyclopedia of Software Engineering , 1994, Encyclopedia of Software Engineering.

[53]  HerbslebJames,et al.  Software quality and the Capability Maturity Model , 1997 .

[54]  Tony Gorschek,et al.  Handshaking with Implementation Proposals: Negotiating Requirements Understanding , 2010, IEEE Software.

[55]  Tony Gorschek,et al.  A Model for Technology Transfer in Practice , 2006, IEEE Software.

[56]  Tony Gorschek,et al.  Identification of Improvement Issues Using a Lightweight Triangulation Approach , 2003 .

[57]  Victor R. Basili,et al.  Quantitative Evaluation of Software Methodology , 1985 .