Existing intranet and wiki systems in all companies are filled with content. When it comes to launching a new Confluence system or a Confluence-based intranet such as Linchpin, many customers want their existing information to be transferred to the new environment and want a fool-proof and efficient migration strategy.
Jira is typically regarded as a technical tool. In some companies, this reputation is so widespread that the IT and software teams use the Jira intensively, while other teams avoid it completely. In this two-part article, I’m arguing why it’s worth freeing Jira from this unfair constraint and expanding its use into the company as a whole.
Technical teams in many companies work happily and successfully with Jira – but software that has a reputation for being a development system is not normally something which the Average Joe can also use for their work. When such a person starts working with Jira for the first time, they may be a little overwhelmed by the depth of the system’s many features and functions. Nevertheless, we and many of our customers use Jira with completely different teams and company departments. The advantages of Jira are not limited to just our technical teams. You can clearly see the advantages that Jira brings to all sorts of teams when you focus on its ability to be transparent, its visualizations and how it inspires collaboration rather than technical integration.
Modern software should help you keep all employees within your organization informed, no matter where they are. Unfortunately, many companies are failing when it comes to corporate communication and keeping their employees up to date with that is happening.
Although this demonstration was from several years go, it is still relevant today. And in fact, Atlassian’s expanded tool suite have only been more tightly integrated! Atlassian’s tools ensure they work well together, achieving a seamless integration of ticket and tracking systems, continuous integration servers and repository management systems.
Back in 2014, we hosted Jens Schumacher, then the group product manager for Atlassian’s development tools in Sydney for a few days. We captured this demonstration where he showed us how Jira, Stash and Bamboo work together – from issues to branches, pull requests and tests, to a successful quality-checked release of a change made to the main code base.
Let’s have a look at how Atlassian’s tools were integrated all those years ago!
In addition to an introduction, we believe it would be useful to actively exchange information with the existing community. So, last November we organized a community and user meetup for ERPNext at our head office in Wiesbaden, and were delighted to host Rushabh Mehta, the founder of ERPNext.
There are quite a few intranet systems that include native instant messenger solutions with integrated chat functions. At first glance, an all-in-one package like this might seem attractive. But looking a bit more closely, it might not be such a good idea.
It is clear there is only so much synchronous communication a person can participate in. There is a natural limit to the amount of time you can spend coordinating with others in real-time, and ultimately, the rhythm of your workday defines the upper limit. In this post, we look at how to make active and conscious choices on when synchronous communication is effective and when it’s not.
Collaboration with partners is an important factor in the continuous development and improvement of our products. Here is a video interview with Brandon Huff from one such partner company, cPrime – a leading Atlassian expert. We talk about our software solution for the implementation of SAFe with Atlassian tools – Agile Hive – its potential from the viewpoint of a US partner, regional differences in scaling agile methods, the importance of comprehensive software integration, among other things.
In this post, we look at the prioritization process used by Atlassian to determine when a new feature will be released for which of its two deployment options – Data Center and Server. We consider the criteria used in the decision-making process to make the decisions more transparent and understandable for customers.