How much is just enough?: some documentation patterns on Agile projects

Authors:
Rashina Hoda;James Noble;Stuart Marshall
Affiliations:
Victoria University of Wellington;Victoria University of Wellington;Victoria University of Wellington
Venue:
Proceedings of the 15th European Conference on Pattern Languages of Programs
Year:
2010

Citing 7
Cited 1

A rational design process: How and why to fake it

IEEE Transactions on Software Engineering
Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects

Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects
Extreme Programming Refactored: The Case Against XP

Extreme Programming Refactored: The Case Against XP
Organizational Patterns of Agile Software Development

Organizational Patterns of Agile Software Development
The XP Customer Team: A Grounded Theory

AGILE '09 Proceedings of the 2009 Agile Conference
Organizing self-organizing teams

Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Balancing acts: walking the Agile tightrope

Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering

Agility in context

Proceedings of the ACM international conference on Object oriented programming systems languages and applications

Quantified Score

Hi-index	0.00

Visualization

Abstract

Agile methods advocate "just enough" documentation on Agile projects. Unfortunately, there are no clear guidelines on what is "just enough" documentation. We describe a set of patterns to help Agile software development teams define "just enough" in their own contexts. Teams can also employ these documentation patterns as strategies to overcome common challenges of adopting Agile methods.