Documentation targeting the team's process.

Doctypes of this Type

Name Short Description

Type-specific category for access information.

Group your alternatives by a self-defined type.

Type-specific category for applications.

Group architecture alternatives by their type.
Group architecture aspects by their type.
Architecture decisions are group by their types. A commonly used decision type is 'Architecture'.
Document requirements you impose on artifacts. Artifacts are created by processes defined and used by the team. This includes assemblies created by the build process, source code artifacts or reports.
Associates two documents.
Categorize associations by a type.
Assumptions are grouped by their type.
Group blackboxes by their type.
Categories allow to set document instance of different doctypes in a hierarchy.
Categorize categories by a type.

Add an severity to classify changes.

Add a status to categorize changes.

Add a theme to group changes.

Type-specific category for changes.

Categorize charters by a type.
Checklists allow to run manual tasks in a defined manner. It guides the user of the checklist through a process and helping to not forget a step.
Categorize checklists by type.

Signals the status of an IT system, application, or a configuration item.

Type-specific category for configuration items.

Add cycles to group cycle phases.

Cycle phases define phases that are bound to a cycle, such as lifecycles or iterations.

Type-specific category for datasets.

Group your decisions by a self-defined type.

Type-specific category for deployment records.

Type-specific category for deployments.

Excerpts are abstracts of information found in a resource, such as a book. If you want to go into more detail for a given resource, there may be multiple excerpts as subpages of the resource document.
Categorize excerpts by a type.
Defines the context through which readers acquire skills. The level sets the expectation on the author's techniques to teach.
Categorize experience levels by a type.
FAQs help to record an answer to a frequently asked question concerning the project, the product, the system or the process.
Categorize FAQs by a type.
Generic Documents provide information where no other doctype matches.
Categorize generic documents by a type.
Glossary items are part of the domain glossary for the project. Glossaries support the team to use terms of the domain consistently in conversations and documentation.
Categorize glossary items by a type.
Group interfaces by their type.

Type-specific category for IT activities.

Type-specific category for IT assets.

Type-specific category for IT functions.

Type-specific category for IT procedures.

Type-specific category for IT processes.

Classifiers to categorize services.

Type-specific classification for IT services.

Signals the status of an IT Service.

Type-specific category for IT services.

Systems are categorized by their type. These types may be quite concrete since systems by nature reference a hard- or software system usually by their IP address or DNS name. Therefore a system type may be 'Artifact Repository' or 'Virtual Server. And types may build hierarchies.

Add lifecycles to group lifecycle phases.

Lifecycle phases define phases that are bound to a lifecycle.

Type-specific category for locations.

Resources are identified by their media type. This may be the MIME type, but also a human readable string, that identifies the syntactic format.
Categorize media types by their type.
Group your minutes by a self-defined type.

Type-specific category for mission statements.

A documentation module is a fragment which is usually transcluded by other documents. The lifetime of a module document is independent of the lifetimes of the documents that reference it.
Categorization of document modules for single sourcing.
Open issues are grouped by the severity of their impact on the project.
Open issues are grouped by the status.
Group your open issues by a self-defined type.
Opportunities are grouped by their type.
Categorize organizations by a type.
Patterns provide solutions for problems in a given context. Patterns are usefull in multiple areas such as design, architecture, documentation, or process.
Patterns are divided into different domains to group patterns.
Categorize patterns by type.
Categorize persons by a type.
Problems are grouped by their type.

Type-specific category for impacts.

Type-specific category for outcomes.

Profiles provide views on documents via delegation.
Categorize profiles by a type.
Project Rules are defined by the team to enhance the collaboration and to define project standards.
Categorize project rules by type.
Qualities describe desired aspects of the product.
Group quality targets by their type.
Quotes relevant for the project. Allows to store the content and metadata to the quote.
Categorize quotes by a type.
Organizes glossary items.
Categorize relations by a type.
Group your release notes by a self-defined type.
Type-specific category for releases.
Group your reports by a self-defined type.
Categorization of requirements for a product.
Resources are books, webpages, videocasts relevant for the project. Add important information to your project about resources that lie outside the control of your team.
Resources are identified by their type. This is not the MIME type, but human readable string, that identifies the semantic, rather than the syntactic format.
Risk actions are grouped by their type.
Risks are grouped by the phase of their impact on the project.
Risks are grouped by the probability of having impact on the project.
Risks are grouped by the severity of their impact on the project.
Risk tagets are grouped by their type.
Risks are grouped by their type.
Defines a role with its responsibilities, tasks and requirements. Roles are incorporated by stakeholders who take interest in the project. The are also used to define the audience for documents.
Categorize roles by a type.
Sections of a document are typically part of a document. But the size of sections may vary. To support a team to write collaboratively on the documentation, a larger document may be subdivided into external section documents.
Categorize sections by a type.

Type-specific category for service announcements.

Type-specific category for service level agreements.

Type-specific category for service level requirements.

Type-specific category for service levels.

Compile other documents, yet space indices are themselves projectdoc documents. So they can be tagged and grouped.
Categorize space indexes by a type.
Categorize stakeholders by a type.
Describes a single step of an activity. A step is a generic document that is associated with a document that describes a process. It may be a test log or a howto.
Categorize steps by a type.

Type-specific category for strategies.

Subject documents allow to set document instance of different doctypes in a common context.
Categorize subjects by a type.

Type-specific category for SWOTs.

Document the semantics of a tag. May also be used to document Confluence labels.
Categorize tags by a type.
Categorize team processes by type.
Technical Debts are grouped by the area they address.
Categorize tools by type.
A description of a given topic. A topic may describing or explaining a concept, a task to accomplish or a reference. There are a couple of topic types that set the expectations for the reader. Instances of the topic doctype usually have independent lifetimes from any referencing documents.
A topic type is a semantic type of the topic. It helps to set the expectations of potential readers.
Guided tours through existing information. This allows to aggregate topics for a given question or audience, thus providing a view on a topic.

Type-specific category for triggers.

Categorize versions by a type.
Groups the views at a system.

Type-specific category for vision statements.

Group whiteboxes by their type.
Type-specific category for work instructions.