We’ve already published 111 good reasons for enterprise wikis. Now we’d like to show through example use cases just what you can do with an enterprise wiki. //SEIBERT/MEDIA has distilled 66 examples for use cases: the first 22 can be found here; now, let’s move on to use cases 23 to 44.
We have summarized in our weblog 111 good reasons for using an enterprise wiki. But how can such a system blossom and show its’ added value and Return on Investment? What are some concrete examples of how companies can implement an enterprise wiki? Which possible uses make sense? Which of them are truly useful? And which of them can actually improve your efficiency? We have collected 66 ways to use wikis in organizations. Here are the first 22.
What before was true for the video recorder is unfortunately again true for many current websites: users have difficulties in completing tasks and reaching their goals. How to use those formerly expensive video recorders was just something the user had to learn, for better or for worse; after all, the piece of equipment was paid for. But the next website – and therefore the next provider of comparable services – is only a click away.
When introducing a new and in its type different software, this aphorism, that once Oscar Wilde and also Mark Twain adjudicated, fits very well, because: a wiki adoption can not be repeated very often. This is why we recommend to prepare a wiki project in the timeframe of a pilot phase, for later application.
Working with Confluence, you notice how fast the content of your wiki is constantly expanding. Eventually some content needs to be updated due to new information or developments. The question that might arise: Shall I create a new page with new content or rather update the existing page? In this video, Martin Seibert from //SEIBERT/MEDIA explains the advantages of updating a page rather than creating a new one. This approach might involve a bit of work and time but reduces redundancies and helps communicating updates to the existing followers of the old content.
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.
Being introduced to JIRA can be intimidating and overwhelming. JIRA is a very powerful and complex task management and bug tracking system. However, the key functions are very simple and user friendly. Starting to work with JIRA issues is the best way to become familiar with this tool. In the following tutorial, Martin Seibert from //SEIBERT/MEDIA shows how create issues in JIRA and gives an overview of the configuration options.
If measures for quality assurance and both internal and customer projects don’t run ideally and thus inefficiently, it is often due to a lack of established and binding workflows in task management. This article focuses on the use of JIRA and shows how JIRA can be used to convert all kinds of tasks into systematic and transparent procedures with the help of prototypical workflows. //SEIBERT/MEDIA is happy to provide you a JIRA test instance free of charge and without commitment, so you can learn about the following workflows and the diverse functions of JIRA.
A form that issues an error message after completing is an annoyance for the user and doesn’t generate any requests. Or: An interactive feature suddenly no longer functions after maintenance work on the code. These and similar scenarios are well-known to web developers. Therefore, it is indispensable for solid high-quality web applications, to run an acceptance test on a regular basis and make use of systematic bug tracking.
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.