Child pages
  • Why should I use the Doctypes for Agile Teams?

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
titleDescription
I am unsure of what the doctypes provided by the Agile Planning Add-on are used for. How are these templates useful?
Section
titleQuestion

I am unsure of what the doctypes provided by the Agile Planning Add-on are used for. How are these templates useful?

Section
titleAnswer

Documents have different properties. One property is its requirement to be updated. While the handbook for an artifact probably needs to be updated on each new release, the notes in a developer diary does not call for maintenance. It is often important to separate those versioned documents from the inversioned records.

The Doctypes for Agile Planning help you to create space for records and the collaborative work of a team during an iteration. The add-on provides a space blueprint to create spaces to work in collaboration. Create Iterations to store all information that is relevant for a particular sprint. During and especially at the end of the sprint decide, which information should be moved to a more prominent space (especially to a place where it further needs to be maintained) and which information could be stored in the iteration without requiring any update. The information of the iteration may still be available, but due to its diary style of usage, demands not to be up-to-date.

There are also templates to prepare your Review or Retrospective. You'll also find a template for User Stories (in case you want to add more information with the tools of a wiki instead of your issue management system) and Improvements (to keep track of you ongoing improvement process).

These templates are just suggests to get you started. You probably want to adjust them to meet your specific documentation requirements.

Section
titleAnswer
The doctypes provided by the Software Development Doctypes are used to document artifacts of an agile software development project. Agile implies that you do not want to follow a process to create documentation, but that you and your stakeholders define the type of documents that are useful for the project and the users of the products you create.

We do not assume that this set of templates defines completely what you need. This would probably defy the notion of agile as we have defined it above. Instead look at these doctypes as a starting point for the definition of your templates. Select those that generate value for you and deactivate those that do not.

Tour for Template Authors may help you to get started with defining your own templates

.

Section
titleSubordinate FAQs
Display Table
doctypefaq
render-no-hits-as-blanktrue
selectName, Short Description
sort-bySort Key, Name
restrict-to-immediate-childrentrue

...