Product-Focused Software Process Improvement

The future software engineers looking for positions in the software industry tend to lean towards software development/coding rather than software testing. Our study investigates what factors cause software testing professionals working both in agile and traditional methodologies, to choose and remain in this career path. Using a qualitative survey among software development companies we retrieve information about the difference between the traditional and agile testers. In addition we identify information about the motivating and de-motivating factors in current testing practices. The results could help the companies in their recruiting processes, in the transition from traditional to agile within a company and in motivating their testers, which will lead to better job satisfaction and productivity.

[1]  Zadia Codabux,et al.  Managing technical debt: An industrial case study , 2013, 2013 4th International Workshop on Managing Technical Debt (MTD).

[2]  Fabio Q. B. da Silva,et al.  Managing technical debt in practice: An industrial report , 2012, Proceedings of the 2012 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement.

[3]  Carolyn B. Seaman,et al.  A portfolio approach to technical debt management , 2011, MTD '11.

[4]  Samir Chatterjee,et al.  A Design Science Research Methodology for Information Systems Research , 2008 .

[5]  Forrest Shull,et al.  Investigating the impact of design debt on software quality , 2011, MTD '11.

[6]  Ward Cunningham,et al.  The WyCash portfolio management system , 1992, OOPSLA '92.

[7]  Yuanfang Cai,et al.  Comparing four approaches for technical debt identification , 2014, Software Quality Journal.

[8]  Erik Stolterman,et al.  The anatomy of prototypes: Prototypes as filters, prototypes as manifestations of design ideas , 2008, TCHI.

[9]  N. Hoffart.  Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory , 2000 .

[10]  Christine Nadel,et al.  Case Study Research Design And Methods , 2016 .

[11]  Vladimir Tosic,et al.  Guidelines for industrially-based multiple case studies in software engineering , 2009, 2009 Third International Conference on Research Challenges in Information Science.

[12]  Robert L. Nord,et al.  Managing technical debt in software-reliant systems , 2010, FoSER '10.

[13]  P. Kidwell,et al.  The mythical man-month: Essays on software engineering , 1996, IEEE Annals of the History of Computing.

[14]  Tomi Männistö,et al.  Bridging the Gap Between Usability and Requirements Engineering , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[15]  Anirban Basu,et al.  A Systematic Method to Evaluate the Software Engineering Practices for Minimizing Technical Debt , 2015 .

[16]  Foutse Khomh,et al.  Tracking Design Smells: Lessons from a Study of God Classes , 2009, 2009 16th Working Conference on Reverse Engineering.

[17]  Robert L. Nord,et al.  Technical Debt: From Metaphor to Theory and Practice , 2012, IEEE Software.

[18]  Richard Baskerville,et al.  Agile requirements engineering practices and challenges: an empirical study , 2007, Inf. Syst. J..

[19]  Rami Bahsoon,et al.  Systematic Elaboration of Compliance Requirements Using Compliance Debt and Portfolio Theory , 2014, REFSQ.

[20]  André L. M. Santos,et al.  Tracking technical debt — An exploratory case study , 2011, 2011 27th IEEE International Conference on Software Maintenance (ICSM).

[21]  Peter J. Coughlan,et al.  Prototypes as (Design) Tools for Behavioral and Organizational Change , 2007 .

[22]  Yuanfang Cai,et al.  Using technical debt data in decision making: Potential decision approaches , 2012, 2012 Third International Workshop on Managing Technical Debt (MTD).

[23]  Richard T. Vidgen,et al.  An exploration of technical debt , 2013, J. Syst. Softw..

[24]  Forrest Shull,et al.  Prioritizing design debt investment opportunities , 2011, MTD '11.

[25]  Carolyn B. Seaman,et al.  A Balancing Act: What Software Practitioners Have to Say about Technical Debt , 2012, IEEE Softw..

[26]  Stefania Passera,et al.  When, how, why prototyping? A practical framework for service development , 2012 .

[27]  Ken Power.  Understanding the impact of technical debt on the capacity and velocity of teams and organizations: Viewing team and organization capacity as a portfolio of real options , 2013, 2013 4th International Workshop on Managing Technical Debt (MTD).

[28]  Peri L. Tarr,et al.  An enterprise perspective on technical debt , 2011, MTD '11.

[29]  Anirban Basu,et al.  Minimizing technical debt: developer's viewpoint , 2012, ICSE 2012.

[30]  Forrest Shull,et al.  A case study on effectively identifying technical debt , 2013, EASE '13.

[31]  Teade Punter,et al.  Views on Evolvability of Embedded Systems , 2010 .

[32]  Frank Buschmann,et al.  To Pay or Not to Pay Technical Debt , 2011, IEEE Software.

[33]  Robert J. Eisenberg.  A threshold based approach to technical debt , 2012, SOEN.