- Created by Uta Opitz, last modified by Administrator on Sep 04, 2014
Recommended variations with optimal cost-benefit ratio:
Position | Lower Quartile in USD | Recommendation in USD | Upper Quartile in USD |
|---|---|---|---|
Wiki consulting at project start re: content/form/strategy In this first phase we will make sure that the wiki project is properly set up. If you just call out to your employees “Hey everyone! Now we have a wiki and we'd like for everyone to use it!”, you can probably assume that – at least in most cases – nothing is going to happen. Whoever is unwilling to spend time to think about the organizational requirements of a wiki in order to apply these to the company, should lower their hopes for the success and effect of the wiki. Do you already have some experience with wikis? Then you could probably handle some of these services yourself, thereby requiring fewer services from us. Our experience / Our recommendation: 12 x 200 = 2,400 | 800.00 | 2,400.00 | 4,000.00 |
Wiki installation and configuration with systems administrators You cannot have a successful wiki introduction without a technically perfect system. Don't be satisfied with a system that can be set up quickly without any plugins or quality control checks. Sure, the technology for a successful wiki is just one necessary component. Still, compromises in this area can be quickly devastating.
| 840.00 | 1,120.00 | 2,240.00 |
Wiki customization (Design): Dashboard, print view and templates for PDF documents In this project phase, our well qualified communications designers work together with our front-end developer to create your customized enterprise wiki. Many companies believe they can save some money here, thinking “But it's only an internal system!” or “The other internal systems are ugly too. All of our employees are used to this.”
| 2,200.00 | 3,850.00 | 6,600.00 |
Programming of wiki design and removing of usability problems Wikis are standardized systems. Open-source-systems, and especially their dashboards, should be customized to remove usability problems. This is not an option: it is a fundamental requirement. In addition, our designers' templates need to be programmed and integrated into the wiki. In this phase of the programming, there are particularly high demands regarding the compatibility of different browsers and browser versions, the optimization of designs for various solutions and monitor color settings, and the consistency of source code and sustainability.
| 4,200.00 | 5,600.00 | 7,000.00 |
Professional wiki workshops for the rollout Using a wiki that works is incredibly easy. However, you have to know how to help your wiki work. You can learn in our workshops how a wiki needs to be structured and built to work properly. We set up the system for your company and train your administrators so that later on you can do everything yourself. If you like, we'll even show your employees how to use the system. In our recommendation we assume that we'll need 4 hours per workshop. There are also some additional costs associated with workshops (http://seibert.biz/reisekosten). The workshop price calculates the price for our employee at the “Partner” level. Our experience / Our recommendation: 4 Hours per Workshop, 2 Workshops => 2 x 4 x 200 = 1,600 (one Executive-Level Employee, i.e., a “Partner”) | 1,200.00 | 1,600.00 | 6,400.00 |
Organizing of enterprise wiki and monitoring of the development of the structure After the workshops your employees will have a fundamental understanding of how the wiki is constructed, what belongs in the wiki, how it should be structured, and how users can adjust their individual settings. Still, during the development there are always going to be more questions and a need for support that requires fast and uncomplicated answers. Our experience / Our recommendation: 8 x 170 = 1,360 | 680.00 | 1,360.00 | 2,720.00 |
Wiki marketing and rollout – the best ways to attract attention Depending on your company's situation and management's goals, it might be logical to promote the use of the wiki in order to strengthen the positive effects for all employees. It doesn't matter at what point in time you take a closer look at your wiki: You'll always say “The wiki would be even more valuable for all of us if even more employees would begin to use it more intensively.” This is true for the very beginning as well as for the most successful wiki implementations within any company. Our experience / Our recommendation: 8 x 170 = 1,360 | 0.00 | 1,360.00 | 6,060,00 |
Quality control and tests Whenever we are finishing our work at a company, we are completely focused on delivering error-free quality. This is why our quality control and tests are only performed by the most experienced members of //SEIBERT/MEDIA. These employees all have at least 10 years of experience in this area. During this phase you could also decide to have additional automated tests performed using Selenium IDE (please see our expert article on this topic at Selenium IDE). Our experience / Our recommendation: 7 x 170 = 1,190 | 170.00 | 1,190.00 | 1,700.00 |
Project management for the wiki pilot (introductory phase) //SEIBERT/MEDIA's project management is professional and flexible. Thanks to our reliable process control, we can offer you any level you need, from “slim and agile” to “the whole nine yards.” Find out more about possible project management processes at our workflows. Our experience / Our recommendation: 20% of the total hours spent on the project. | 4,900.00 | 4,900.00 | 5,300.00 |
Total: | 14,990.00 | 23,380.00 | 42,020.00 |
- No labels
This content was last updated on 09/04/2014.
This content hasn't been updated in a while. That doesn't have to be a problem. Some of our pages live for years without becoming obsolete.
Old content can be incorrect, misleading or outdated. Please get in contact with us via a form on this page, our live chat or via email with content@seibert.group if you are in doubt, have a question, suggestion, or want changes from us.