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.
- Agile/Lean Documentation Strategies for Agile Software Development http://www.agilemodeling.eom/essays/agileDocumentation.htm (Feb 2010)Google Scholar
- Kent Beck. ---A Theory of Programming||. Dr. Dobb's Journal, Nov 2007Google Scholar
- Charles Connell. ---It's Not About Lines of Code|| http://www.developer.com/java/other/article.php/988641/Its-Not-About-Lines-of-Code.htmGoogle Scholar
- James O. Coplien, Neil B. Harrison. ---Organizational Patterns of Agile Software Development|| Pearson Prentice Hall, 2005 Google ScholarDigital Library
- Rashina Hoda, James Noble, Stuart Marshall. ---Organizing Self-Organizing Teams||, In the Proceedings of the International Conference on Software Engineering (ICSE), Cape Town, 2010. Google ScholarDigital Library
- Rashina Hoda, James Noble, Stuart Marshall. ---Balancing Acts: Walking the Agile Tightrope.|| Cooperative and Human Aspects of Software Engineering (CHASE) workshop at ICSE2010, South Africa, May 2010. Google ScholarDigital Library
- Rashina Hoda, James Noble, Stuart Marshall. ---Agile Undercover: When Customers Don't Collaborate.|| XP2010, Norway, June 2010.Google Scholar
- Rashina Hoda, James Noble, Stuart Marshall. ---What Language Does Agile Speak?|| XP2010, Norway, June 2010.Google Scholar
- Ron Jeffries. Essential XP: Documentation http://xprogramming.com/xpmag/expDocumentationInXP (Feb 2010)Google Scholar
- Jerry Weinberg. ---Psychology of Computer Programming||Google Scholar
- The Agile Manifesto http://agilemanifesto.org/Google Scholar
- Mary Lynn Manns and Linda Rising. ---Fearless Change: Patterns for Introducing New Ideas.|| Addison-Wesley, 2005.Google Scholar
- Angela Martin, James Noble, Robert Biddle. ---The XP Customer Roles: A Grounded Theory||. Agile2009, Chicago, August 2009. Google ScholarDigital Library
- Matt Stephens, Doug Rosenber. ---Extreme Programming Refactored: The Case Against XP||, Apress L. P, 2003 Google ScholarDigital Library
- D L Parnas, P C Clements. "A rational design process: How and why to fake it||, IEEE Transactions on Software Engineering, 1986 Google ScholarDigital Library
- Andreas Ruping. ---Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects||, John Wiley, 2003 Google ScholarDigital Library
Index Terms
- How much is just enough?: some documentation patterns on Agile projects
Recommendations
Necessary and neglected?: an empirical study of internal documentation in agile software development teams
SIGDOC '11: Proceedings of the 29th ACM international conference on Design of communicationWhen 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 ...
Understanding Self-Organizing Teams in Agile Software Development
ASWEC '08: Proceedings of the 19th Australian Conference on Software EngineeringTraditional software teams consist of independently focused self-managing professionals with high individual but low team autonomy. A challenge with introducing agile software development is that it requires a high level of both individual and team ...
Multi-level agile project management challenges
Self-organizing teams are closely involved in project management activities.High team involvement in project management leads to new challenges.We present the multiple levels of agile project management challenges.Relationships between challenges at ...
Comments