Re: Is workEffortTypeId "Project Phase" a Iteration

Posted by Anil Patel-2 on
URL: http://ofbiz.116.s1.nabble.com/Is-workEffortTypeId-Project-Phase-a-Iteration-tp181353p181357.html

David,

I'll plan for a Screen to show list of Tasks in Project. I think we can add
a flag to filter out tasks that have been assigned to some Iteration.

For Tasks and Sub Projects association with Project in AssociationType of
WORK_EFF_BREAKDOWN. Should be use some different kind of association between
Tasks and Phase (Iteration) So its easy to filter out during reports and
different user tools.

Regards
Anil




On 5/28/07, David E Jones <[hidden email]> wrote:

>
>
>
> Anil Patel wrote:
> > David,
> > Should we add another WorkEffortType for Iteration?
>
> My preference for flexibility is that we just use phase for both, and then
> people can interpret it based on the structure.
>
> For both higher level phases and iterations the general process for
> managing them will be similar. A classic agile/XP style iteration is just a
> shorter time period like two weeks as compared to a project phase which may
> be a few months.
>
> For either one part of setting them up is deciding which tasks from the
> project in general should go into them, which is why we want a screen that
> shows a list of all project tasks sorted by priority to make it easy to pick
> the top few and assign them to a phase (big or small).
>
>
> > Also I understand that
> > 1) Sub Project (WE) will be a Project that has a Parent.
> > 2) Sub Task (WE) will be a Task that has Parent task.
>
> These terms don't really mean anything when applied to a single
> WorkEffort, but as you mention only when describing one WorkEffort relative
> to another WorkEffort. In other words, we would never have a WorkEffortType
> of "Sub Project" or "Sub Task", these are just WorkEfforts of type Project
> or Task that are children of another Project or Task.
>
> -David
>
>