Numerous internet surfers probably know the following process: you’re surfing a website and you find a link with an e-mail-address. You click on the link, which begins your odyssey-like journey through the depths of your computer. Why? Because the link leads to the whirring of your hard drive, as the mail-client installed on your computer stirs to action (or, possibly, asks to be set up) and all sorts of additional windows begin to pop open on your screen. Even though you had just been comfortably surfing through the web, now you have to master strong currents as you fight off towering waves.
We have already summarized 111 solid reasons for using an enterprise wiki. Now with the help of some concrete examples we are going to show you how an enterprise wiki can actually benefit your firm. Following in the footsteps of examples 1-22 and 23-44, we now close our series with 22 more concrete use examples.
It is now possible for software teams to implement development best practices and world-class project tracking at the same time without hassle. JIRA 6.3 is now more integrated with Stash and Crucible. The moment the development of an issue is complete, JIRA automatically updates the issues. In addition, JIRA Agile now allows the entire team an end to end view of the project through enhanced reporting decisions.
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.