Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • 6 George Street, Cranbourne, Victoria, 3977, Australia Founded: 2002 Employees: 1.001-2.500 sales@atlassian.com 1(415) 701-1110

    (0 reviews)

    Industries: , 105 views, 0 comments

    A brief history

    Armed with a credit card and a dream, two college friends, Mike Cannon-Brookes and Scott Farquhar set out to create Atlassian. In 2002, they didn't know what kind of company Atlassian was going to be, but they knew exactly what it shouldn't be—an environment where they had to conform rather than be who they authentically are.

    Now, over 15 years later, our team has grown to over 3,000 Atlassians worldwide with offices around the globe. But it didn't happen overnight.

    Values to live by

    Our unique values describe, at the most fundamental level, what we stand for. These five values shape our culture, influence who we are, what we do, and even who we hire. They're hard-wired into our DNA and will stay the same as we continue to grow.

    We ❤️ teams

    Over 150,000+ customers use Atlassian to empower their teams and drive their missions forward.

    We take 'Don't #@!% the Customer' seriously because our customers are the reason why we do what we do. It's even why we price our products, so every company can afford them. They inspire us, challenge us, and in turn, help us build better products.

    Working open

    We believe all teams have the potential to do amazing things when work is open.

    Much of the world works, often unwittingly, in a closed way. Information is hidden or lost, bonds between teams and teammates are weak, and perspectives are withheld. The result? People burn out. Knowledge is wasted. Potential is left on the table. Forward progress is halted. This is why Open matters. This is why we do what we do at Atlassian.

    Open work has always been central to our values. It's in the DNA of our products and we bring it to life through our practices. But it doesn't just happen. Our teams make an effort to work, communicate, and collaborate openly every day to lead by example.

    Open unlocks new opportunities. Open brings us together. Open unleashes potential.

    • Jira Software Cloud

      Jira Software is part of a family of products designed to help teams of all types manage work. Originally, Jira was designed as a bug and issue tracker. But today, Jira has evolved into a powerful work management tool for all kinds of use cases, from requirements and test case management to agile software development. In this guide, you'll learn which features and functionalities of Jira can help your team with your unique needs. 
    • Trello

      Trello helps teams work more collaboratively and get more done.
      Trello’s boards, lists, and cards enable teams to organize and prioritize projects in a fun, flexible, and rewarding way.
      Work with any team
      Whether it’s for work, a side project or even the next family vacation, Trello helps your team stay organized.
      Information at a glance
      Dive into the details by adding comments, attachments, due dates, and more directly to Trello cards. Collaborate on projects from beginning to end.
      Built-In Workflow Automation With Butler
      Let the robots do the work! Boost productivity by unleashing the power of automation across your entire team with Butler, and remove tedious tasks from your to-do lists with:
      Rule-Based Triggers Custom Card & Board Buttons Calendar Commands Due Date Commands
    • Confluence Cloud

      Confluence is a web-based corporate wiki (collaboration software) developed by Australian software company Atlassian. Atlassian wrote Confluence in the Java programming language and first published it in 2004. Confluence Standalone comes with a built-in Tomcat web server and hsql database, and also supports other databases.
      The company markets Confluence as enterprise software, licensed as either on-premises software or software as a service running on AWS.
    • Jira Work Management

      Jira Work Management combines cutting-edge work management capabilities with the power and customizability of Jira to create a new standard for business teams managing projects. Marketing, HR, Finance, Design, Legal, Sales, Operations, and other teams of any sort will find it easy and intuitive to get work done in this new Jira product built just for them.
      This is the first Jira built for business teams, by business teams. We crafted this new Jira experience directly with customer design partners of all sizes and industries, as well as internal Atlassian teams of every type — including our own Jira Work Management teams.
    • Advanced Roadmaps - Adding a portfolio workflow to Jira Software

      Regardless if you work in a continuous delivery flow like Kanban, a sequential delivery flow like waterfall or an iterative delivery flow like Scrum, you will benefit greatly from having portfolio management. Having a dedicated funnel ensures that you get a proper overlook of your incoming request. In this article we will discuss how that can be done by creating a process for it in Jira Software.
      Advanced Roadmaps is a very useful tool because it allows us to get the big picture. It also allows us to scale the hierarchies in Jira for issue types. This is important because the standard hierarchies are designed for teams, so they do not scale well. While you can work around this using the sideways approach where you have the higher hierarchies in a separate project and link between them, that is not really a hierarchy. This also works poorly when you wish to display things in Advanced Roadmap.
      The first thing we need to do for a proper hierarchy view in Advanced Roadmaps is to define the portfolio levels. We need to accommodate for multiple scenarios as requests, or demands, often come in different forms. The most common types are projects or even programs, or new features. We also want to make sure we can work with the different frameworks out there, so we add a collaboration level as well as defined in SAFe.
      To avoid a lot of confusion between different frameworks and other tools, we rename the Epic issue type in Jira Software to Feature. It will not be perfect, but it will have to do until we get the ability to rename it properly when Atlassian makes that change in the future.  We do this by going to Issues -> Issue Types and edit the Epic issue type. We also add two new issue types for Initiative and Capability.
      Next we go to Plans -> Settings -> Advanced Roadmaps hierarchy configuration. There we add two new levels called Initiative and Capability and map them with our newly created issue types with the same names. Finally, we rename the Epic to Feature, and we should have our first hierarchy defined. We can go back and adjust this later if we want. The setup should now look like this:

      We can now add this to our projects by adding the issue types to our Issue Type Schemas. Depending on your setup you may want the new issue types for Initiative and Capability to exist in a separate Issue Type Schema, or you will add them to the standard schema. Either way we still need to give the new issue type a workflow that match their purpose. So we head over to Issues -> Workflows and create a new workflow.
      Again we want to consider what the purpose of these issue types is and who will actually work with them. Initiative, Capability and Feature are all used by management and requirement analysts to provide information on how to realize demands. That means that we do not have the same transfer of responsibility as for User Stories. Instead, we need to consider what we actually do in the portfolio and what we need to track in terms of activities.
      SAFe have a pretty good example of this for their Portfolio Kanban. Their first step is Funnel and for us that is pretty much everything that comes into our workflow, and we define this as new. Anything that comes in to the portfolio needs to be reviewed to see what we should focus on next. Since we will not review everything we add two steps for the review process: Ready for Review and In Review. This allows us to only pick things that we want to review by moving them from new to Ready for Review, and then we have an active status to indicate that we are working on this.
      We do the same for Analysis, which is the step where we involve Business Analysts and Requirement Analysts to define the need in more detail. For this we add Ready for Analysis for when the Review process lead to us spending time to break down the need in a requirement process. We also add the In Analysis to indicate that it has entered the Requirement process.
      Before we close this workflow we add the Implementation process as well. Ready for Implementation indicate that the requirement process has led to a decision to implement and In Implementation indicate that the need is being fulfilled. We do not fracture this further as we can easily drill down to individual tasks in Advanced Roadmaps, and it is not really useful to have for example test and release part of this workflow. That is because each issue type will have many issue types below it, and you can only transition on the last sub-task, making it misleading and feeling stagnant.
      Finally, we add a status for Blocked/Pending to allow us to track when things are preventing this activity from being fulfilled. This can be external or internal dependencies or financial reasons for example.
      As always we go for an open workflow to allow for free transitions. We add a close screen to the Close status to set a resolution and then add a post function to remove resolution on all other statuses. This workflow should now look like this:

      The final step is now to go to our workflow scheme and add this new workflow. We do this by going to Issues -> Workflow Schemes and click edit on the workflows scheme we have Initiative, Capability and Feature added to. We click add Workflow and add the new workflow we just created. Then we select that this workflow will be applied to Initiative, Capability and Feature before hitting save.
      This should now allow you to work inside Advanced Roadmaps using Initiatives, Capabilities and Features in a proper portfolio management process that allow for larger projects and programs as well as manage smaller feature or even user stories.
      I hope you found this useful and as always, if you have any questions just write a comment and I will do my best to help you.
    • 4 new feature for DevOps in Jira provide more visibility and better insights

      One of the biggest cause for complicated workflows and custom fields is the fact that Jira has never been a deployment tool, but the teams need the visibility of deploys. With this latest update to Jira Software Cloud we see improvements in this field with no less than four new features. DevOps teams or not, this will make life easier for everyone.
      While there are several add-ons for Jira Software Cloud that will tie together repositories with Jira, this is now a standard feature in Jira. That means that it can be used with no additional cost (except for the Premium features if you don't have Premium of course), which lowers the entry point substantially. Hopefully this will mean the end of operations based statuses in the workflow and custom fields to hold release data.
      Code in Jira
      This feature allows you to connect your repo to Jira so you can visually see the repos in a new tab in your project called Code. Doing so if fairly easy, especially if you use Bitbucket, but adding Github for example takes only a few minutes. The biggest benefit of this feature for me however is that you will see the repo information in the Jira issue itself. This provide a lot of information to the viewer on where this issue has been committed.

      Deployments in Jira
      This is where things get interesting.  With Code in Jira above you can see where your code packages are and their status. With Deployments, you can see where those packages also have been delivered to. This provides a very nice overview of where your code currently is available, which is what most people want to know when they try to build this into their workflows or work views.
      Premium Features
      The last two features are only available for the Premium version of Jira Software Cloud. Normally I don't like to have features split between a standard and a more expensive version, but these two features are all about measuring which I think is fine to have as a bonus if you need the more expensive version.
      Deployment Frequency

      Cycle Time

      My Thoughts
      This is a very good addition to Jira Software Cloud that have been needed for a long time. While I think the Premium features is mostly for numbers people and not really for the daily work I think this still is a solid addition. I would like to see the deployment information on the issues and it needs a connection with Insight, so I can connect deploys to my assets.
      There is a lot of potential here and I look forward to seeing this taking further in the future.
    • Jira Work Management - What is it and why do you want it?

      Atlassian recently announced a reboot of their Jira Core, which was practically unused by everyone due to its lack of unique features. The reboot comes with a new name, Jira Work Management, and a new setup focused on business teams. This is a great change and it will make Jira a bit more interesting for business teams in the future.
      Four views to rule them all
      Jira Work Management focuses around three main views: Board, List View, Timeline and Calendar. There are of course other features as well, such as a form builder experience as in Jira Service Management and the ability to pick a background color. The focus is on these four views however and they will determine how the business teams will react to this reboot.
      The List View

      The list view will appeal to anyone who spend a lot of time in Excel, or if you use something like Asana or Tasks in Teams. Inline editing and individual settings for the visual changes are big selling points, even if I foresee a bit of confusion when the views differ from user to user.
      Timeline View

      The timeline view is pretty much a slightly watered down version of the Roadmaps feature in Jira Software. It will work well for team level, just like Roadmaps in Jira Software, but not much more.
      Calendar view

      The Calendar view is nice, even though I am not so sure how useful it actually is. if we could tie it to our tasks in Outlook, then maybe the calendar would be more useful, but for now I think it will be more of a glance tool, just like the list and timeline views. I could be wrong though and I would need to try it out to test it out for real.
      Board View

      The board view is the only view that existed in Jira Core as well and it looks pretty much the same. This is very similar to Trello and it will be a nice alternative to Teams that are used quite a lot for this kind of view for many business projects.
      The four views will pretty much satisfy most need from a business team, but my question is how these boards will tie in with the steering products Advanced Roadmaps and Align? I see this as a common theme with Atlassian lately with the same concern for Next-Gen projects and so on. It's something I will bring up in another article though.
      Introducing Forms

      It is interesting to see that forms are moving out from Jira Service Management as a way to create input and display forms. I think this will probably show up in Next-gen projects down the road as well. It is a good change and I think it makes perfect sense to make input and output presentation in this way.
      Background color

      Adding a background color to your project will not make or break the customers' appreciation of it, but it is a nice icing on the cake. I don't see what the point is to restrict to standard colors when you could just add a color option to the surrounding text as well and let users add whatever color they want. I foresee images coming soon as well, just as for Trello.
      So why do you want this?
      Adding business teams into Jira are a good thing. Earlier it has been a bit difficult to convince them to join, but I think that the List View will be a big selling point to be honest. Maybe even the Calendar, even if I am not seeing it at the moment.
      Having the business teams in Jira means that you can bring in a lot of processes that currently live outside of Jira. This will allow easy management of early project/program planning, procurement processes, staffing, legal and security management and not to mention brick and mortar projects such as store building.
      This is of course the first release of Jira Work Management and it will very likely evolve quite a bit in the coming year or so. For now, it is also free for all Jira owners, so once you get access to it, I suggest you take some time to check it out and see what it can do for you and your organization.
      You can sign up on the waiting list here:

    • Atlassian acquire Mindville - asset and configuration management from Sweden

      Atlassian and Mindville announced on thursday that Atlassian has acquired Mindville.  This means that Atlassian acquire Mindville's asset and configuration management product Insight, which strengthen their psoition against competitors like ServiceNow.
      The CEO of Mindville Tommy Nordahl is well known to us in Stockholm who have participated in the Atlassian Usergroup events that I ran for two years. For many he is Riada, the company he started many years ago as the Atlassian company number one in Stockholm (and sweden?). Lately he has focused more on the asset and configuration managament product Insight and I am not surprised that Atlassian now have aquired it.
      Atlassian and ServiceNow are both gearing up for a battle. Since ServiceNow are strong in the asset and configuration management it makes sense that Atlassian want to stregthen their portfolio in their area.  With more than 1700 customers already and Atlassian now adding resources I think we will see the cloud adaptation speed up a lot.
      If you have not looked at Insight before, then I suggest you do. Not only is it looking great and is easy to work with, it is also powerful and a very useful addition to your support organization. Using Insight alongside Jira Service Desk and Confluence is probably the most powerful way to manage incidents in your organization. The fact that you can directly connect it to your development and opertions team who already work in Jira make it even more powerful.
      I just want to say congratulation to Tommy and his amazing team for this accomplishment. To Atlassian I can only say good job on this acquisition. It will take you another step closer to being the natural choice for mid sized and large organizations, just as you already are the natural choice for small companies and all development teams today.
    • Love 1

    User Feedback

    Create an account or sign in to leave a review

    You need to be a member in order to leave a review

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

    There are no reviews to display.

  • Create New...