//SEIBERT/MEDIA is one of the biggest Atlassian Experts Partners worldwide. And of course we intensely use Atlassian tools for our internal organization. In the following video our colleagues Martin Seibert and Alex Boerger demonstrate first conceptual and later directly in the system what roles Confluence, JIRA and HipChat play in our digital communication, how the tools are connected to each other and how they support coordination, teamwork and productivity.
By using management dashboards, your company’s managers will have access to a better overview and more transparency. By dashboards, we mean graphical evaluations that represent certain quantifiable key numbers in charts and make time segments visible through trending. This compiles information into a critical mass in an easily understandable and accessible way.
draw.io is the leading diagramming plugin for Confluence and JIRA. draw.io enables you to collaborate seamlessly in creating diagrams that aid the communication of information in both Confluence pages and JIRA issues.
The Data Center deployment option that was already available for JIRA was designed to meet the needs of large enterprise customers providing performance at scale, high availability and instant scalability.
Have you ever wondered how to visualize a server rack on a tool like visio with a fully integrated Confluence tool? draw.io is the answer.
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.