Perhaps the ~500 largest companies are the exact worst place to assess the impact of disruption.

An interesting counter narrative. I'd need to sit down with the purveyors of the corporate mortality story to see how each is counting.

Zing!

who needs exco

hey tanguy this is interessting

Hi Philipp!

call these guys tongiht to books

forge

We've had this vision but not conviction in messaging it. Will we as part of economy, platform?

Let's get together on this and build a masterclass. You, Mike Cannon-Brookes (founder), me, 3 coaches and customers.

Rather than the typical Twitter rant that always ends with an audience split of "It is a tool/you are using it right/wrong" let's end this one with real collaboration, real people in a room showing the world how to be better eng leaders and how to use the tool in a way that is helpful. Cutting rope with a Zoom call is a tough task but a razor blade, used correctly is powerful.

We'd agree.

A well setup Jira connects to the development pipeline to show you what is in staging, what deployed and it can connect to tools that tell you how an experiment is doing in production. e.g. your Launch Darkly experiment status auto populates the related issue.

A well setup Jira will automatically inform a dependent team when a dependent service has been deployed so they can begin work. That doesn't mean those teams should never speak. Perhaps the automation of that communication makes it too easy to keep the headphones on and head down. In that case, we need to address the cultural issue of, "I don't want to be interrupted by meetings and people" aspect of development. Something the manifesto addresses well as you point out.

You can see this information on the board without even clicking.

The Jira team would agree. I'll look into how we might make integrations with live collab tooling more accessible.

At Atlassian we often used large TVs with the board on the wall as a tool during standups.

Now with remote work we do the same but with Zoom.

There should be no such thing as the "Jira Methodology". We try to be decidedly unopinionated, allowing teams to design he way they prefer to work.

In the past and in our server editions we made this harder than it should be.

In the cloud version of the product we have created team managed projects that empower the teams to have more autonomy re how they design their work. This creates some ruckus in companies where the Jira admin/PGM?eng leader might have very/overly prescriptive controls. We believe that while a less centrally controlled way of working can be frustrating in companies like this it is necessary to prevent an overwrought way of working form continuing or emerging.

This is what it is. I can annotate anything on the web and share with my team.

Preach!

What are the causes of this effect?

How did this come about?

