Question on organizing projects...
I'm in academia, and a big part of my job is publishing papers in scholarly journals. These are usually multi-year efforts to publish a paper. They involve many moving parts, such as finding and reading relevant literature, obtaining and analyzing data, and writing the paper. Each of these parts have different objectives, but should all come together when the paper is finally published. I'm wondering what is best way to organize projects like this.
I could create a all-encompassing project like "Publish Paper on XYZ" with many different actions focused on literature, data, writing. Or I could set up different projects like: "Perform Experiments for Paper XYZ", "Find and Read Relevant Literature for Paper XYZ", "Write Paper XYZ".
What does the GTD collective recommend for situations like this?
p.s. I could imagine a similar situation for product development, such as software development. Like "Release Version 2.3 of Software Program XYZ", where lots of efforts have to come together (writing code, debugging, user testing, etc.).
I'm in academia, and a big part of my job is publishing papers in scholarly journals. These are usually multi-year efforts to publish a paper. They involve many moving parts, such as finding and reading relevant literature, obtaining and analyzing data, and writing the paper. Each of these parts have different objectives, but should all come together when the paper is finally published. I'm wondering what is best way to organize projects like this.
I could create a all-encompassing project like "Publish Paper on XYZ" with many different actions focused on literature, data, writing. Or I could set up different projects like: "Perform Experiments for Paper XYZ", "Find and Read Relevant Literature for Paper XYZ", "Write Paper XYZ".
What does the GTD collective recommend for situations like this?
p.s. I could imagine a similar situation for product development, such as software development. Like "Release Version 2.3 of Software Program XYZ", where lots of efforts have to come together (writing code, debugging, user testing, etc.).