Opened 10 years ago

Last modified 10 years ago

user story #97 (closed: DONE)

AgileAdmin? should be able to 'reset' points per iteration in the event of drastic team changes

Test Complete Size: 3 Test Complete Date: 03/31/2009
Documentation Complete Size: 1 Documentation Complete Date: 04/09/2009
Acceptance Complete Size: 1 Acceptance Complete Date: 04/09/2009
Reported by: ja11sop Owned by: ja11sop
Milestone: Clean up of Plugin with Patch Component: iterations
Version: Keywords:
Cc: Blocked By:
Blocking: Patch SVN Revision:
Patch Trac Version: not_applicable
In Iterations: 20


AgileAdmin? should be able to 'reset' points per iteration in the event of drastic team changes

For example if a team changed from 1 person to 6 people and the team was working in 3 week iterations then the current moving average calculation means that roadmap dates would be wildly inaccurate for several iterations. With 3 week iterations this would mean that the dates provided would not be useful for strategic planning due to their inaccuracy.

By allowing the system to 'ignore' older atypical iteration data you can see new more accurate dates as soon as the first iteration with the new team approaches completion.

We also want to ensure:

  • iterations in the future are ignored
  • only the duration of the current iteration before 'today' is considered

We can add a config setting that allows the AgileAdmin? to specify the ignore_iterations_ending_before date. The date format should match that expected for dates used in the trac instance itself as internally parse_date() will be used. For example you might write:

ignore_iterations_ending_before = 03/17/09

Change History

Have a look at the list of modified files related to this ticket.

Changed 10 years ago by ja11sop

  • test_complete_date set to 03/31/09

Changed 10 years ago by ja11sop

  • acceptance_complete_date set to 04/09/09
  • doc_complete_date set to 04/09/09
Note: See TracTickets for help on using tickets.