TeamPlanningSpreadSheet2007Story

Acceptance Criteria

Implementation as part of PhpReport of the "time planning spreadsheet", currently used by some groups inside Igalia.

Additional Specification Comments

The idea is as follows. Let's consider this input data:

• Assembly estimated dates (6 by year, by the moment)
• Group meetings estimated dates (6 by year, by the moment)
• Other events estimated dates (congresses, training sessions...)
• Bank holidays related to each worker (NOTE: at this moment, bank holidays are automatically managed, because each worker is associated to a city which its particular bank holidays. It'd be a better idea to change that approach and let each worker choose the bank holidays he or she prefer, checking the maximum allowed).
• Holidays (vacancies) related to each worker.
• Start and end date for each project (I think this data is being collected yet).
• Dates when each worker is associated to a certain project. A worker can enter and leave a project multiple times.
• Dedication of each worker to the project in hours/day. Can change as the project goes by. This information could be merged with the previous one and dedication changes could be seen as the worker leaving and rejoining the project with a different dedication the day after.

With this data in mind, the available work effort in weeks/man for that project can be known (35 hour weeks).

Moreover, the program should allow in an easy way doing tests and solve questions like: What if I assign this worker with this dedication instead of that other worker? (put here any of the previous variables).

During the project course, comparative information about real done work vs. theoretic planified work. It can be that a worker has a 4 hour daily journey assigned but having done 23 hours in the first week for multiple causes.

This requirements could be the basic ones. From there, the module could be greatly improved, but if the things explained are done, it'll start to be useful.

The most interesting should be the data to be able to be changed to do tests, and displaying should be comfortable (using graphs, for instance).

The typical use case is, on one hand, at the project start, when the budget is done. On the other hand, as the project goes by, to see if the evolving is the expected one or if a replanification is needed.

If you have any questions, get in touch with juanjo at igalia dot com.

Implementation Notes

Delay Causes

Final or Pending Considerations

Tasks in this story

div class="twikiTopicInfo twikiRevInfo twikiGrayText twikiMoved"<&/div>-->