Provides doctypes to collborate with your team. Run iterations and record discoveries that may be of interest at the end of the iteration or for even later reference. Quick notes are more easily added as records to the team's space than to the official documentation tree. Defer the talk to the documentation architect to the end of the iteration (if the discovery is still of interest).
English and German by Default
All doctype add-ons are available in English and German language (except for the V-Modell XT add-on for which only supports German).
For more information on this topic please refer to Localization.
At the heart of this set is the Iteration Doctype. We suggest that each agile team creates a page for each iteration to log all information that looks interesting. The team may then decide at the end of the iteration, which information goes to the global documentation, which should be archived or which permanently discarded.
The iteration page is therefore a kind of diary, allowing to add information collaboratively. But there is no burden on maintaining the information on this page and its subpages. After the iteration is completed, all information not propagated to the documentation wiki simply get archived.
To get started create a new space for your agile team:
The Doctypes for Agile Planning requires the projectdoc Toolbox to be installed. The projectdoc Toolbox has a commercial license.
Please install the following add-ons on your Atlassian Confluence server:
List of Doctypes for Agile Teams
The following doctypes help agile teams to collaborate in their iterations.
|#||Name||Short Description||Documentation Type||Categories|
Announcements are a way to communicate an important piece of information with your team.
Improvement proposals help to start the conversation within the team for process improvements.
Document an Iteration that may be linked from JIRA. Allows the team to set the goal and add notes relevant to a particular iteration.
Product Backlogs are means to collect user stories.
Record the discussion of the team about their last iteration.
Plan and run your review meeting.
A single act to show on the review. Use this only if you have a lot to show or you want to reference the review results later. Often a simple numerated list is sufficient.
User Stories document a requirement of a stakeholder with a specific business goal. It also provides an acceptance test. It is a representation of a unit of work.
We do not expect to meet all your requirements for your documentation. So please feel free to use this set of blueprints as a template to create your own!