Archives for Dan Radigan

JIRA Agile 6.6 – Now available

It's no secret that better planning means faster and higher quality deliverables for any agile team. Our newest release of JIRA Agile provides richer data during the planning process by making agile cards more customizable than ever before. Now teams can display the data that is important to them. Additionally, we've made improvements that will allow agile teams to better optimize their flow of work across the team. With JIRA Agile 6.6 it’s now easier than ever to pre-assign work to specialists,

Continue reading »

5 tips for great code reviews

In almost every organization, team members collaborate to get work done. Software teams typically transition issues between people for different functions like code development, code review, and testing (even if they are all on the same team). When transitioning an issue from one team member to another it’s important to minimize the amount of ramp up required for the receiver to fully understand the issue. Transferring issues can be extremely expensive as it requires time from not only one,

Continue reading »

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 »