Authors: Rashina Hoda; James Noble; Stuart Marshall
Addresses: School of Engineering and Computer Science, Victoria University of Wellington, P.O. Box 600, Wellington 6140, New Zealand. ' School of Engineering and Computer Science, Victoria University of Wellington, P.O. Box 600, Wellington 6140, New Zealand. ' School of Engineering and Computer Science, Victoria University of Wellington, P.O. Box 600, Wellington 6140, New Zealand
Abstract: 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.
Keywords: agile software development; documentation strategies; self-organising teams; software engineering; grounded theory; agile development; New Zealand; India; agility; agile teams; electronic back-up; change decisions; business terminology; requirements elicitation; positive customer feedback.
International Journal of Agile and Extreme Software Development, 2012 Vol.1 No.1, pp.23 - 37
Published online: 18 Jul 2012 *Full-text access for editors Access for subscribers Free access Comment on this article