IntraNET.Reloaded Berlin 2017 is over. Our empulse colleagues had a few exciting days at the event with diverse discussions, talks and presentations. Almost 400 attendees discussed the “webification of enterprise communication” and examined the topic in detail. We were able to present Linchpin and Linchpin Touch, developed by our partner //SEIBERT/MEDIA from Wiesbaden, with great success.
My colleague Torsten – our pioneer in landscaping and cultivation – recently came up with the great idea of planting our terrace with useful plants instead of simply decorative ones. Space is abundant, and especially for colleagues who live in the city without their own garden, urban gardening is a great opportunity to put our green thumbs together. There’s also something to hanging out during the lunch break in our own garden with the growing vegetables! 🙂
It’s useful to always extend the 12-month support period for your Atlassian software – you receive regular updates with bug fixes, new features, improvements, and security patches. But when should you extend, and when should you upgrade? Look a little into the future, if your user numbers are increasing it may make more sense to upgrade!
There’s a trend that’s moving away from being always on and always available. Some companies even go so far as to prohibit checking email on smartphones outside of working hours and on weekends.
Nowadays, there are more enterprise software providers coming out with mobile apps. Would this constant email accessibility bring on additional stress? And employees aren’t just getting email. They also have to deal with work-related questions that could come up at any time via push notifications.
I’d like to share a few of my own thoughts and experiences.
Unlike email, an intranet contains information that is valid for a longer time, as well as preserving context and providing options for both synchronous and asynchronous communication. These days, there are better tools than email for communication.
//SEIBERT/MEDIA’s Atlassian Enterprise Club (AEC) had its most recent customer meeting on 28 March. It was a full house at our Wiesbaden office, with many important customers, great discussions, interesting lectures, and seamless organization, all of which created a successful experience with plenty of positive feedback.
This year, we were able to host a notable guest from Sydney, Australia at our AEC meeting, Keshav Puttaswamy, Head of Product (Server) at Atlassian. In his presentation, Atlassian for Enterprises, he gives a comprehensive overview about what’s been done with Atlassian’s server products and looks ahead towards further development.
Confluence and JIRA are definitely great products in their own right. However, there are several great reasons to use them together. Software development teams already using JIRA will benefit from using Confluence as well.
You now have the opportunity to license the entire Atlassian portfolio at a cost-effective flat-rate with Atlassian Stack. This is perfect for large companies whose internal infrastructure is based on Atlassian products or who are planning to convert to an Atlassian infrastructure.
At //SEIBERT/MEDIA, we’ve been developing and creating software for years. During this time, we’ve discovered some basic elements that are vital to building products that gain wider marketplace acceptance and are, ideally, exciting.
When I hear about dissatisfied customers or projects that failed, it’s usually because we’ve neglected to consider at least one of the following “three pillars of successful product innovation.” I now regard them as essential to our success as a product provider.
Last year, Facebook started offering a business solution called, Workplace by Facebook. It’s a variation of the social network of the same name, but for use in the office. Companies can easily register, calculate costs, and quickly get up and running.
But what does the term “workplace” really mean in this case? What does Workplace by Facebook (referred to as Workplace hereafter) actually offer companies?
