When, in the middle of a meeting, Martin managed to convince me to start writing blog posts, we were talking about intranets that can live independently, so to speak, because they are ‘fresh, healthy, robust, adaptable and vital’. Nearly everyone understands this metaphor in the work environment. This message is even understood during sales pitches. But its real potential, its incredible resilience, is much harder to understand and to explain.
Until 10 or 20 years ago, intranets were created either as a result of an experiment (for example in IT), or because there was a need to improve communication within a corporation. In the meantime, intranet capabilities have increased tremendously and stakeholders’ requirements diversified. What objectives are there for an intranet?
The intranet started its triumphant progress about 20 years ago. However, it’s only recently that corporations started to focus on their intranets’ true stakeholders: the employees. Not long after the emergence of intranets in organizations, those responsible for them started to ask what a modern intranet actually is. After all, no one wants to set up an outdated system that employees don’t want to use. Today, in the times of digital transformation and Generation Y, intranets are at least as important as 10 or 15 years ago. But what is a modern intranet nowadays? Is a ‘social intranet’ with user profiles, status updates, communities and chats sufficient?
Atlassian has released Confluence version 5.7, which includes a variety of new features. The team collaboration system now fully supports files in any format and offers in-line comments for pages and even attachments. It also comes with the Roadmap macro, which simplifies the HipChat integration. Advanced users now benefit from the Confluence Query Language in the content search.
In agile software projects, it goes without saying that the developers work together. Scrum is, after all, based on teamwork. In most cases, however, each programmer works alone in front of their screen. The concept of pair programming is different because it pairs up two programmers who then together work on the same task, taking turns who sits at the keyboard. Customers unfamiliar with the pair programming idea might think this is some sort of job creation program: Why should we pay for two developers to work on a task that one programmer could do alone? This would only make sense if it cut development time in half, but that is most certainly not the case. No, this is indeed not the case. But how does pair programming benefit customers then?
If two users (accidentally) edit the same Confluence document at the same time, data may be lost in some circumstances. Conflicts arise, the changes made by the users are not correctly merged, entries are lost and must be redone. The Edit Lock Confluence plugin developed by //SEIBERT/MEDIA ensures better protection and less confusion by displaying a more visible and interactive warning.