Two projects sharing one Next Action

  • Thread starter Thread starter jayx773
  • Start date Start date
J

jayx773

Guest
Hello,

Is it possible to have two projects (a project and its subproject) share the same NA?

For instance, I have two projects listed:

1. Creation of Database reported to Boss
2. Database Created

I have listed the report db in projects because I think it is very important and i don't want to forget it.

Now I obviously can't report to my boss until the DB is created. In reality all NAs for project 2 also belong to project 1. Does project 1 need it's own NA or waiting for, or can it share project 2's NAs so that when I review, I can rest assured that project 1 does indeed have a NA?

Thanks!
 
Hi Jay, my question is do you really need two projects?

For instance, if you just work on the final goal of "Report Database Creation to Boss", the actual creation of said database is implied. So do you need to explicitly list that as a separate project?

Hope that helps,

Adam
 
Jay, it seems to me that you could have one project "Database Creation" with report to boss as the last NA for that project; the NA that says to you "project complete".
 
Reporting the creation of the database doesn't seem to me like a project at all. Having two seperate project tags for the same set of tasks is redundant and already created more work than was necessary. Even if it has multiple steps to it, it is part of the project for creating the database. Combine them and your problem is solved
 
I think that if you work with your final outcome as your project title (I dip in and out of this, really not something I focus on, but . . . ), then if reporting the creation of your database to your boss is your envisioned "wild success" as per DA, I think that project could be the one remaining.

Yes, Creating the Database is the project, but if you are trying to use the name as an additional visualization/motivation tool, then this might not be as poignant as the mental picture of reporting your success to your boss.
 
Alright, after reading Adam's reply I am having different thoughts about this than I first posted. If "Reporting New Database to Boss" is indeed the project (and I definitely see the argument for that) then I think that "Database Creation" must be a sub-project. Since the completion of the main project is continent upon the successful completion of the subproject, all NA's would be attached to the sub-project until the database is created. After that, NA's would be attached to the main project until the report to boss is done.
 
jayx773;51200 said:
Hello,

Is it possible to have two projects (a project and its subproject) share the same NA?
Click to expand...

This actually happens to me quite a lot. Its one of the few real advantages that software has over paper. Any decent software organizer will let you classify an item/task/event in multiple projects/folders, in multiple contexts, and in multiple categories all at once. I do this fairly frequently not just because I want to be sure to see the item at the proper time and place, but because filing it multiple ways makes it more likely I'll find it easily later.

Tom S.
 
jayx773;51200 said:
Hello,

Is it possible to have two projects (a project and its subproject) share the same NA?

For instance, I have two projects listed:

1. Creation of Database reported to Boss
2. Database Created

I have listed the report db in projects because I think it is very important and i don't want to forget it.

Now I obviously can't report to my boss until the DB is created. In reality all NAs for project 2 also belong to project 1. Does project 1 need it's own NA or waiting for, or can it share project 2's NAs so that when I review, I can rest assured that project 1 does indeed have a NA?

Thanks!
Click to expand...

I think it is possible. If it does happen you are prioritizing correctly by picking the next action that effects the most things in your world.

In addition to asking yourself what the next physical action to move forward on a project, for projects with multiple possible next actions that could effect other projects you can say.

What is the best possible next action I could be doing on this project right now.

Take into mind how many projects the next action effects and this is a good way to prioritize.
 
I often have one next action for two projects, but in the sense that they are really separate projects. For example, if I am working on two printing projects and the same printer (or same graphic designer) is working on both, then in my next action to "Call X" I can move both projects forward in my discussion. The projects can be separate, they might be at different stages, the single phone call can handle tasks for both projects.
 
I think this is becoming too complex. Whichever you consider as the project vs. subproject, one of these has one and only one step - Communicate the completion to the boss. Separating out one step as a project or subproject seems like overkill. It takes some number of tasks and time to build the DB. One more task that takes little time of informing the boss that it's complete should not be elevated to the same level.

Even if informing the boss consists of scheduling a meeting, preparing a presentation (even if it's only outlining for yourself what you want to say), actually saying it and documenting the conversation, I can't see that as any more than a series of final tasks within your Build the Database project. Especially since all of this work is dependent on the completion of the Build the Database work. If it sits on your project list as a separate project, every time you review the list your mind will tell you, Oh - this is a project I can't do until Build the Database is complete. This will give you a project list that contains a project you can't do yet and that can't have a task on your NA lists, unless you want to schedule that meeting ahead of time to push yourself to meet a deadline. Then again, it's very interrelated with the Build the Database project. You can't start putting your presentation together until at least some of the work is completed. Bottom line, I don't think it's a separate project or subproject.
 
WebR0ver;51239 said:
I think this is becoming too complex.
Click to expand...

As usual I agree. I would advocate a little common sense here. Do what's most comfortable. If that means one action and multiple projects, do it. If you try it and it doesn't work, then do something else. But only make it as complex as you need to.

I mean, honestly, does it really matter in the end if you get it done?

Tom S.
 
Tom Shannon;51245 said:
As usual I agree. I would advocate a little common sense here. Do what's most comfortable. If that means one action and multiple projects, do it. If you try it and it doesn't work, then do something else. But only make it as complex as you need to.

I mean, honestly, does it really matter in the end if you get it done?

Tom S.
Click to expand...

Great point!

Thanks for all the help!
 
You must log in or register to reply here.
Top