Use case driven object modeling with UML: a practical approach
Use case driven object modeling with UML: a practical approach
Agile Software Development with Scrum
Agile Software Development with Scrum
Questioning Extreme Programming
Questioning Extreme Programming
The relevance of software documentation, tools and technologies: a survey
Proceedings of the 2002 ACM symposium on Document engineering
Globalization by Chunking: A Quantitative Approach
IEEE Software
New directions on agile methods: a comparative analysis
Proceedings of the 25th International Conference on Software Engineering
Documentation and agile methods: striking a balance
ACM SIGCSE Bulletin
Managing Uncertainty in Requirements: A Survey in Documentation-Driven and Agile Companies
METRICS '05 Proceedings of the 11th IEEE International Software Metrics Symposium
WikiWiki weaving heterogeneous software artifacts
Proceedings of the 2005 international symposium on Wikis
Theoretical reflections on agile development methodologies
Communications of the ACM - Emergency response information systems: emerging trends and technologies
Empirical studies of agile software development: A systematic review
Information and Software Technology
The role of physical artefacts in agile software development: Two complementary perspectives
Interacting with Computers
Supporting agile software development through active documentation
Requirements Engineering
Articulating everyday actions: an activity theoretical approach to scrum
Proceedings of the 30th ACM international conference on Design of communication
Hi-index | 0.04 |
When compared to traditional development methods, agile development practices are associated with more direct communication and less documentation. However, few empirical studies exist that investigate the role of documentation in agile development teams. We thus employed a questionnaire to measure the perceptions of a group of agile practitioners with regard to the documentation in their projects. We obtained responses from 79 agile software development professionals and 8 teams in 13 different countries. Our findings include that over half of developers in our data set find documentation important or even very important but that too little documentation is available in their projects. Agile practitioners do not seem to agree with the agile principle that "The most efficient and effective method of conveying information to and within a development team is face-to-face conversation." We were able to validate this result for a set of dissimilar agile teams in various domains.