Sometimes one board per project just isn't enough! Why should development teams get all the fun?! This presentation explores how teams can use Kanban and Scrum boards for any part of your development cycle - from idea to deployment and beyond!
Unlocking the Future of AI Agents with Large Language Models
Agile boards in Jira Are For Everyone
1. Agile Boards in Jira
Are For Everyone
Using Kanban and Scrum Boards
Together for Every Part of Your Process
By Chris Nicosia
Product Manager & Atlassian Expert
at Modus Create
origdiva
2. Product Development
◈ Customer Centric Solutions
◈ Feature / Value throughput
◈ Building Competitive Advantage
◈ New Product Launch & Scale
Customer Experience
◈ Design Thinking
◈ User Research
◈ Evidence Based Design
◈ Usability & User Testing
Digital
Transformation
Agile Transformation
◈ Kanban & Scrum
◈ Devops & Automation
◈ Automation
◈ Cloud Native
Technology Partners
◈ Atlassian
◈ AWS
◈ GitHub
◈ Ionic Framework
3. WHAT YOU’LL
LEARN TODAY
◈ The lifecycle of a ticket doesn’t usually start
and end with development team
◈ Use boards to help manage every part of
your process
◈ Goal: Everything needed to complete your
work is in the ticket
◈ How? — Configure Jira to make it easy for
everyone to contribute
◈ Finish with a live demo
4. AGILE BOARDS IN JIRA
Scrum board
For teams who plan their work in sprints. Includes
a backlog.
● “Done” issues disappear when closing a
sprint
Kanban board
For teams who focus on managing and
constraining their work-in-progress. Includes the
option of a Kanban backlog.
● “Done” issues disappear when you Release
Agility Board
Light-weight board in Jira Cloud that’s easy to
customize basic features (think Trello in Jira)
About Boards
Boards display the results of the board filters
● You can have multiple boards per project
● In most situations, don’t overlap your board
filters
● Kanban boards have a filter and sub-filter
All projects in a board filter should use the same
workflow scheme
S
K
A
6. AWESOME CO
Awesome Co has a team of
awesome people who develop
awesome software using Agile
methodologies.
They have all the right people for
the project but are having trouble
managing their entire development
process with one scrum board.
Product Owner UX Designer
Scrum Team Scrum Team
Release Team
7. THE ASK
Before Dev
The Product Owner and UX Designer need an organized
place to prep tickets for the Scrum teams
During Dev
The Scrum teams only want to see tickets that are ready
for them to work on and want to get credit for their work
when it is ready for release
After Dev
The release team only cares about seeing all tickets that
are ready to release
10. BEFORE DEV
◈ Use a Kanban board to manage new tickets and the icebox
◈ The Grooming Board
○ Who: Product Owner, UX Designer, Architects/Lead, etc.
○ Supports an organized grooming process
○ Keep your dev team’s backlog(s) clean
11. KEEP IT CLEAN
◈ Use Swimlanes and Quick Filters
◈ Optionally use Kanban Backlog for the
Icebox and easy Epic management
◈ Tickets should disappear from the board
when ready for development
◈ Use transition screens to fill in fields at
the right time and route tickets
13. DURING DEV
◈ Use a separate Scrum board for each team
◈ Only show tickets that are groomed and relevant to
that team
◈ Adjust the “Done” column to match the team’s
definition of done
15. AFTER DEV
◈ Use a single Kanban board to manage release flow for
both teams
◈ Tickets appear once they are ready for the release
team
◈ Use the Release menu to clear out the “Closed” column
18. OTHER BOARD IDEAS
Overall Status Board
The Product Owner and stakeholders want to see the
status all tickets without having to go to multiple
boards
● Use a single column for multiple statuses
● Use epic or release swimlanes
Combined Scrum Team Board
The backlog view will allow the Product Owner to easily
manage groomed tickets for both teams
Bug Triage Board
Use a separate board and workflow to triage incoming
bug tickets before sending to the Scrum teams
19. THANK YOU
Check out the Modus Create blog
Slide deck will be posted to the NOVA AUG Community page
