At Atlassian, the key to faster, higher quality releases is a strong relationship between our dev and ops teams, and the right tools and processes in place to support them.
DevOps and Atlassian
At some major big box retailers, really heavy items have “team lift” stickers on them to indicate when
several employees need to help move the items from shelf to shopping cart. “Team lift” is actually a perfect analogy for the entire DevOps methodology, since DevOps isn’t any single person’s job—it’s everyone’s job. At Atlassian, we use our own products to understand our various use cases, and provide additional testing before we release them to our customers. In short, we dogfood our own products. In this ebook, we’ll cover each step in detail, and exactly how we use each Atlassian solution. For now, let’s start with our process, which looks a bit like a hot tasty pretzel.
Building Products, DevOps Style
Let’s say your engineering team has gone Agile. They work in sprints, collaborate, and are building a lot of great features. But there’s just one catch: you still have to wait for the release train to leave the station, and customers aren’t getting value fast enough. We’ll show you our best practices for building products, DevOps style. Let’s start with feedback; because no matter the product, your success is solely based on your users. HOW TO GATHER FEEDBACK—AND USE IT TO SHAPE AND BUILD FEATURES We’ve learned over the years that the easiest way to make our product better is to listen to the people that use it. You can collect feedback from just about every source imaginable.