Archives for Dan Radigan

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 »

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 »

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 »