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.
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.
In the article Architecture of a Wiki-Project: Elements, Process, Approach, Rules, the procedure for a typical adoption of a Wiki is portrayed in detail; we suggest you read that article first. This article completes our explanation with the types of questions, which many customers have, questions that require coherent, unambiguous answers.
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.
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 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.
Microblogging for Confluence is a plugin developed by //SEIBERT/MEDIA, which expands Confluence by a seamlessly integrated microblogging function. Developed within the scope of an intern “Hackathon” and since then constantly enhanced by our team, this add-on has gained a great stability and a wealth of features. We have now released a new version. In this article we show the big and small innovations that are part of the latest release.
draw.io is a sophisticated diagramming plugin for Confluence and JIRA, created by JGraph. With draw.io you can quickly and easily create a wide range of diagrams in both Confluence and JIRA: flow charts, network diagrams, org charts, UML diagrams, mind maps, and many more. Here are some examples. The underlying core technology, mxGraph, has been in development since 2005 and today is the market reference implementation. In 2012, the draw.io plugin for Confluence was created for the Atlassian Marketplace, these are some of the advantages of draw.io for Confluence and JIRA.
Did you know that Atlassian has a beer wardens? That the Atlassian User Groups in Sydney meet at the Hall of Justice? That there is an extremely dangerous item in the kitchen of the Atlassian office? That Atlassians innovation program ShipIt offers very practical solutions to everyday requirements? We bet you didn’t. Check out the video tour to learn more.
Exciting product news, such as Confluence Questions, were announced during Atlassian Summit 2013, Atlassians big user and partner conference. Confluence Questions expands Confluence by functionalities to build a knowledge base, which allows the user to actively ask for information. During the Summit, we met and interviewed Matt Hodges, Product Marketing Manager for Confluence, and Chris Kiehl, Dev Manager in the Confluence Team. What can Confluence Questions do? How does it differ from Microblogging-Tools such as Yammer, where users can also ask questions? Why is Confluence Questions not available with Confluence for Enterprise customers, but needs to be licensed separately? The following video has answers to these and more questions: