Browse the blog
Filters
Kanplan: where your backlog meets kanban
There’s no silver bullet when it comes to picking an agile framework for your agile team. Whether you use kanban, scrum, or a combination of the two, like scrumban, agile is a team process. Every team needs to figure out which framework works best as a foundation for how to plan, track, and release great software.
Trellisheets: How we spin up CSS for Trello sites with ease
We’ve talked about our CSS a lot in the past. We did a State of the Trello CSS and published a guide for writing CSS. We’ve wrapped up everything we’ve learned into Trellisheets, a public repo for all things CSS at Trello. What’s in the project? Our core CSS files. We use these on multiple sites to give them […]
Super-powered continuous delivery with Git
Developing as a team can be messy. You’re trying to understand which pieces of code everyone is working on, trying to make sure changes don’t conflict, trying to find defects before your customers do, and trying to keep everyone connected with the project up to date on how things are progressing. As it turns out, each of those problems is addressed by either Git branching or continuous delivery.
Inside Atlassian: Jira workflows for tracking blog projects
Chances are, your marketing team manages blog projects on spreadsheets. You probably track who is working on it, what state it’s in, when it’s going to be published, what it’s about, how it fits into larger marketing campaigns… And that’s just the stuff you’re concerned with before it’s published. It’ll come as no surprise that Atlassian’s marketing team uses Jira Core, Confluence, and Hipchat to keep our blogs running smoothly. So today I’m going to get all meta with a blog about how we use Jira Core, including some example workflows, to track our blogs.
Getting started with Jira Service Desk’s employee self-service and customer satisfaction reports
The right metrics aren’t just a “nice to have” – they’re a “must have.” Now, you can measure both employee self-service and customer satisfaction. By providing an easy and fast way for customers to get answers – like taking advantage of a knowledge base – customers are happier and agents are more productive. If you deliver a better self-service experience, you’ll likely see your customer satisfaction (CSAT) scores improve. Over time, your IT team will benefit from seeing these improvements, which in turn will improve team productivity. (Not to mention job satisfaction.)
4 ways to enhance product documentation for mobile first
If your company has made the switch to a mobile-first strategy, make sure you don’t leave your product documentation behind. Your customers are increasingly accessing product information on their phones, making a seamless mobile experience more important than ever. These four tips will help give your customers a great mobile experience. Plus, check out the Instant Websites for Confluence Cloud add-on which turns any Confluence space (such as your documentation) into a super-fast, static website that looks beautiful on mobile.
Why agile isn’t agile without continuous delivery
Continuous delivery is both part of the agile recipe and a great revealer of inefficiencies. Moreover, in order to reap the benefits of agile, you need to be agile through all phases of the software development lifecycle. Iterative planning and development don’t count for much if your user stories and bug fixes languish in a repository for weeks on end before stakeholders and customers ever get a look at them.
What designers, game developers, and architects need to know about Git LFS
It’s a known issue that Git doesn’t play nicely with large files, and it’s not just developers who struggle with large files and version control. Native Git’s limitations make it challenging for team members like designers, tech writes, sys admins, and build engineers to work closely with developers. That’s why we decided to collaborate with GitHub on building a standard for large file support. Here’s what’s happened since.
How Hipchat and Statuspage help companies manage incidents
?! There’s a hiccup with your service. You jump into incident-management mode. Your users, who are already tweeting and sending support tickets, need to know what’s up. Your team needs to come together to diagnose and fix the issue – FAST. This is the story of two Hipchat customers, and how they use our integration with Statuspage to manage incidents.
Inside Atlassian: how our site reliability engineers do incident management
“Ohhhhh $#!τ. We broke Confluence.” In one of our first Confluence Cloud releases in 2016, we broke our users’ ability to edit pages. As the head of Atlassian’s site reliability engineering group, this kind of thing falls right into my wheelhouse. In this post, I’ll walk you through how we responded to the situation to get Confluence working again. I’ll give an insider’s view of our incident management process, as well as how we’ve configured Atlassian tools to support this work.
Fighting the perfect product
One of our main goals as product managers as we move from casting the vision to executing is to de-pressurize the room – no one on the team should waste energy sweating over the perfect product. Instead, focus the team on shipping the best first version in order to get insight. Then use that feedback as a compass for future versions.
From Asana to Jira Software: one customer’s journey towards agile development
Switch Communications is a San Francisco based company whose mission is to provide cloud-based business communications systems for the fastest growing, most innovative companies in the world. Switch.co recently found that their project management software wasn’t fully supporting their software development process. The most glaring pain point was bug reporting, and they needed a single […]
Helpful Trello tips for event planners
One of the biggest pain points for those planning events is managing all of your event to-dos in one place. In the old days, Type-A event planners would resort to an Excel spreadsheet, or a wall filled with Post-it Notes ordered chronologically.
Bumpversion is automation for semantic versioning
Semantic versioning (or just semver) is a specification for communicating about changes in code from one version to the next. It targets the problem of dependency hell. Dependency hell is where you are when version lock and/or version promiscuity prevent you from easily and safely moving your project forward. In short, semver specifies the first […]
Inside Atlassian: how IT & SRE use ChatOps to run incident management
Any team that slings code for a living deals with service issues. They know all too well the hated red alert… the dreaded text in the middle of the night… the loathsome ping from a coworker telling them that $#!π just hit the fan. But what separates good services from great services is the ability to recover swiftly with minimal affect on users. And a big factor in swift recovery is ChatOps.