Skip to end of metadata
Go to start of metadata

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).

Take an alternative introduction to the Doctypes for Agile Planning

English and German by Default

 

All doctype add-ons are available in Englisch and German language.

For more information on this topic please refer to Localization.

Overview

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:

Prerequisites

The Doctypes for Agile Planning requires the projectdoc Toolbox to be installed. The projectdoc Toolbox has a commercial license.

The add-on also uses blueprints from the Core Doctypes for projectdoc (like Role or Stakeholder). This add-on is available on the Atlassian Marketplace for free.

Please install the following add-ons on your Atlassian Confluence server:

1. Install projectdoc Toolbox

List of Doctypes for Agile Teams

The following doctypes help agile teams to collaborate in their iterations.

# Name Short Description Documentation Type Categories
1
Announcements are a way to communicate an important piece of information with your team.
2
Improvement proposals help to start the conversation within the team for process improvements.
3
Document an Iteration that may be linked from JIRA. Allows the team to set the goal and add notes relevant to a particular iteration.
4
Product Backlogs are means to collect user stories.
5
Record the discussion of the team about their last iteration.
6
Plan and run your review meeting.
7
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.
8
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!

Resources

Doctypes
Doctypes define properties and sections for documents. They are essentially Confluence Blueprints that help to create pages in your wiki based on templates.
Doctypes Overview
List of all doctypes provided by add-ons. Provides an overview over doctype IDs and blueprint keys.
Project Management
Make all decisions, issues, and project relevant resources easily accessible for your team. This includes meeting minutes, stakeholder contact information, open issues, and identified risks with their mitigation strategy.
Macros
List of macros provided by the projectdoc Toolbox.
Doctypes for Project Management
Provides doctypes for documenting decisions, risks, open issues, and meeting minutes.
Doctypes for V-Modell®XT
Use products (templates) from the V-Modell®XT in your Confluence wiki as blueprints!
Doctypes for Risk Management
Provides doctypes for documenting and tracking risks.
projectdoc Developer Diaries
Provides doctypes to organize the developer's work by the employment of a diary. Take you personal planning and professional records to the next level!
Doctypes for Teamwork
Provides doctypes to define the checklists, processes, patterns, tools, and rules your team agrees upon. Writing them down makes them accessible for anyone - especially for new team members. Keep these documents short and to the point!