Archives for Dan Radigan

As teams transition to an agile development workflow, many struggle with how to adapt traditional testing methods in an agile culture. Teams are often forced to trade off the quality of their product against the speed of shipping. At Atlassian, we've pioneered a different approach, known as Quality Assistance. Instead of creating a separate test team to hold responsibility for quality, a small team of Quality Assistance engineers evangelizes and coaches sustainable testing methods across the

Continue reading »

JIRA 6.3: Untangle Development

Software teams can now easily implement development best practices and world-class project tracking at the same time. JIRA 6.3 is more tightly integrated with Stash and Bitbucket for teams using Git and Crucible for teams using Subversion, Perforce, and Mercurial. JIRA automatically updates issues the moment development of an issue is complete. We've also enhanced reporting in JIRA Agile to give the entire team an end to end view of the project allowing for more data-driven decisions. Combined with

Continue reading »

At the heart of every software team is a vibrant culture around creation, organization, and delivery of work. All types of work – be it new features, bugs, spikes… are called 'issues' inside of JIRA. Issues provide a flexible way to organize and distribute work across the team so that everyone remains productive and the whole organization runs at a smooth cadence. This article will focus on three key mistakes teams make and how to correct them when using issues to track work. From feature

Continue reading »

I've had a number of people ask me lately, “how can I use priority to better manage issues inside of JIRA?” Throughout my career in software different teams have used priority to communicate different processes inside of their issue tracking systems. Failure to be crisp about the definition of priority makes work more confusing to get done. Allow me to set a few global definitions to frame our discussion: Priority – The relative importance of an issue in relation to other issues

Continue reading »

Today I'm excited to announce the availability of the new release burndown chart inside of JIRA Agile labs. The release burndown chart gives the team clear insight into the evolution of a release throughout its life cycle. It's every scrum software team's goal to deliver new features and optimizations to their customer base. Many software teams bucket chunks of work for a release into a version inside of JIRA. A version is a distinct piece of software that is shipped to customers. During development,

Continue reading »

Task management with Confluence and JIRA

Hey! Dan from the JIRA team here. I'd like to take a few moments to share how task management in Confluence relates to JIRA. Both products enable teams to collaborate using task management and distribution, but Confluence works well for smaller business teams whereas JIRA excels for larger projects and software teams. Getting from here to goal People rally around goals. For goals to be actionable we need to break them down into a set of tasks that bridge the gap from where we are to where we

Continue reading »