Scrum Maturity Model: Validation for IT organizations’ roadmap to develop software centered on the client role

Within the agile development methodologies context, the topic of client relationship management is strongly focused, mainly due to the importance of collaboration between the development team and its clients. Most clients avoid or are unable to develop a close cooperation with vendor organizations, since it requires a motivation and close participation among key stakeholders in the development processes within and correct usage of the adopted software development methodology. Hence, software development projects fail and become unsuccessful because of this lack of communication. In order to increase the rate of successful projects, this paper will present the journey of the validation process for this roadmap to lead and aid software vendor organizations improve their development processes, concentrating mainly on the client’s role throughout the process. This concept is called Scrum Maturity Model; therefore, our main goal is to validate this concept with organizations that use Scrum agile methodology as their main development process, which turns out to be an viable approach to reduce the rate failed development projects. Keywords-development methodologies; agile methodologies; scrum development methodology; maturity model; action research

[1]  Juliet Sutherland,et al.  SCRUM: An extension pattern language for hyper productive software development , 2000 .

[2]  Tsun Chow,et al.  A survey study of critical success factors in agile software projects , 2008, J. Syst. Softw..

[3]  J. Herbsleb,et al.  Global software development , 2001 .

[4]  Lucas Layman,et al.  Motivations and measurements in an agile case study , 2006, J. Syst. Archit..

[5]  Michael Kircher,et al.  Distributed eXtreme Programming , 2001 .

[6]  Keith Braithwaite,et al.  XP Expanded: Distributed Extreme Programming , 2005, XP.

[7]  Richard Baskerville,et al.  Investigating Information Systems with Action Research , 1999, Commun. Assoc. Inf. Syst..

[8]  Cmmi Product Team CMMI for Development, Version 1.2 , 2010 .

[9]  Mary Beth Chrissis,et al.  CMMI: Guidelines for Process Integration and Product Improvement , 2003 .

[10]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

[11]  Alistair Cockburn,et al.  Crystal Clear: A Human-Powered Methodology for Small Teams , 2004 .

[12]  Robert C. Martin,et al.  Iterative and Incremental development , 1999 .

[13]  Jeff Sutherland,et al.  Distributed Scrum: Agile Project Management with Outsourced Development Teams , 2007, 2007 40th Annual Hawaii International Conference on System Sciences (HICSS'07).

[14]  Winifred Menezes To CMMI or Not to CMMI: Issues to Think About , 2002 .

[15]  Pär J. Ågerfalk,et al.  Agile Practices Reduce Distance in Global Software Development , 2006, Inf. Syst. Manag..

[16]  J.S. Reel,et al.  Critical Success Factors in Software Projects , 1999, IEEE Softw..

[17]  Capers Jones,et al.  Why software fails , 1996 .

[18]  Miguel Mira da Silva,et al.  Scrum Maturity Model , 2011 .

[19]  Ken Schwaber,et al.  Agile Software Development with SCRUM , 2001 .

[20]  Dinesh Batra,et al.  Modified agile practices for outsourced software projects , 2009, CACM.

[21]  Robert Benefield,et al.  Seven Dimensions of Agile Maturity in the Global Enterprise: A Case Study , 2010, 2010 43rd Hawaii International Conference on System Sciences.

[22]  R.N. Charette,et al.  Why software fails [software failure] , 2005, IEEE Spectrum.

[23]  A. Cockburn,et al.  Agile Software Development: The People Factor , 2001, Computer.

[24]  Victor R. Basili,et al.  Iterative and incremental developments. a brief history , 2003, Computer.

[25]  Robert E. Kraut,et al.  Coordination in software development , 1995, CACM.

[26]  Alistair Cockburn,et al.  Agile Software Development: The Business of Innovation , 2001, Computer.

[27]  David B. Anderson,et al.  CMMI ® or Agile: Why Not Embrace Both! , 2008 .