(I'm going to Usenet-style quoting, because that's easier with my editor and I'm a lazy dinosaur.)
Originally Posted by lareaarnett
> I don't like to set up multiple levels
> of subprojects either. (to tell you the truth I'm not all that
> crazy about outlines in the first place!) But the items above I
> see as clearly one project - although it may have separate moving
> parts and different phases.
> Now you could make each evaluation a subproject but you don't
> have to unless there is so much going on that putting it all
> under one is too confusing.
But that's my problem. I like it all to be _really_ simple, especially when I'm dealing with something scarey where I have limited expertise - and I'm assuming that that's the case in this scenario, where I've inherited a business that I don't know. To go to the "cranking widgets" metaphor, I want to define tiny little nonthreatening widgets that I can easily crank.
So wherever I have a moving part, I like to have a separate project. I see each accountant evaluation as having separate moving parts, so I'd build a separate project for each one. The same for developing each checklist, and so on.
Now, I could have organized "evaluate accountants" differently. If I were evaluating, say, a dozen, then I would have designed it as a single project, with actions for creating evaluation checklists, for going through a call sheet, and so on. Again, I'm assuming that this is scarey and I don't know what I'm doing, so I'm getting it down to the simple-task comfort level of "call Jane".
> I think that most projects have future things that can't be done
> right now and I think it's good to capture those but they are not
> next actions and likely are not stand alone projects......I will
> be interested to see your response.
I agree that the truly future things - for example, all the tasks that have to wait until I've chosen an accountant - can just stay in the project support material somewhere. But every separate area that can be moved forward at this time, I'm inclined to define as a separate project.