When we started building websites professionally in 1996, we were still operating on intuition. Meticulous project planning was foreign to us. The business developed, we grew and quickly reached a point where we began looking for professional processes for developing our projects. We tried several (Gantt-Charts with MS Project and project checklists we developed ourselves), but none had the result we hoped for. For a while, project managers could decide how they wanted to develop their projects.
With JIRA 7, Atlassian gives individual teams in a company the exact products they need for their use. The license structure was broken up, three new products were created at the same time, and the use cases were changed. This applies to the tools JIRA, JIRA Agile and JIRA Service Desk. In this article, we explain how changes to JIRA licensing affect you and answer the most important questions.
A few days ago, I had to put up with Winfried Felser calling me a “fake.” It was meant as a joke because I had told Winfried that some of my tweets are automatically generated from a blog and our public microblog. In a way, he is right. I really did up my Twitter game in October or November last year – first via Buffer and now Hootsuite. It’s been working really well so far. And I’ve always answered and responded personally and will continue to do so.
Microblogging for Confluence is a plug-in developed by //SEIBERT/MEDIA which gives Confluence the same social media features you know from services like Twitter and Facebook. Microblogs are good for ad hoc discussion, quickly addressing questions and making suggestions and simple exchange between teams, departments or across the entire company (a digital grapevine for the office). Our development team just released version 2.2 which offers a number of new features and improvements.
Linchpin Intranets rock. We have reached a situation where it is more and more difficult to accept new intranet projects. That is why I have joined a hackathon group, that wants to help customers and us improve workshop efficiency and effectiveness. We are trying to come up with a comprehensive plan, samples, concepts, goals and templates for every project step in a new intranet project. In case you didn’t know: Linchpin is an intranet solution based on Atlassian Confluence, that enhances the collaboration with a dozen add-ons and comes with a guaranteed fixed price for professional services.
At the Atlassian Summit 2015 in San Francisco, an entire //SEIBERT/MEDIA team presented our social intranet solution Linchpin (based on Atlassian Confluence) and made all sorts of contacts in the process. To turn these leads into project partners, our Linchpin and Atlassian consultant Eric Klein embarked on an exhausting but successful two-week tour through the U.S. last December. Here is his report.
My colleague and Atlassian consultant Adil Nasri wrote his bachelor thesis in 2015 on the topic of “Functional requirements for wiki systems for use as an intranet using Confluence as an example”. For his thesis, he conducted a scientific study of requirements for intranet systems in which 208 participants filled out surveys. Of those participating, 61.1% worked in companies with Confluence-based intranets, and 38.9% used other technical platforms. The contacts were provided by //SEIBERT/MEDIA.
When I spoke to Mike Cannon-Brooks, the co-founder of Atlassian, during AtlasCamp 2015 in Prague, I was a bit surprised that he wasn’t too afraid of classic B2C messengers as competitors for Atlassian HipChat. I am pretty convinced that Slack as HipChat’s main competitor right now is way overhyped. The solution may have grown faster than HipChat in the past. I still think that Atlassian is in it for the long haul and with their existing strong presence in the enterprise they are in a very good position to win the battle.