{"id":2269,"date":"2015-08-12T16:53:18","date_gmt":"2015-08-12T15:53:18","guid":{"rendered":"http:\/\/blog.davidkeen.com\/?p=2269"},"modified":"2025-10-23T10:17:54","modified_gmt":"2025-10-22T23:47:54","slug":"a-kanban-and-scrum-workflow-with-jira-agile","status":"publish","type":"post","link":"https:\/\/davidkeen.com\/blog\/2015\/08\/a-kanban-and-scrum-workflow-with-jira-agile\/","title":{"rendered":"A Kanban and Scrum workflow with JIRA Agile"},"content":{"rendered":"\n

JIRA Agile<\/a> has come a long way from the days of the GreenHopper plugin. It’s now pretty well integrated into JIRA and I’ve found it great for running an Agile workflow.<\/p>\n\n\n\n

JIRA Agile supports both Scrum and Kanban boards so you can manage your tickets using whichever methodology you prefer but what if different parts of your team want or need to work in different ways? With JIRA Agile you can have multiple boards so tickets flow through different teams in different ways.<\/p>\n\n\n\n

Maybe your developers are using Scrum with week long sprints. They want a standard Scrum board where they can take tickets from the To Do<\/em> column, move them into In Progress<\/em> when work starts and then to Done<\/em> when complete.<\/p>\n\n\n\n

But perhaps weekly sprints don’t really suit the planning workflow of your product team. They would prefer to use a Kanban approach of managing their work in progress.<\/p>\n\n\n\n

Ideally we want to be able to create tickets on the product team’s board and move them into the developers’ board when they are at a suitable stage of readiness. By mapping statuses you can have a kind of combined Kanban\/Scrum process.<\/p>\n\n\n\n

Product Board<\/h3>\n\n\n\n

This is a Kanban board with 5 columns: Backlog<\/em>, Requirements<\/em>, Ready for development<\/em>, Test<\/em> and Ready for release<\/em>. Each column is mapped to the following respective Statuses: IDEA<\/em>, REQUIREMENTS<\/em>, TO DO<\/em>, RESOLVED<\/em> and CLOSED<\/em>. The IN PROGRESS<\/em> status is left unmapped so tickets in this state will not show up on the board.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

<\/p>\n\n\n\n

The product team can work on tickets in the Backlog<\/em> and Requirements<\/em> phases before moving them to the Ready for development<\/em> column which will cause them to show up in the Development Scrum board (as we will see).<\/p>\n\n\n\n

Once the developers have completed a ticket it can be moved into the RESOLVED<\/em> state and it will then reappear on the Product board in the Test<\/em> column. When the product owner is happy that the requirements have been met it can be moved to the Ready for release<\/em> column.<\/p>\n\n\n\n

Development Board<\/h3>\n\n\n\n

This is a Scrum board with the standard three columns: To Do<\/em>, In Progress<\/em> and Done<\/em>. Some tickets may not need to be sent back to product for review and can be closed directly so the Done<\/em> column has both RESOLVED<\/em> and CLOSED<\/em> statuses.<\/p>\n\n\n\n

\"Scrum<\/a>
Scrum development board<\/figcaption><\/figure>\n\n\n\n

When planning a sprint, the Development board will only show those tickets with a status of TO DO<\/em> in the backlog. Tickets that are still being prepared by the product team (IDEA<\/em> and REQUIREMENTS<\/em>) are left unmapped so won’t show up until they are ready to be scheduled into a sprint. Once a ticket is moved into the RESOLVED<\/em> state it will reappear on the Product board.<\/p>\n\n\n\n

By combining Scrum and Kanban boards you can create a hybrid workflow that better suits the needs of the people actually working on the tickets. You don’t need to force everyone into a single way of working.<\/p>\n","protected":false},"excerpt":{"rendered":"

JIRA Agile has come a long way from the days of the GreenHopper plugin. It’s now pretty well integrated into JIRA and I’ve found it great for running an Agile workflow. JIRA Agile supports both Scrum and Kanban boards so you can manage your tickets using whichever methodology you prefer but what if different parts […]<\/p>\n","protected":false},"author":1,"featured_media":2623,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[25],"tags":[27],"class_list":["post-2269","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dev","tag-featured"],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/davidkeen.com\/blog\/wp-content\/uploads\/2015\/08\/pexels-photo-394377.jpeg?fit=1280%2C719&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/posts\/2269","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/comments?post=2269"}],"version-history":[{"count":15,"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/posts\/2269\/revisions"}],"predecessor-version":[{"id":2849,"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/posts\/2269\/revisions\/2849"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/media\/2623"}],"wp:attachment":[{"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/media?parent=2269"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/categories?post=2269"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/davidkeen.com\/blog\/wp-json\/wp\/v2\/tags?post=2269"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}