Child pages
  • Community of Practice

Versions Compared

Key

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

...

Section
titleCreating an Infrastucture

Some notes on how to create an infrastucture for a community of practice.

Steps


Section
titleCreate an Index Space

If you are new to Confluence and the projectdoc Toolbox, the first space you may want to create is the Index Space. This space is typically the root of a other spaces and provides some commonly used configuration (like categories and tags).

You may want to create a separate Address Book space, Library Space, and Glossary space. If not, store these resource in the index space.

projectdoc-box-note

All these spaces are commonly used by teams and are created only once. So you usually have one address book, one library, etc. per site.

If you need to keep things separate you can have all this information as part of your index space.



projectdoc-section
titleDefine the Subject

To define the subject you are investigating we recommend to use the Tag doctype. Use the tag homepage of your index space as the parent to this document.

Tip Box

There is a Subject doctype. But subjects are typically exclusive for a document, while tags are not. Categories are often unwieldy since they require to have entered the whole path.



Section
titleDocument the Community

Use the Organization doctype to add information about the community. The organization document is typically stored on its doctype homepage in the the Address Book space.

You may add Person documents to describe basic information (typically contact information) and add a Stakeholder document to add information that is relevant for a given person in the context of the community. The person document is typically stored on its doctype homepage in the the Address Book space, while the stakeholder document is part of the community space (may be an Teamwork Space teamwork space and the organization document should probably point to the space - and vice versa).

The Teamwork teamwork space will include the current rules and descriptions of currently used tools.


Section
titleAdd Workspaces - as needed

Create an Agile Planning space and have a team journal in the form of Iteration documents. The members of the community may run their own personal journal where they track events. You may use each or one of them, whatever suites your needs of communication more. Note that these spaces will contain records (which document events that need not to be updated. The Teamwork space created in the last step contains documents which require to be up-to date (for instance if a rule is changed, removed, or added, the space needs to be updated accordingly).

For spikes that require more room you may use additional workspaces for a subset of the community.

Tip Box
titleDo not get lost in empty spaces!

Create workspaces at the moment they are needed. Otherwise there is the tendency to have a large number of spaces with little content. Keep this content in the Agile Planning space as long as you are comfortable with that.



Section
titleAdd Topic Spaces - as needed

Put each information to its topic space. Topic spaces contain documents that need to reflect the current state of knowledge. A community may maintain only one topic space for their subject of interest.

Note Box

The teamwork space contains the rules and tools of the community.

The workspaces (including journals) log events with interesting and useful information discovered by the team members.

The topic space contains the current status of knowledge of the community on the subject.

In addition there may be specialized attachment spaces kept separate from these other spaces.

  • address book
  • library
  • glossary




...