Sequential and Parallel Projects
I'm a long time Omnifocus and GTD'er. I've been heavily relying on Omnifocus's ability to do Parallel vs. Sequential projects. Sequential projects hide any tasks which are dependent upon a task before it.
1. Call girlfriends mom about her ring size @phone
2. Go to the mall and buy ring @errands
3. Make dinner reservations @phone
In this example, only the first task will show in my @phone next actions list since the other tasks are not available yet.
I'm a software developer and a few of my colleagues (who have built some fantastic GTD software) disagree with this methodology. They say this is not a standard GTD practice, it's something that I've just added to my own workflow.
I've read the book several times, and I don't remember this ever being directly addressed. But, the concept of only seeing items that are actionable was addressed quite clearly.
Are my colleagues right? Should I be working entirely out of parallel projects and ditching sequential projects entirely?