What was caused in the short term (3.5 years vs long term 4+here?

Has any other country had a similar issue?

Why were we so much worse off than other countries in this regard?

This seems a cultural barrier that is somewhat more difficult to address in America

How did Europe handle this issue of privacy?

Is there any credence to claims that our population contains more co-morbidities than other nations? e.g. Obesity

Is there credence to the claims that perverse incentives have driven aspects of the medical services in the US to attribute deaths in a materially different way than other countries?

What you see in Jira is largely up to you. Tune it to suit your work. One thing that Jira cloud makes really easy is stripping down the capabilities.

• If you don't want sprints, one click it off. All the Agile, with more agility/ Next-gen projects let you design the way your team wants to work. Teams can begin with a lightweight approach and then progressively add more features like backlogs, estimations, sprints, and more. All in a single click.

• Want to add a roadmap based on the epic and issues already in Jira, one-click it on.

• Want to have the simplest issue view? Design the way your dev team wants to work in Jira by stripping down the fields. The Jira issue functions as the core unit of work in the software industry, connecting work across tools and teams of all kinds. In the new issue design, it’s now easier to understand what’s most important and how to take action that will move work forward. And if you want to drop fields, go into the drag and drop field editor and strip the view down to the minimum. ![]

• Want a real simple board? Build-your-own-boards: Customize your own workflow, issue types, and fields for the board you want and need. All without needing an administrator’s help or putting another project’s customizations at risk.

More Info: https://support.atlassian.com/jira-software-cloud/docs/enable-agile-features-in-next-gen-projects/

We spoke with Justin about his setup with his Jira admin. I think some tweaks we uncovered in the way Jira was running will make a big difference

The Jira Software you needed in 2002 isn’t the Jira Software you need today. The workflows you built in 2010 aren’t the workflows you need today. And the permissions model we built for early adopters of Jira Software isn’t the right model for all the teams using Jira Software in your company today. Modern software team building for the cloud work differently than the teams of the past.

That’s why our teams have totally reimagined the product to focus on making it easier to use and more powerful for modern software teams. In Jira Cloud software teams have more autonomy in the way they work while still delivering the power Jira administrators expect.

Make Jira work for You! Integrations automatically sync with the Jira issue so that everyone knows what’s going on without having to update Jira manually.

e.g. In the dev panel of the Jira issue and in the board view you can see live updates from Git tools, feature flagging tool and more. These updates flow into Jira based on what happens in 3rd party tools and the information from these tools can be used to power automation, workflows and reporting and even JQL.

For developers and the broader team that can see what is happening without having to click into another tool to look for it. e.g. What is the status of. Launch Darkly Feature Flag? You can see it in the dev panel.

More Here: https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/

This works with Bitbucket, GitHub and GitLab and we have lot's of partners in the ecosystem you can plug in.

We knows devs hate the interruptions. Here are a few features that help.

Atlassian in VS Code lets you update Jira and work in Bitbucket without ever leaving VS Code.

• Your Work in BB let's you interact with Jira right from the Repo so Pull Request and Issues assigned to you come to you instead of you going to Jira looking for them. Best of all, updates you make in Git flow though to Jira Automatically.

• Automation for Jira can make Jira update itself based on work done in 3rd party tools.

• Slack integrations can ping developers about pull requests and code reviews etc. when it is important to cut through the noise and get ^&*( done.

Beautiful! We see that value as well and make sure it shows up on the issues and in the board views so everyone can see at a glance what's happening across the pipelines.

We're here with you too and we just announced a pretty major partnership that will make it easier for more people to use Slack and Atlassian. That means our integrations are going to get even better. Here's the Jira one.

We'll help you & your colleagues stay up to date with everything happening in your Bitbucket. You'll always know:

If that pull request got approved When the build finished and if it succeeded or failed When a new branch is added to a repository Much more Even better, some notifications allow you or your colleagues to take an action right from a notification:

Nudge outstanding reviewers on your pull requests Reply when someone makes a new comment on your issue tracker, a commit, or pull request Merge that pull request now that it's approved Re-run a failed Pipelines build

We agree. Out-of-the-box filters in Jira Cloud generate a custom view of your next-gen board in seconds, with out-of-the-box filters by issue owner, epic, label, and more. No JQL required (although it’s still under the hood if and when you need it).

We think there is value in seeing a board but agree that reducing the manual ^%&*&^%& devs need to do to update status about their work is important. We want to make the value of using Jira greater than the effort of using Jira for devs. Here's a few things we do.

• Devs work in their editor and update Jira and BB from there.
• If they are in Bitbucket, they interacts with Jira from BB directly.
• Automation updates Jira for the devs based on work they do in code.

Sounds like a cool process. We do some similar things. Jira Service Desk links customer support right to devs so devs can see and interact with issues.

And, we recently added Halp to the portfolio to create a way for people in Slack to get support. Customers are one great use case for that.

I'm @seanjregan I work on Jira. Thanks for checking out some of my thoughts on this article. (Hi Rocco!)

Usually we don't engage in the annual articles by competitors that pin SW industry failures on Jira but in this case it seems a lot of what we've been shipping in Jira Cloud is perhaps still unknown. (And, this annotation tool seemed well suited to this sort of dialog.)

Much respect to the LinearB team. Anyone working to make SW Development better is good in our book. Great products will stand out on their merits among the dev community.

While riding the Jira coat-tails via blog titles is a common approach to generating traffic, I want to also note that Atlassian is very open and we're happy to partner with any vendor that can make dev life smoother.

We partner with GitHub and GitLab as an example. If they can do a better job or a customer prefers their tools then it is on us to 1.) Support them and 2.) continue to up our game.

Caveat: My team and I met with Justin and his team prior to this article's publication. Out of respect to Justin, I will not share details of our conversation other than to say that we had a great chat and I'm optimistic we can improve things based on his feedback and based on some tips we shared.

Business leaders don't traditionally buy Jira. Development teams typically do via Credit Cards.

Jira is most often introduced in a company by a developer or dev manager, founder, devs, or PMs. As use grows it is common for PGM to get involved.

When usage grows it is important for the Dev team to work with the PGMs to make sure the workflows are suited to the work. Just as you update your wardrobe, weed your garden and change your jacket with the season, Jira should change to support the best way your team wants to work.

In short, if a Jira admin is abusing your dev team with ornate, un-helpful process we want that to stop and are shipping lots of features to put more autonomy in the hands of developers.

