The newest release of JIRA Agile provides richer data during the planning process by making agile cards more customisable than ever before. Read more about the new features in this post.
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.
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.
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.
“We’re very happy to have you guys on board!”
//SEIBERT/MEDIA has been working with the Australian software manufacturer for years. Offices in Germany, the U.S. and Australia, //SEIBERT/MEDIA is one of the biggest Atlassian partners in the world. We have talked to Atlassian employees on several occasions and asked for their feedback.
A few weeks ago, Atlassian released Confluence 5, a major update of it’s enterprise software. A great occasion to review the development of Confluence since version 3.5, which is still running in many organizations. There have in fact been fundamental changes since Confluence 3.5. The following are the main features of the last big releases: