In the last session of this multi-part series, we spoke about the theory of the solution which involved the creation of 4 separate Scrum Boards using Atlassian JIRA Agile. In this article we will discuss how to actually create the initial Scrum Boards.
In this lesson, we will create Scrum Boards on the JIRA project which in an earlier article, we created essential Components for the following solution. OK, lets dive into creating your first (actually 4) Scrum Boards.
- After successfully logging into JIRA, click on the menu Agile then Manage Boards.
- In the top right of the Manage Boards screen, click on the button Create Board to display the following light box:
As mentioned in earlier blog post, my experience is with and this solution will be based on Scrum Board. As such, click Create a Scrum board.
- It will then ask if you want to create the board based on an existing project or existing Saved Filter. One of the many cool features of JIRA Agile is ability to have a Scrum board not only cover one but multiple projects in same board. If you have already created a saved filter, you can use that filter as your starting point. In this example we will start from scratch by selecting Board from an existing project.
- Now we provide a descriptive name for the board and select the projects it will map to. As you remember, we are creating 4 separate Scrum Boards, so we will create each board using the following names:
- You have now successfully created your first board and be sent to the Plan view of that board. We will discuss more about different views in a later blog. We are not done yet though. We need to now filter the list to show all the appropriate tickets in the Collective Team Board. To do this, locate the button Board in top right and click, then select Configure.
- You will be sent to the General configuration section of the board configuration page. Locate the section Filter on this page and select Edit Filter Query.
- For the Collective Team Board, we want to display both silos of the project (Platform and Marketing & Production) but only display tickets of Tasks and Sub-tasks and Stories. To do this, locate the menu Type: All and click on it. This will display a list of issue types available in your project. Select:
- Epics (helpful for organization and filtering of tickets in Plan view of the Scrum board)
NOTE: Since this Scrum board is used by Shared Resources, we do not need to define Components in the filter. Also make sure the correct JIRA project is selected in the menu to the left of Types.
- Above the location you just selected types, locate and click the button Save to save the updated filter.
- Lets go back to your Collective Team Board to see the results. Easiest method is to open the menu Agile at the top of the screen and should see Collective Team Board at top of the menu.
Now we repeat all steps above to create our Scope Planning Board, but this time Step 7, modify filter query, we select only the issue type Stories.
For our final 2 Scrum Boards, Platform Team Board and Production & Marketing Team Board, we have a slight modification related to Step 7, modify filter query. In addition to selecting Tasks, Sub-Tasks, Stories and Epics, we need to add Components to the filter as well. By default, Components are not displayed in the Basic query, but is very easy to add.
- In the same row as issue types filter, locate the button More and click on it to see a menu of attributes in JIRA.
- Locate the entry Component by either scrolling in the menu or typing in the Search box the word Component. Select it and it will automatically appear in the Basic filter section expanded.
- Depending on what Scrum board you are creating, select the appropriate component. Example
- Platform Team Board = * – Platform
- Marketing and Production = * – Production and * – Marketing
NOTE: When you select more than one value within a menu it creates an OR operand between each value, and when you define a value across more than one attribute, it applies an AND operand between each attribute. Here is the techincal JQuery output (you can also see this by clicking the word Advanced in your window:project = [ProjectKEY] AND issuetype in (Epic, Story, Task, Sub-task) AND component in (“* – Marketing”, “* – Production”) ORDER BY Rank ASC
You have now successfully created your 4 new Scrum Boards for same project.
Read more about the Atlassian Solution below:
Bring Calm to Chaos, a success story with Atlassian Tools
- The introduction and power of Components
- The theory behind the solution
- Creating the Scrum Boards (Hands-on) – this article
- How to create sprints and lessons learned
- How we estimated