The title basically says it all. I'm a software engineer, and sometimes some of my projects read "develop xyz app", which technically is a thing I plan to do which takes more than one action, but really I'm not sure whether tracking that as a project adds any practical value to my system. A project like that might have 10-15 possible next actions, which could be grouped up into smaller projects. I'm not sure whether "develop app" should be an area of focus (level 2) instead; sometimes its large enough scope that it does become an area of focus, but often projects like this feel like they live in a middle ground.
My question is: At what level of granularity should a project live? Do you use nested projects ever? Should I even be tracking a project like this, or just swap it out for 3-5 smaller projects that are more specific?
Thanks!
My question is: At what level of granularity should a project live? Do you use nested projects ever? Should I even be tracking a project like this, or just swap it out for 3-5 smaller projects that are more specific?
Thanks!