Currently, I practice GTD using Omnifocus [pdf link] as the execution tool. I believe this system to be the best out of all the systems I’ve tried thus far, yet I still struggle with prioritization. After completing a few weeks of agile training with our awesome Rally coach Ann, I began to think of how I can apply agile principles, particularly the prioritization methods, to help solve the priority issue.
The first major difference that struck me is the prioritized backlog that is central to agile vs. the list of next actions split by context that is key to GTD. In trying to follow the non-prioritization ethos of GTD, I always have this feeling in the back of my mind that perhaps I’m working on the wrong thing at a given time. My work around has been using due dates and flags within Omnifocus. Specifically, due dates are for items that have some consequence if I fail to deliver on that date and flags are action items I’d like to complete that day.
Here are some initial thoughts of how to apply concepts from both GTD and Agile within the framework of the GTD weekly review in order to achieve some level of prioritization.
