Tag Archives: Confluence

The Wiki Gardener: Tasks and Requirements

The idea of a wiki gardener is outstanding. There is hardly a company that is not delighted by this principle. But only a few companys actually transform this concept systematically and successfully. In doing so, it is generally no drama to recruit a gardener internally, and entrust him regularly with appropriate work. All you have to know is what a so called wiki gnome does, and why and who fits to the job profile.

Factors for the Success of Wikis 3: Overcoming Resistance from the Company Culture

From dozens of enterprise Wiki projects, we know that the successful introduction of a Wiki into a company typically depends on three factors: technology; organization; and culture. In the first of these three articles we focused on the requirements of technology. The second of these articles focused on organizational factors. This report will now focus on the implications of company culture and how these relate to the introduction of a Wiki.

Factors for the Success of Wikis 2: Organization is the Key

From dozens of enterprise Wiki projects, we know that the successful introduction of a Wiki into a company typically depends on three factors: technology; organization; and culture. In the first of these three articles we focused on the requirements of technology. This report will now focus on the organizational factors for a promising Wiki project.

Factors for the Success of Wikis 1: Technology is important, but not King

An enterprise Wiki is not only a new technology for many employees (at least within the company environment); it also requires a change in the normal communication- and collaboration patterns throughout the entire company. Through our experiences with dozens of company Wiki projects, we know that the successful introduction of a Wiki usually depends upon three factors: technology; organization; and culture. This article – the first of three articles on this topic – is dedicated to the challenges of technology.

Architecture of a Wiki-Project: Elements, Process, Approach, Rules

Many companies are unsure of how a successful Wiki project should be started and executed. This article will give you an overview and inform you of the basics. //SEIBERT/MEDIA/ offers transparent services. Ultimately, as the saying goes, we’re also just cooking with water, but we’ve collected many experiences regarding the process for Wiki-projects, which we will happily explain here – regardless of whether or not you are currently running a project with us, are planning a project with us, or simply wish to be more successful with your Wiki – without our help.

License Atlassian Products with //SEIBERT/MEDIA: These are your benefits.

We are a close partner of the Australian software manufacturer Atlassian. We offer you the opportunity to license your Atlassian Products with //SEIBERT/MEDIA: You buy with the official distribution partner, obtain an overall use license including Atlassian-Support and free update authorization. Licensing with //SEIBERT/MEDIA has a range of advantages for you.

SWIFT: The Easiest and Fastest Way to Try Confluence, Jira or Stash

SWIFT is the first step if you want to try out JIRA, Confluence or Stash – without any artificial restrictions. Your free and nonbinding test instance is valid for 30 days but can be extended if necessary. It’s also a great possibility to try out add-ons. All you have to do is fill out a simple form and after about 15 minutes you are ready to start. In this video tutorial our colleague Martin Seibert explains to you the whole registration process and gives you additional information about the difference to Atlassian OnDemand and pricing.