Project

General

Profile

Feature #370

Parallel versions in a milestone

Added by Raghu GS about 12 years ago. Updated about 12 years ago.

Status:
Resolved
Priority:
Normal
Category:
Versions
Target version:
Start date:
2010-12-29
Due date:
2011-01-17
% Done:

100%

Estimated time:
Milestones:

Description

Does Advanced Roadmap Plugin supports Parallel Versions?

Problem:
Milestone "Cairo" has two versions, Version "Virgo" and Version "Lucid".
Both "Virgo" and "Lucid" has it's own set of resources or workers.
"Virgo" estimated version completion time is 6 months.
"Lucid" estimated version completion time is 3 months.

If Advanced Roadmap Plugin supports parallel versions, then "Cairo" Milestone completion date should be 6 months.
But currently, "Cario" Milestone completion date is 9 months.

Can you fix this behavior or give me pointers to fix this issue in my installation?

#1

Updated by Emilio González Montaña about 12 years ago

  • Tracker changed from Support to Feature
  • Target version set to Advanced roadmap 0.3.0
  • Start date changed from 2010-12-03 to 2010-12-10

May be it will be useful to include some project configuration to allow defining an effort in men, so if you have 2 (or any floating number) people working in a project, the milestone due date will be recalculated by this cipher.

What do you think?

#2

Updated by Raghu GS about 12 years ago

But why do we need to complicate this requirement?
Just improve the plugin to check whether same resource (Employee) or same set of resource (Team) working in any number of versions.
If it matches, then it should not do parallel version estimation, but if it doesn't, then the plugin should give a combined estimation.

#3

Updated by Emilio González Montaña about 12 years ago

  • Start date deleted (2010-12-10)
#4

Updated by Emilio González Montaña about 12 years ago

Please, give me a better description about the solution, I mean in algorithmic point of view.

#5

Updated by Raghu GS about 12 years ago

Hi Emilio

Actually devising an algorithm for calculating correct eta is difficult.
So if both "Virgo" and "Lucid" has issue, then, the plugin should assume that both the versions are being worked on concurrently, so it should calculate Milestone ETA by combining both version's ETA.
As relying on headcount or resource differentiation won't make sense, so we can simplify the solution.
So just show the longest ETA of a version as the milestone completion time, instead of calculating each versions separately.

#6

Updated by Emilio González Montaña about 12 years ago

  • Status changed from New to In progress
  • Assignee set to Emilio González Montaña
  • Start date set to 2010-12-29
#7

Updated by Emilio González Montaña about 12 years ago

  • Due date set to 2011-01-17
  • Status changed from In progress to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF