Jira Workflows power effective teamwork
Plan, track, and release great software with workflows designed to fit every initiative or project. Start with a template, or create a custom one and get your team working more efficiently and transparently.
That's just the beginning. What can your company manage with a Jira workflow?
- Asset management workflow
- Change management workflow
- Procurement workflow
- Problem workflow
- Risk mangement workflow
- Helpdesk workflow
- Bug tracking workflow
- Incident workflow
- ITIL workflow
- Ticket workflow
- Code review workflow
- Release management workflow
- Requirements management
- Test Case management
- DevOps workflow
Methodologies to guide
Perhaps the most famous of the Agile methodologies, Scrum encourages team collaboration by focusing on a single goal at a time and delivering incrementally.
A standard Scrum process begins with the creation of a product backlog, which in simple terms, is really the team's to-do list. Each team member plans how much of the backlog he or she can complete in a given timeframe (the "Sprint," typically two weeks). The Sprint begins and team builds the product. At the end of each Sprint, the team determines what work to tackle next based on the outcome of the previous Sprint. And the process repeats.
Unlike Scrum, Kanban focuses on status rather than due dates. Each item of work progresses through pre-defined project stages so teams can easily see what work is in-progress and identify roadblocks.
A basic kanban board is a three-step workflow: To Do, In Progress, and Done. But depending on the unique requirements and composition of your team, additional workflow stages can be mapped in.
Agile teams often adopt mixed methodologies and that's where Jira's customizability becomes so powerful. For example, scrumban takes fixed-length sprints and roles from scrum and the focus on WIP (work in progress) limits and cycle time from kanban. Or kanplan, which is kanban with a backlog.
Jira Epics and Stories
While not a methodology per se, epics and stories are Agile artifacts to classify amount of work. An epic captures a large body of work that can be broken down into a number of smaller tasks.
Those smaller tasks, called user stories, are an effective way to write product backlog items. When utilized, they are often written from the point of view of an end users.
Or, create your own customized workflow
Many teams discover that strictly adhering to Scrum or Kanban doesn't work for their team, and that's where Jira's new project type come in.
The concept behind Jira's new board is for teams to start simple and pull in various elements - whether it be additional stages to the workflow, a Sprint, a Backlog, or a work-in-progress limit - as needed.
Nothing is set in stone so these additional features can be turned off in a simple click, allowing teams to experiment, risk-free, with various workflow styles.
Using Jira Software to manage workflows
Simple workflow building blocks in Jira Software allows organizations to start simple and customize as they grow.
Statuses show where a piece of work is within a workflow. Assignees are responsible party for a piece of work.
Transitions are links between statuses that allow work to move from one status to another.
Resolutions explain why a piece of work was closed, whether it was canceled, resolved, or escalated.
Connect your entire workflow with Jira automation
Seamlessly connect your third-party tools to any Jira workflow with automation. Whether your team is using Bitbucket, Slack, or any other tool, automation keeps Jira up to date so you don't have to. Learn more