Our processes for your successful Intranet project.
Traditional intranet projects are often complex and drawn-out. The Nielsen Norman Group (awards the renowned Intranet Design Annual each year) has determined that developing an intranet required an average of 1.4 years in 2015 . And customers often didn’t know how their intranet would actually look and feel until late in the project. In contrast, Linchpin intranets can be rolled out in a matter of months.
How does an implementation project work and how can you benefit of this process?
Components do not have to be first expensively developed. Instead, they are available as market-ready plug-ins that seamlessly link together. From the start of the project, you have a completely functional prototype of the intranet at your disposal that offers the complete functionality of the final system. Implementation is carried out using modern, flexible and efficient development methods that can accommodate later requirement changes.
Distinction between production and staging systems
In order to avoid disruptions and ensure continuous intranet operation, we set up a test system alongside the production system. This system is a clone of the production system, has the same content and configuration and is embedded in a similar system environment. We install new releases on this test system and test them. New features are then accepted by you. Only then are the features installed on the production system.
Iterative and regular delivery of product increments
Your introduction project is implemented based on the scrum framework. The core of scrum-based agile software development is the regular delivery of product increments to the customer The software’s functionality is gradually extended, and the customer receives a version of their software right from the first sprint. There is a review meeting at the end of each sprint where the development team presents the new functions to the customer. Furthermore, this adaptable process lets you change requirements down the road.
All our software development processes are based on the Atlassian stack with Jira, Bitbucket and Bamboo and take advantage of the options of continuous integration. This calls for many test scenarios that are tested, in large part, fully automatically for each development increment. We will gladly show you our current build pipelines from other projects.
Test system in live operation
We will also operate a testing and staging system with you in live operation to ensure that you can test the new versions thoroughly at your own pace. This way, updates and comprehensive actions can be controlled on the production system and are as short as possible.
Functional prototype from the start
After your project order has been placed, a functional prototype is immediately drawn up. As soon as your users start testing the first prototype, it becomes much easier to bring others on board and rally additional support for the project. This is why a preliminary version of Linchpin is delivered at the start of the project. It won’t feature your corporate design yet but is likely much more powerful than your current intranet or current Confluence instance (if applicable). It includes all plug-ins that the final version will offer and is first operated on our servers since setting up the production system and a suitable staging environment must be coordinated with your IT department, which can take some time. All work on setting up and configuring the software, operating systems and hardware is covered under the fixed price guarantee.
Example schedule for orientation
|Week 1||Written order|
|Week 4||Start of the first (official) sprint|
|Week 6||First sprint review (official presentation of intermediate results)|
|Week 7||Availability of the first prototype with a majority of features|
|Week 8||Prototype is installed on the customer's systems (requires support from your IT department)|
|Week 8||Second sprint review (official presentation of intermediate results)|
|Week 10||Third sprint review (official presentation of intermediate results)|
|Week 12||Fourth sprint review (official presentation of intermediate results)|
|Week 14||Fifth sprint review (official presentation of intermediate results)|
|Week 16||Test phase is completed, new intranet portal put into production|
|Week 18||Acceptance is issued. Introduction project is completed.|
What can and should you do yourself to establish a successful social intranet?
The implementation and establishment of a social intranet is a project that often accompanies change in company culture – leading to better informed employees, more trust and less regimentation. Management must stand behind such a project from the start. Early employee involvement is an important factor to success. The following suggestions provide best practices for effective change management.
Make the prototype openly available
Give employees the opportunity to acquaint themselves with the system; e.g. with a large touchscreen in the employee cafeteria, in the foyer or other heavily frequented areas. We can also provide you with such a device for a limited time at no charge.
Kick off an internal marketing campaign
Trailers, posters, stickers, holding devices, notepads and other similar advertising materials with the right message call attention to the intranet and its possibilities and help highlight application scenarios.
Establishing an intranet charter
An intranet charter offers a code of conduct and usage guidelines for collaborative efforts. It helps prevent misunderstandings from arising and ensures proper use. We can give you a template for such a charter.
Viewing the intranet as a project of change
View the project not only as an IT project but also as an opportunity to improve company culture. The key to a productive social intranet is culture, not technology.
Officially announcing the project
Management should be transparent from the start and officially announce the new project (for example with a trailer). Management should prepare employees and manage expectations on practice and use of Intranet 2.0.
Involve the works council at an early stage
Involve the works council from the start so there are no misunderstandings and show the council useful ways to get involved with the intranet project.
Make project progress transparent
In order to record and document project progress, you should offer period project status reports during sprint reviews of the introduction project and make them accessible to all stakeholders (if applicable, for employees too).
For the actual introduction, management can think about a doing a roadshow or giving intranet presentations at various company locations.
Determine user requirements
Conducting surveys during the implementation and roll-out of the intranet system will help you recognize user needs.
Pick a name together
If the employees are included in naming the intranet, the intranet will receive more attention and encourage identification with the system. A naming competition might be a good idea.
Offer informational materials
Users should be able to easily inform others about the new tool. Provide them with a flyer, FAQ, internal blog articles, training documents, presentations, etc.
Homepage on employee computers
The new social network can be set as the homepage on employee computers.
Consulting by experienced service providers
An experienced and reliable partner together with a strong and flexible platform with a powerful and efficient process will guarantee that an intranet is a sustainable solution.
Who is //SEIBERT/MEDIA?
Since 1996, //SEIBERT/MEDIA has been a professional internet and intranet service provider with offices in Wiesbaden and San Diego. Over 100 employees make up independent interdisciplinary teams in all areas of the organization focusing on agile software development. The company covers all facets of strategy, consultation, conception, design, software development, operations and security. //SEIBERT/MEDIA is a leading service provider for software tools that promote communication and collaboration in companies and is among the leading Atlassian Experts in the world. More than 60% of all DAX companies are among our customers as are numerous other companies of all sizes from all types of industries. Linchpin intranets have been rolled out in companies with over 50,000 users all over the world.
Holistic project assistance
We take care of your intranet introduction project from design to delivery and offer the software system, licensing of all components, required services for implementation and implementation consultation, training, and, if necessary, hosting from a single source. For all these things, we have experienced experts on our interdisciplinary teams with experience from hundreds of holistic web and intranet projects.
Even after the roll-out, we will not abandon you with your intranet. We will gladly help you continuously develop your system, mobilize your employees to use the system and resolve any challenges that arise quickly and smoothly. We also serve as the German-language interface for Atlassian support.
Why a Linchpin introduction project with us?
- //SEIBERT/MEDIA is one of the few intranet service providers who deliver a functional test instance that meets all your requirements.
- Compared with other established intranet solutions, a Linchpin project is very affordable (much lower licensing fees and comparably lower service costs).
- We invoice Linchpin introduction projects at a guaranteed fixed price. These costs cover the implementation of all requirements.
- Many traditional intranet projects are very complex and take a long time to implement. Linchpin can be rolled out to users only a few months after the project is commissioned.
- We have extensive experience with Confluence intranets. Upon request, we can refer you to other intranet customers so you can call them and ask about our high quality services.
- The Confluence developer Atlassian puts their faith in //SEIBERT/MEDIA. We are the largest German Atlassian partner and are among the top 5 partners in the world.
Demo instance and test accounts
The Linchpin demo instance is equipped with a clean and simple theme and some demo content. You can play around, test, and get to know Linchpin on your own. No worries, you can’t break anything. We hope you will get a good idea of how Linchpin works and what makes a Confluence-based intranet work.
Please note that the Linchpin demo instance will be reset every Sunday. If you want to test Linchpin fully fledged for 30 days or more, please go ahed and create your own demo environment. It’s up and running in an hour, for free and has no strings attached.
1. Go to a demo instance
2. Log into a demo instance
Standard user account
Claire Customer: A standard customer login with basic access rights just like a standard user.
- username: kholmes, password: kholmes
Customer Administrator: A customer administrator login with extended rights that let you access configuration pages of the most important Linchpin settings and plugins.
- username: pwinter, password: pwinter
- username: tschroeder, password: tschroeder
Create your own test instance
Instead of testing the public Linchpin demo instance you can create your own instance with a click. It’s up and running within an hour and free. We even help customizing the design if you ping us.