All posts by Martin Seibert

66 Use Cases for an Enterprise Wiki (1 – 22)

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.

Confluence – Update pages to reduce redundancies

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.

111 Reasons why you need an Enterprise Wiki

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.

Real integration: The interaction of JIRA, Stash and Bamboo

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.