• Next Gen Boards are a simple way to run a Kanban style workflow for Dev and can be setup to be as easy as Trello.
• Automation in Jira updates Jira based on work happening in Git Automatically so devs don't need to. What happens in Git shows up in Jira. *Roadmaps in Jira automatically update based on work happening in Jira so devs don't need to be interrupted to answer questions about what is shipping when all day.
• Project level permissions allows devs to design their own ways of working in Jira without impacting other project.

We agree. One way we see Jira helping here is the Roadmaps View. This turns all the work happening in Jira into a visual of the work that can be shared with a single click.

What's best is that it is based on the work being done in Jira. So business leaders and dev managers and dependent teals can see what's happening without Dev managers having to chase up hundreds of issues and updates from devs.

[](https://www.atlassian.com/blog/jira-software/roadmaps-in-jira

)

That's an expensive meeting.

Agree- This one made my life so much easier!

There is so much value ini your company that can be templatized. Admins can scale effective ways of working easily.

This was was exciting and disappointing. We knew we were going to bring the house down well in advance.

We had almost 30k registrations and around 1/2 showed up. That's insane for a webinar. Though best efforts were we broke our webinar provider at that scale. Thankfully the teams on both sides were standing by ready and the impacts were not widespread.

For all the business, PR, Finance, Support teams who want to know what happened, what we are doing different etc. this is a killer feature.

When things get weird, this dash is amazing.

One customer told me it would take him 25 years to work through the backlog of change requests at his company. That sounds dire.

This can help a lot. All the low risk, high volume stuff can get approved automatically but with a record of what was done via the Jira issues.

Yup- We've done a ton of work for MS customers so that Jira makes life better for them. Jira and BB show up inside of VSCode when you connect them. It got quite popular quite quickly.

https://marketplace.visualstudio.com/items?itemName=Atlassian.atlascode

We have a saying internally

We want to make the value of using Jira greater than the effort of using Jira for all, especially developers. This is one of the features that springs from that.

Live Status is the other. You can make Jira update itself! In terms of project management tools, that's pretty slick. One customer called it a , "Self-licking ice cream cone". Not sure I'd use those terms but I get the concept I think....

This one is literally a Dinner Saver. Don't stay at the office trying to hustle a roadmap update together. Let Jira and Confluence do it.

Admin life/Dev Manager Life just got easier here.

We're glad to ship this and encouraged every ShipIt to see more and more design and eng teams building for this.

The word "Scalable" is overused in tech. That said, if you are an admin in a large company this is an appropriate use of more "scaleable".

For those highly regulated firms this is a big deal. Glad it is there for them.

No doubt they will!

Server or Cloud- We rely on our partners for so much of our success and the success of our customers. Thank you!

This one is great.

1.) Some customers want us to ship more faster, more faster, more faster. So we do. But....

2.) Some customers don't want to introduce so much change into mission critical processes So, they want release tracks. This helps them with change management.

Given that some companies run space ship launches as workflows in Jira. I can appreciate both sides of this one.

This lets teams choose to use a super flexible rapid collab model with Trello or a more structured model with Jira without losing the ability for the leadership to plan and track work across tools. Let your teams design their own ways of working. We'll help make sure it is coordinated.

Objectives and Key Results.

Here's a template to try.

https://www.atlassian.com/software/confluence/templates/okrs

For sure. This one is popular with our larger and more security focused customers.

It is always a balance. We could ship a premium tier fast but unless we pack a lot fo value into it it isn't the right move.

Automation now packs a ton of value into JSD so now we're ready to let customers have it.

Yup! This will help our customers build and use more apps on the cloud service because we make it easier for them om the back end.

I'm sure you could get this much higher, especially if you use Your Work and or Slack.

Fair point! We agree. 1.) Notification preferences help. 2.) Your work in Bitbucket will help.

Bonus: End users can config this so admins don't need to doi it.

You guessed correctly. We're making sure we have a world class cloud with the security, management and scalability our biggest customers expect. We saw a recent survey from Bank Of America about cloud migrations. They surveyed Atlassian customers and almost 50% were planning a migration in the next 12 months. We're making sure we're ready.

I'll be very happy to get back to Las Vegas, nothing replaces the face time with customers and partners.

Covid-19 has become a digital transformation driver everywhere. It before those words were vague corpratisms, the last few weeks has made them all too real.

Love your summary! It is the fastest way to get everything that happened at Summit.

gchvnbmn