A few months ago, I was listening to an episode of The Jira Life while commuting back home from the office. (Special shoutout to The Jira Life and Kythera Contreras!) The episode was all about using Jira to run your personal life.
My first thought was “kinda sounds like overkill”. My immediate next thought was “wait… why haven’t I thought of this”?
The episode featured Kythera Contreras, who was a huge source of inspiration for this article, this experiment, and my now improved personal productivity. The more I listened to the episode, the more using Jira outside of work just made sense. Before the episode even ended, I had already decided that I’d experiment with this for myself. I reached out to Kythera to ask a few more questions about her process and what her configuration in Jira looks like to get some ideas for my own.
Then, I set out to answer the question: Could Jira really be the answer to my personal productivity problems?
The Problem
Each time I tried a new task tracker or to-do list app, I would run into the same scenario. It was always great at first because my list would be small in the beginning. Inevitably, it would grow into this enormous, overwhelming mountain that I couldn't seem to climb.
And it wasn't just one list. Tasks lived on sticky notes, in notepads, in two or three different apps - wherever I happened to be when the thought hit me. I never had a single, trustworthy view of everything on my plate.
Even when I did sit down to get things done, I'd start five things and finish none. Everything was "in progress." And every task looked the same on the list, whether it was renewing my car registration or scheduling an appointment. Every time I opened one of the apps, I'd stare at the list, immediately feel overwhelmed, and close the app.
The worst part was the guilt. Every unchecked box felt like a small failure, and eventually I'd just abandon the app altogether, only to start the cycle over with a new one a few months later. And yet again, I'd find myself drowning in an endless sea of tasks.
Never clarity. Only chaos.
The Setup
Space Type
For the type of space, I decided to go with creating a team-managed software space. With this experiment, simplicity is key, and a company-managed setup would have been overkill.
Workflow
I intentionally kept the workflow extremely basic.
To Do → In Progress → Done
The columns of the board also reflect these 3 statuses.
Work Types
I decided to create two work types with a tiered approach:
- Mission (at the epic level)
- Task (at the standard level)
I wanted some way to track tasks that were related to the same larger effort (Holiday shopping, for example) and found that this approach gave me what I was looking for.
Fields
Didn’t change too much here from what the out-of-the-box Jira template gives you. I did, however, create one custom field - Energy.
Energy (Single Select):
- High Energy
- Medium Energy
- Low Energy
I created this field because every task doesn’t carry the same level of effort and I wanted to capture that. When it’s 9 PM on a Thursday night, I probably don’t have a high mental capacity for a medium or high energy task… but maybe I do for a low energy one.
Mission | Task |
|---|
- Summary
- Description
- Assignee
- Priority
- Due Date
| - Summary
- Description
- Assignee
- Priority
- Energy
- Due Date
- Sprint
- Parent
|
WIP Limits
I decided to configure a WIP limit of 2 on the In Progress column on the board. If I hadn’t done this, I very well may have ended up in the same scenario as when I used other task trackers - where everything becomes “In progress”. And when everything is in progress, nothing is in progress.
P.S. Multitasking is a myth!
The Experiment
With the above configuration, I started working on my backlog. I took the various tasks that I had scattered across my notepads or my plethora of task tracking apps and moved them all into the backlog. I ended up with an initial backlog of 89 items.
With that done, I started to plan my first sprint. It would start on Sunday and end the following Sunday. I decided on 6 as the maximum number of items I would have in the sprint at a time. I chose 2 items from each energy level and added them to the sprint.
At this point, I didn’t have a process. I didn’t have a plan. I didn’t even have a sprint goal.
I didn’t wait for the stars to align and for things to be perfect. I simply started the sprint.
Lessons Learned
I’ve been doing this for 3 months now and here’s some of what’s changed.
Created a Sprint Cycle
After a few iterations of sprints, I’ve established a process that works for me. Collectively, it’s only 22 minutes out of my week.
- Sprint Planning (15 minutes)
- Before I open Jira, I look at both my personal calendar and my work calendar. Do I have any tight work deadlines? Any big personal events coming up that are going to require more of my energy and focus?
- Each Sunday, I go to the backlog and review the items there, looking specifically at Due Dates. Is there anything that NEEDS to be done during this next sprint because it has a hard due date? Those are priority items and pulled in first.
- Mid-week check-in (2 minutes)
- Each Wednesday, I sit down and look at where things are in the sprint. Is anything blocked? Does anything need to be removed from the sprint and sent back to the backlog guilt-free?
- Sunday Retro (5 minutes)
- Each Sunday, before planning, I sit down and look at the sprint I’m preparing to close. The only column I focus on is the Done column. I take note of each item in the column and before doing anything else, I give myself a pat on the back. Again, the goal was never perfection.
Leveraged Automation and Rovo
This is my absolute favorite.
As part of my process, I started to realize that even though my number of fields is relatively low, it still took a great deal of effort to ensure the work items in the backlog were filled out with proper information for my future self. One day, while adding some items into the backlog I had a random thought. “Man, I wish AI could just do this for me.” Then, I remembered that Rovo exists.
I immediately went to Rovo Studio and started filling out the prompt for having Rovo create a new agent. It was simple - I wanted an agent to triage new work items as I was creating them. I just wanted to enter the summary of the work item and have Rovo fill out the rest of the information. I called it the “Work Item Enricher”.
I gave it simple instructions:
You are an intelligent assistant that helps streamline work item creation by analyzing the
summary field and automatically populating related fields. When a work item is created:
1. Read and analyze the summary to understand the nature and scope of the work
2. Generate a clear, detailed description that expands on the summary with relevant context
3. Assess the energy/effort required and set the appropriate energy field value
4. Determine the priority level based on keywords and urgency indicators.
With the agent created, the next piece was creating an automation so the agent could take action every time I created something new. As a Jira Admin, I’m very familiar with creating automations so I did this part myself, but I could have used Rovo Studio to create this automation as well. The automation is simple: 3 steps in total.
Whenever a work item is created, the Work Item Enricher Rovo agent will automatically update the work item on my behalf, setting fields such as the priority or the energy level. After performing the updates, the Rovo Agent will comment on the work item with context behind why it made the decisions that it did for the work item.
Incorporated the Jira Mobile App
Initially, I was working with my Mac only. It was fine whenever I was at home or somewhere stationary with my mac present. Not so much whenever I was on the move or trying to briefly interact with Jira. Phones, however, are perfect for when you’re on the move. I downloaded the Jira app and created a widget on my home screen. Now, my backlog and my active sprint are with me wherever I am.
Key Learnings
- Start simple.
- I did not create the Rovo agent and automation on Day 1. I worked with the process manually for a while before the need for the agent and automation came organically. It’s perfectly fine to start simple and then add complexity as maturity grows and habits start to form.
- Respect the Backlog.
- If something doesn’t make the cut for this week’s sprint, that’s a win. It means you effectively prioritized and chose what matters most. It doesn’t mean you’ll never get to that item. As the classic saying goes, “Rome wasn’t built in a day”.
- Your Jira Your Way.
- What works for me may not work for you, and that’s great! Jira is a highly flexible tool that can be customized to meet all kinds of needs and use cases.
My Results
There's been a monumental difference in how I view personal task tracking. It's no longer this painful, guilt-inducing chore. It's become a simple system that takes way less brainpower and way less time to manage.
My tasks are no longer scattered. All of them now live in a single backlog.
It's no longer overwhelming. During the week, I never look at my backlog. Instead of focusing on my full to-do list, I'm only focusing on the tasks in my active sprint.
I'm the most productive I've ever been. My backlog is down to 9 tasks. I'm feeling great about my productivity and great about myself.
It's no longer busywork. I simply type in a summary, Rovo does the rest, and I'm left with a groomed backlog.
Most importantly… It's no longer chaos. It's clarity.
Over to You
Now it's your turn. Have you ever used Jira (or any Atlassian tool) outside of work? What does your personal productivity setup look like?
Share your tips, your setup, or even your chaos in the comments. Trust me, there’s no judgment here.