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 »

We are happy to announce new Atlassian University lessons for Confluence 5.5 and JIRA Agile 6.5! In the last few versions we've released a lot of handy features you may have missed. For example, did you know that you can create JIRA issues directly from a table in Confluence? Or that you can easily move issues from the backlog to a sprint by using the right click menu? The Confluence 5.5 lessons include: Blueprints Production Requirements Blueprint (Video) JIRA Integrations

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 »

Deliver well: requirements to deployment

This article is part of a blog series! Part Title 1 Yes Virginia, even agile teams roadmap! 2 Moving from roadmaps to requirements 3 Deliver well: requirements to deployment   Prioritizing requirements using epics and versions Now that we have all of the requirements as user stories for a particular feature inside of JIRA, it's time to start work. When we did the import of issues from Confluence, we linked each user

Continue reading »

This article is part of a blog series! Part Title 1 Yes Virginia, even agile teams roadmap! 2 Moving from roadmaps to requirements 3 Deliver well: requirements to deployment   If you're still with me after my agile heresy, Yes Virginia, even agile teams roadmap!, then I'd like to move down to the next level of the project planning process: requirements. In our roadmap, features are organized into themes that represent a significant enhancement to one of our

Continue reading »