Software project initiation and planning - an empirical study

This study describes a study of 14 software companies, on how they initiate and pre-plan software projects. The aim was to obtain an indication of the range of planning activities carried out. The study, using a convenience sample, was carried out using structured interviews, with questions about early software project planning activities. The study offers evidence that an iterative and incremental development process presents extra difficulties in the case of fixed-contract projects. The authors also found evidence that feasibility studies were common, but generally informal in nature. Documentation of the planning process, especially for project scoping, was variable. For incremental and iterative development projects, an upfront decision on software architecture was shown to be preferred over allowing the architecture to just ‘emerge’. There is also evidence that risk management is recognised but often performed incompletely. Finally appropriate future research arising from the study is described.

[1]  Peng Xu,et al.  Software Process Tailoring: An Empirical Investigation , 2007, J. Manag. Inf. Syst..

[2]  MyersWare,et al.  How Solved Is the Cost Estimation Problem , 1997 .

[3]  Barry Boehm,et al.  Software economics: a roadmap , 2000, ICSE '00.

[4]  Des Greer,et al.  Software release planning: an evolutionary and iterative approach , 2004, Inf. Softw. Technol..

[5]  Mike Cohn,et al.  Agile Estimating and Planning , 2005 .

[6]  Carolyn B. Seaman,et al.  Qualitative Methods in Empirical Studies of Software Engineering , 1999, IEEE Trans. Software Eng..

[7]  Barry W. Boehm.  Value-based software engineering: reinventing , 2003, SOEN.

[8]  Márcio de Oliveira Barros,et al.  Evaluating software project portfolio risks , 2007, J. Syst. Softw..

[9]  Robert M. Hayes,et al.  Systems analysis and design , 1970, ACM '70.

[10]  Barry W. Boehm,et al.  Software Risk Management , 1989, ESEC.

[11]  Reidar Conradi,et al.  An empirical study of variations in COTS-based software development processes in Norwegian IT industry , 2004 .

[12]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[13]  Steve McConnell,et al.  Feasibility Studies , 1998, IEEE Softw..

[14]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[15]  Richard Turner,et al.  CMMI Distilled: A Practical Introduction to Integrated Process Improvement , 2001 .

[16]  Neil A. M. Maiden,et al.  Where Do Requirements Come From? , 2001, IEEE Softw..

[17]  Norman Mooradian,et al.  Tacit knowledge: philosophic roots and role in KM , 2005, J. Knowl. Manag..

[18]  Craig Larman,et al.  Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition) , 1997 .

[19]  Magne Jørgensen,et al.  A Systematic Review of Software Development Cost Estimation Studies , 2007, IEEE Transactions on Software Engineering.

[20]  Mary Poppendieck,et al.  Agile Contracts , 2005, XP.

[21]  Des Greer,et al.  Preparing small software companies for tailored agile method adoption: Minimally intrusive risk assessment , 2008 .

[22]  Claes Wohlin,et al.  A product management challenge: Creating software product value through requirements selection , 2008, J. Syst. Archit..

[23]  Marco Torchiano,et al.  Development with Off-the-Shelf Components: 10 Facts , 2009, IEEE Software.

[24]  Linda M. Northrop,et al.  CMMI Distilled : A Practical Introduction to Integrated Process Improvement , 2022 .

[25]  Kjetil Moløkken-Østvold,et al.  The Relationship between Customer Collaboration and Software Project Overruns , 2007, Agile 2007 (AGILE 2007).

[26]  Shari Lawrence Pfleeger,et al.  Principles of survey research: part 1: turning lemons into lemonade , 2001, SOEN.

[27]  Des Greer,et al.  Preparing small software companies for tailored agile method adoption: Minimally intrusive risk assessment , 2008, Softw. Process. Improv. Pract..

[28]  Eugene Miya,et al.  On "Software engineering" , 1985, SOEN.

[29]  Claes Wohlin,et al.  An Investigation of a Method for Identifying a Software Architecture Candidate with Respect to Quality Attributes , 2005, Empirical Software Engineering.

[30]  Björn Regnell,et al.  Case Studies in Process Improvement through Retrospective Analysis of Release Planning Decisions , 2006, Int. J. Softw. Eng. Knowl. Eng..

[31]  Standard Glossary of Software Engineering Terminology , 1990 .

[32]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[33]  Reidar Conradi,et al.  An empirical study of variations in COTS-based software development processes in the Norwegian IT industry , 2004, 10th International Symposium on Software Metrics, 2004. Proceedings..

[34]  Claes Wohlin,et al.  A project effort estimation study , 1998, Inf. Softw. Technol..

[35]  Ware Myers,et al.  Manager: How Solved is the Cost-Estimation Problem? , 1997, IEEE Softw..

[36]  Barry Boehm,et al.  Balancing Agility and Dis-cipline: A Guide for the Perplexed , 2003 .

[37]  J. Barrie Thompson,et al.  Software engineering 2004: ACM/IEEE-CS guidelines for undergraduate programs in software engineering , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[38]  Nazim H. Madhavji,et al.  Architecting-problems rooted in requirements , 2008, Inf. Softw. Technol..

[39]  Brian Fitzgerald,et al.  Customising agile methods to software practices at Intel Shannon , 2006, Eur. J. Inf. Syst..

[40]  Ghassan Beydoun,et al.  A field study of the requirements engineering practice in Australian software industry , 2007, Requirements Engineering.

[41]  Martyn A. Ould,et al.  Strategies for software engineering - the management of risk and quality , 1990, Wiley series in software engineering practice.

[42]  Vinod Kumar,et al.  The Organizational Changes Required and the Challenges Involved in Adopting Agile Methodologies in Traditional Software Development Organizations , 2007, 2006 1st International Conference on Digital Information Management.

[43]  Geir Kjetil Hanssen,et al.  Tailoring and Introduction of the Rational Unified Process , 2007, EuroSPI.

[44]  Victor R. Basili,et al.  Tailoring the software process to project goals and environments , 1987, ICSE '87.

[45]  Sergey M. Avdoshin,et al.  Software risk management , 2011, 2011 7th Central and Eastern European Software Engineering Conference (CEE-SECR).

[46]  Magne Jørgensen,et al.  A Systematic Review of Software Development Cost Estimation Studies , 2007 .

[47]  Stefan Biffl,et al.  Software process improvement in Europe: potential of the new V-modell XT and research issues , 2006, Softw. Process. Improv. Pract..