Browse Agile
Filters
Inside Atlassian: a product manager and a dev manager walk into a planning meeting…
Product planning meetings are one of the most important meetings in a product’s lifecycle so we decided to take you inside a product planning meeting at Atlassian by filming the latest Portfolio for Jira planning meeting (filming the planning meeting of a planning tool seemed only fitting). These product planning meetings tend to happen quarterly and last about four hours (don’t worry – we time-lapsed it for you of course!).
Examples of capturing customer feedback for agile development
Customer feedback in agile development is a three-step process of gathering, documenting, and prioritizing. Here are examples from our product managers.
Inside Atlassian: designing software with the customer at heart
I decided to sit down with different Jira designers to learn how they reimagined Jira as Jira Software, Jira Core, and Jira Service desk from a design perspective. The stories were endless, but three things kept popping up in each designer’s story: design spikes, live data prototyping, and a stellar feedback collector.
How the agile manifesto rescued The Daily Telegraph’s service desk
The Daily Telegraph’s Director of Service Delivery, was facing a seemingly impossible task: bring service delivery back in-house, and do it within three months. Learn how they applied the agile manifesto and improved customer satisfaction by 140%.
How to prioritize features using NPS®
In case you’re unfamiliar, NPS stands for Net Promoter Score. NPS is a loyalty metric that quantifies how customers feel about your product. Let’s take a look at how NPS can be used not just as a metric, but also as a powerful tool to help your software team prioritize features.
Who’s who in agile teams?
Agile teams are structurally different than their waterfall counterparts. Agile teams focus on the team itself, whereas waterfall teams often follow the structure of the organization. As I was learning scrum, one of the questions that kept coming to mind was, “How do development managers and scrum masters share responsibilities in the team?” Let’s explore the answer to this question.
Open letter from an @ignored test
Dear developer, I’ve been wanting to talk to you for a while now, but words don’t always come easy. We’ve had some really fun times together. I still remember the first time I warned you about a minor bug in your code, and how happy you were for having me in your life! Do you remember it? I also remember the first time you refactored me to make me more efficient and how well-written I felt afterwards… ah, great times!
From rough to real-time: Klarna’s planning revolution with Portfolio for Jira
Klarna simplifies buying by providing a streamlined solution for all payment types, so that businesses can give their customers the simplest buying experience. They believe that the easier it is for people to shop, the more you sell. But Klarna’s planning process wasn’t as simple as its buying process. They needed a real-time planning solution […]
Jira Software just got easier to navigate (and more fun, too)
The new customizable sidebar brings projects and your team to center stage in Jira Software. Read on for our list of conventional (and not-so-conventional) ways to use it.
Introducing Jira Software: the #1 software development tool used by agile teams
Today we’re thrilled to announce the next branch in Jira’s evolution: Jira Software. This new branch was created specifically for software teams, the customers who made Jira great from the beginning.
Inside Atlassian: using scrum to balance operations and innovation on the support team
One of Atlassian’s core values is “Be the change you seek.” For Atlassian support, it means innovation can’t be put aside, despite very busy schedules. In other words, obstacles to change can’t stand in the way forever. Read about some of the successes and failures of the Atlassian support team’s efforts to innovate, and how scrum keeps their eyes on the ball.
How to make better decisions as a software team
Sometimes, it’s easier to make a decision asynchronously. And for that, there’s no place better than Confluence. The Decisions Blueprint provides a simple, repeatable process for making decisions asynchronously with your team and recording them forever in Confluence. And once everything’s in Confluence, you—and anyone on your team—can reference it later.
How to build a release planning page in Confluence
Every product release requires a lot of hard work and a ton of coordination between individuals and teams. In some places, a release coordinator takes this on as a full time job, while in others, a developer, product manager, or project manager might be in charge of release planning. At Atlassian, we use Confluence to collect and organize […]
How to create sprint retrospective and demo pages (like a BOSS) with Confluence
As software makers, we rely heavily on sprint retrospectives and demos to learn more about what’s going on with our team and our products. Read on to see how to build pages that record what you’ve learned and let you share it outside your team.
How to create product requirements using Confluence
We’ve written quite a bit about the conundrum of writing requirements in an agile environment. The most important takeaway is: the best way to kick-off your software projects is to build a shared understanding amongst your team. At Atlassian we find the best way to do this is to create a collaborative product requirement to hash […]