Today is my first productive Codeyard day. Codeyard is our new all in one Atlassian solution and will hopefully become as successful as our Linchpin intranet solution based on Confluence. It offers the full Atlassian stack (HipChat, Confluence, JIRA, Bitbucket, Bamboo) including all required professional services (organizational and cultural coaching, consulting, installation, configuration, …) at a guaranteed fixed price.
Continuous delivery aims to reduce development costs through high-level automation, speed up deployment processes, increase the quality of processes and be more flexible and responsive to customer requirements earlier on in the process. (Our video session offers a detailed introduction to the concept.) Part of this article addresses how this is done in practice. We will configure Atlassian’s CI server Bamboo to install a simple Java web application on a Tomcat application server at the touch of a button.
This post is about Linchpin Intranet in 2016. It wants to give you some background information and ask you to participate in our survey to help us understand what you need from us. Please help. We promise to listen closely and offer high value to those who believe in our technology.
JIRA Portfolio helps linking business strategy with daily business. The latest version of JIRA Portfolio 1.9 makes portfolio planning even more realistic. Due to the new capacity visualization, it is easy to see how much work can be done. It becomes transparent whether dates and deadlines really are realistic. Also, it is now possible to edit work day settings to include holidays and off times to be considered in the portfolio plan.
Atlassian has come out with version 6.4 of it’s tracking and project management system JIRA. Lately, the JIRA team has not only been focussing on new functions, but also on integration with other Atlassian products and a continuous optimization and user friendliness. Take a look at the latest updates in JIRA 6.4:
We have discussed the Scrum framework in software development in various of our blogs and in our wiki. The conclusion has always been: it is not an easy task to establish agile methods, however, Scrum is always worth it. In this series of articles, we have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. In the last two articles, we explored how the customers and how staff benefits from Scrum. The last article lists the benefits of Scrum projects for service providers:
We have discussed the Scrum framework in software development in various of our blogs and in our wiki. The conclusion has always been: it is not an easy task to establish agile methods, however, Scrum is always worth it. In this series of articles, we have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. In the last article, we explored how the customers benefit. This article focuses on the benefits of Scrum projects for staff:
We have discussed the Scrum framework in software development in various of our blogs and in our wiki. The conclusion has always been: it is not an easy task to establish agile methods, however, Scrum is always worth it. In this series of articles, we have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. First, let’s take a look at the benefits for the customer:
If you take a closer look at the various company wiki systems available on the market and objectively evaluate them, you will likely come to the conclusion that Confluence by Atlassian is the best and most sophisticated solution out there. Often, such comparisons are made when a company already uses another wiki – a system that grew organically beyond a department, an open-source system introduced as a trial run, or consciously chose the Wikipedia system MediaWiki because it’s the most successful software of its kind.
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?
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationContact
Our Sites
News
Auszeichnungen
