Describes an information need and use this description as a basis to create and maintain a document.
Agile documentation is about to provide information that is really needed. Agile documentation needs to be valuable, essential, and available just-in-time.
Therefore a stakeholder is required to define what is required, to what extend, and at which time.
A charter document starts a documentation session by defining what is required.
The document type charter provides the following properties:
Please note that only information about specific properties is provided here. Common document property used by all document types are documented by Document Properties.
The Charter Type allows to organize charters by type.
Define the timebox within to run the session.
Documented Information Type
Define the documented information type of the new document as either
- A document is required to be kept up-to-date. Therefore there is an ongoing maintenance cost until the document is deprecated or removed.
- The record is just an information that is up-to-date at the instance of its creation. It may serve as a source of information that was valid in the past. It is never updated and therefore does not require resources for maintenance. It may be edited if it contains errors or it may be updated if it is deemed useful by the team or stakeholders. But it should never be considered to be accurate without further inquiry of the stakeholders and experts.
Specify a list of stakeholders that are interested in the information and therefore sponsor it.
List the names of stakeholders who may provide additional information on the area being examined.
Add a reference to the root of the documentation created based on this charter.
This allows interested stakeholders to navigate to the created documents quickly.
Document the purpose of this charter. This may contain the whole charter information in a couple of sentences.
Write a short summary about the result intended for team members and other stakeholders
State where the exploration is taking place.
List the tools to employ to run the exploration.
List the information the sponsors are interested in. May state a problem to be solved.
Teams may want to break a larger charter into smaller charters to have several, more focussed sessions. In this case add the additional charters as child pages to this document. Keep in mind that the child relationship indicated that if - for some reason - the parent charter is removed, all children should be removed, too. If this is not the case, better add the charters to the homepage.