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 »

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 »

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   Give context to your teams Roadmapping has always been a dirty word in agile circles. In some ways it feels inherently waterfall to plan a 6, 12, or 18 month roadmap for the team. I'm here to tell you that roadmapping is a good thing. It gives the organization context and shared direction

Continue reading »

The all-new control chart makes it easy for teams to better understand their delivery pipeline to help optimize their process. It highlights differences in estimate and delivery time so that the team can continually make better estimates and deliver more reliably. Today we're going to explore how it can help your team, but if you haven't read the overview article on new control chart yet, start there. 1. Dig into your data! The new control chart is interactive, which makes it easier to dig into

Continue reading »