Is workEffortTypeId "Project Phase" a Iteration

[Anil Patel-2]

Hi,
Can we use Workeffort type Project Phase for Iteration in software
development projects?

Regards
Anil

[David E Jones]

Yes, an iteration is basically a project phase, but it depends on the context. Actually in many cases a phase will involve a larger set of requirements and involve various iterations. In a way a phase is a super-iteration (ie a parent iteration).

-David


Anil Patel wrote:
> Hi,
> Can we use Workeffort type Project Phase for Iteration in software
> development projects?
>
> Regards
> Anil
>

[Anil Patel-2]

David,
Should we add another WorkEffortType for Iteration?

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.

How is this?

Regards
Anil Patel



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

>
>
> Yes, an iteration is basically a project phase, but it depends on the
> context. Actually in many cases a phase will involve a larger set of
> requirements and involve various iterations. In a way a phase is a
> super-iteration (ie a parent iteration).
>
> -David
>
>
> Anil Patel wrote:
> > Hi,
> > Can we use Workeffort type Project Phase for Iteration in software
> > development projects?
> >
> > Regards
> > Anil
> >
>

[David E Jones]

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

[Anil Patel-2]

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
>
>

[David E Jones]

Anil Patel wrote:
> 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.

Yeah, that'd be great.

> 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.

If we did this it would introduce redundant data. My preference would be to use the natural model and just use a view entity with the 2 WorkEfforts and a WorkEffortAssoc and just query on those. I think that would leave more flexibility for customization and future extension as well.

-David