Documentation strategies on agile software development projects

Agile software development methods and their proponents suggest 'just enough' documentation on agile projects. However, for practitioners of these methods it remains unclear how much is 'just enough' documentation. Based on a grounded theory study of 58 agile practitioners from 23 different software organisations in New Zealand and India, we found several documentation strategies being used by agile teams to overcome various challenges they faced. These documentation strategies include documenting electronic back-ups of physical paper artefacts that are prone to damage and loss; documenting change decisions by customers to trace changes and avoid disagreements; documenting business terminology for more effective requirements elicitation; documenting the traditional way when collaborating with non-agile teams; and documenting positive customer feedback to demonstrate advantage of agile adoptions. These documentation strategies collectively help define 'just enough' documentation by describing the different forms and amounts of documentation agile teams engage in.

[1]  Raul Sidnei Wazlawick,et al.  The influence of organizational culture on the adoption of extreme programming , 2008, J. Syst. Softw..

[2]  James Noble,et al.  How much is just enough?: some documentation patterns on Agile projects , 2010, EuroPLoP.

[3]  George Mangalaraj,et al.  Challenges of migrating to agile methodologies , 2005, CACM.

[4]  Mira Kajko-Mattsson,et al.  Problems in agile trenches , 2008, ESEM '08.

[5]  James Noble,et al.  Supporting Self-organizing Agile Teams - What's Senior Management Got to Do with It? , 2011, XP.

[6]  Helen Sharp,et al.  An Ethnographic Study of XP Practice , 2004, Empirical Software Engineering.

[7]  Per Runeson,et al.  Combining agile methods with stage-gate project management , 2005, IEEE Software.

[8]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[9]  Philippe Kruchten,et al.  Agility in context , 2010, OOPSLA.

[10]  Rashina Hoda,et al.  Self-Organizing Agile Teams: A Grounded Theory , 2011 .

[11]  James Noble,et al.  Organizing self-organizing teams , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[12]  B. Glaser.  Theoretical Sensitivity: Advances in the Methodology of Grounded Theory , 1978 .

[13]  Orit Hazzan,et al.  The Agile Manifesto , 2014 .

[14]  Tore Dybå,et al.  Empirical studies of agile software development: A systematic review , 2008, Inf. Softw. Technol..

[15]  Scott W. Ambler.  Agile Software Development , 2010, Encyclopedia of Software Engineering.

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

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

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

[19]  Barry W. Boehm,et al.  Get Ready for Agile Methods, with Care , 2002, Computer.

[20]  A. Strauss,et al.  The Discovery of Grounded Theory , 1967 .

[21]  Helen Sharp,et al.  The role of physical artefacts in agile software development: Two complementary perspectives , 2009, Interact. Comput..

[22]  James Noble,et al.  Developing a grounded theory to explain the practices of self-organizing Agile teams , 2012, Empirical Software Engineering.

[23]  Andreas Rüping,et al.  Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects , 2003 .

[24]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[25]  James Noble,et al.  What Language Does Agile Speak? , 2010, XP.