Date index for Jul 2002
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [achievo] sub-projects
We use the project and phase combined as the principle key for collecting
cost. Phase definitions usually vary significantly from project to project
either based on customer SOW or preferred cost collection breakdown
approach.
Activities are standardized across all project in order to facilitate
consistent metrics gathering. Activities include the tasks that we do every
day like: Analysis, Design, Coding, Report Status, System Administration,
Recruiting, etc..
We would like to have the ability to create multi-level projects and/or
phases, because very often two levels of cost breakdown (Project and Phase)
provides insufficient granularity to adequately capture cost. This is
particularly true for large projects.
Best Regards
Rodney
----- Original Message -----
From: "Scott Thurmond" <scott.thurmond dot
To: "Achievo" <achievo dot
Sent: Thursday, July 11, 2002 8:09 AM
Subject: [achievo] sub-projects
> This is my first cut at using Achievo. I have some usability questions.
>
> In a project, I have several programs that need to be written - non of
them
> dependant on the other. Could be programs to produce reports, some entry
> screens, etc. How should I organize my data?
>
> Should I list each program as a separate project? I could do that but it
> would make my record keeping very messy. I would like to have a master
> project that contained sub projects. Any help?
>
> How do most people use phases and activities? Are common phases
> "development", "test", "productions", "maintenance", etc?
>
> Could you give me some examples of how you would group activities and
> phases?
>
> Kind Regards,
> -Scott
>
>
>
> [ Achievo mailing list - http://www.achievo.org/ ]
> [ to unsubscribe send an e-mail to achievo-unsubscribe dot
>
>