There's one situation I encounter a lot, and that's where the ability to start or continue one project depends on the outcome of another project.
I'll give a concrete example. I'm planning my wedding (well, *we're* planning a wedding, but never mind that). I have several things that are considered separate sub-projects of "Get married", like "Choose venue for wedding", "Choose date for wedding", "create guest list", "Send invitations", etc. etc.
Now, I can't send invitations until I know the date of the wedding and the guest list, and I can't know the date of the wedding until we choose the venue. So I would like the "send invitations" project to not appear until both of those projects are completed.
I realize this can be handled by action groups, but this feels somewhat wrong to me – it's a project all it's own, not an action group. (I guess I think of action groups as "I have this 2 or 3 step project to do and don't want to create a whole project for it.")
So how do you handle these kind of dependencies?
I'll give a concrete example. I'm planning my wedding (well, *we're* planning a wedding, but never mind that). I have several things that are considered separate sub-projects of "Get married", like "Choose venue for wedding", "Choose date for wedding", "create guest list", "Send invitations", etc. etc.
Now, I can't send invitations until I know the date of the wedding and the guest list, and I can't know the date of the wedding until we choose the venue. So I would like the "send invitations" project to not appear until both of those projects are completed.
I realize this can be handled by action groups, but this feels somewhat wrong to me – it's a project all it's own, not an action group. (I guess I think of action groups as "I have this 2 or 3 step project to do and don't want to create a whole project for it.")
So how do you handle these kind of dependencies?