Midway through Interstellar Racing League, I decided to use JIRA to track and manage tasks of an important sub-team. This page describes the ways I sued the software to discover blockers, facilitate communication, and gain insights.
WHY: REPOSITORY FOR TEAM
PRACTICAL USE: FIND DEPENDENCIES
By individually entering each of the track team’s tasks, I identified inter-team dependencies. I then connected the appropriate parties, saving a significant amount of time. This had the greatest benefit for the track and environment teams.
WHY: CLEARER TASK DISPLAY
PRACTICAL USE: GAUGE DISCIPLINE PROGRESS
I created four filters to simplify JIRA navigation for the team. The “LD” and “AC” filters allowed me to determine how our level designers and artists were managing their tasks. In one instance, I realized one of those groups had been checking out multiple tasks at once, resulting in slow progress in many areas rather than finished work.
WHY: ASSOCIATE TASKS WITH GOALS
PRACTICAL USE: TRACK PROGRESS ON USER STORIES
In this project, I used epics to represent user stories. Using JIRA’s built-in Epic Report, I followed the progress of our user stories throughout the sprint. When we needed to cut content, I was able to identify the features for which the team had the most work left.