FIT2043 Lecture 23: FIT2043 Lecture 23 Agile Documentation Techniques Notes
13 Jun 2018
School
Department
Course
Professor
L23 - Agile Documentation Techniques
Spikes
● A task aimed at answering a question or gathering information, rather than at
producing shippable product
● Idea:
○ Write the smallest amount of code you need in order to figure out what you
need to know
○ Spikes are throwaway code. They are not integrated into the project
● Goals:
○ Be clears. What’s being investigated? What information is sought?
○ Timeboxed
● Still documented so that other team members can understand what has been done
and what information has been found and can be looked up if needed
● Why do it?
○ When a team gets stuck and is not sure how to proceed, usually the solution
is to get more information so that members are more knowledgeable
Retrospectives
● Since agile methodologies are iterative, there are plenty of opportunities to improve
the process, these are done by retrospectives.
● At the end of each sprint, team gets together to discuss how the sprint went
○ What went well? Should we do it again?
○ What went badly? Should we do it again?
○ What needs changing?
● Documenting:
○ Someone is delegated to do a proper write up of what changes has been
suggested
○ Audience: the dev team, maybe Product Owner if they are very involved with
the development process
Links:
http://www.xmlvalidation.com/index.php?id=1&L=0
http://www.utilities-online.info/xsltransformation/
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
A task aimed at answering a question or gathering information, rather than at producing shippable product. Write the smallest amount of code you need in order to figure out what you need to know. Still documented so that other team members can understand what has been done and what information has been found and can be looked up if needed. When a team gets stuck and is not sure how to proceed, usually the solution is to get more information so that members are more knowledgeable. Since agile methodologies are iterative, there are plenty of opportunities to improve the process, these are done by retrospectives. At the end of each sprint, team gets together to discuss how the sprint went. Someone is delegated to do a proper write up of what changes has been suggested. Audience: the dev team, maybe product owner if they are very involved with the development process.
