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.
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.
The JIRA plugin Tempo Planner offers agile capacity and resource scheduling, team and project management, and business data for teams. It extends the JIRA platform by deeper agile planning and management specific features.
LINCHPIN is the social intranet suite from //SEIBERT/MEDIA, that expands Confluence by a completely customizable internal platform, which is the basis of communication and collaboration among employees. The Navigation Menu Editor plugin is a central function we have developed. This feature allows for a quick and easy integration of a global navigation bar in the Confluence user interface. It makes it possible to directly access all important sites.
Stash 3.2 offers you a few helpful updates. Branch compare already allows you to view differences between two branches and with Stash 3.2 you can now create a pull request with one click. You will know the code changes, that will be merged, before you create the pull request. Click to read about all the updates.