Within a company there can be many approaches for the development of texts as well as the sharing of texts for further revision. We could, for example, write a text in Word and then load the final version into the enterprise wiki. We could also send around texts by e-mail, asking colleagues to read them and, if necessary, to make changes. But we could also develop a text directly within a wiki. What should we think of this particular work process?
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.
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.
By using management dashboards, your company’s managers will have access to a better overview and more transparency. By dashboards, we mean graphical evaluations that represent certain quantifiable key numbers in charts and make time segments visible through trending. This compiles information into a critical mass in an easily understandable and accessible way.
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.
The Data Center deployment option that was already available for JIRA was designed to meet the needs of large enterprise customers providing performance at scale, high availability and instant scalability.
Within an Intranet, Wikis are a good means for the quick and uncomplicated collecting of information that is needed for the long-term; this creates a base of knowledge as well as a platform for communication that is always available to the participating employees.
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.
Did you know that Atlassian has a beer wardens? That the Atlassian User Groups in Sydney meet at the Hall of Justice? That there is an extremely dangerous item in the kitchen of the Atlassian office? That Atlassians innovation program ShipIt offers very practical solutions to everyday requirements? We bet you didn’t. Check out the video tour to learn more.