At //SEIBERT/MEDIA, we’ve been working on a wiki for years. Through our day-to-day work as well as through dozens of enterprise wiki projects, we have experienced – thanks to innumerable different cases – how useful and valuable a wiki can be on a number of levels. Therefore, we believe it is high time to compress the arguments for a wiki into the limited space offered by tweets to make our points as efficiently as possible.
During the most recent meeting of the Atlassian Enterprise Clubs by //SEIBERT/MEDIA, Jens Schumacher, the Group Product Manager of Atlassian Dev-Tools in Sydney, was our guest for a couple of days. In an interview, he directly demonstrates the close links between JIRA, Stash and Bamboo – from issues over branches, pull-requests and tests until the successful, quality assured shipment of a change in the main codebase.
Wikis for enterprise use, both those available commercially as well as those available in open-source contexts, have become quite sophisticated. This article introduces and evaluates possible requirements as well as decision-making criteria.
Whenever we speak with clients and go through possible services with them, they often have questions regarding why we offer services such as “Layout Design” or “Executing the Design in HTML and Implementing within the Wiki”. In this article, we will offer you a couple of arguments and explanations to answer why it is worth having your wiki professionally designed.
We can no longer conceive of the //SEIBERT/MEDIA Intranet without a Wiki. As a knowledge management system and employee portal, the Wiki is of incalculable value within the company network, fueling the Intranet motor.
Every company has individual needs regarding its internal systems, wants special features and finds bugs, that are unnoticed by other organisations, due to specific workflows. Atlassian listens to its customers and offers a variety of possibilities to report certain issues to the developer teams and to take forward the implementation. What you can do, if you want to escalate an issue, is shown here.
Starting with HipChat for Mac 3.0, Atlassian began to roll out a new version of HipChat that looks a whole lot different. At first you’ll notice it’s lighter and cleaner, but there’s a lot more going on. Read about the new HipChat in this post.
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.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationContact
Our Sites
News
Auszeichnungen
