ARIS - Projectplan
The project plan is calculated the following way:
For each part, an estimation in ideal implementation weeks (i.e.
weeks with 5 ideal implementation days) is used to get a basic
value to calculate the real needed time. Note that
in ideal implementation weeks/days, only real programming time (which
programmers can estimate best) is counted, i.e. the following is not included:
testing, discussion, dokumentation, bugfix, etc.
To get the really needed calendar weeks, we have to multiply the ideal
implementation weeks with a factor, which is determined empirically (i.e.
measured in former projects), for this
project, we assume, that one ideal implementation week is equivalent to
three calendar weeks. As there are four programmers in the team, and
as we decided to choose an iteration length of three calendar weeks,
we conclude, that our team will manage to implement four ideal programming
weeks in one iteration.
Given a total effort of 21 ideal implementation weeks, we can
calculate, that 15-16 calendar weeks will be needed to complete the
project.
It is also worth to mention, that in the fourth iteration, the
limit of maximum ideal implemenation weeks per iteration is exceeded
by one week, this could lead to a deadline miss, but as splitting
of implementation units between iterations is hard in this case, this
risk is accepted.
| Unit |
Effort |
Week |
Iteration |
|---|
| Entry Basic Data |
2 |
01 - 03 |
1 |
| Search |
1 |
01 - 03 |
1 |
| Display Artefacts |
1 |
01 - 03 |
1 |
| Relations |
1 |
04 - 06 |
2 |
| Adding Documents |
1 |
04 - 06 |
2 |
| Search Graphics |
1 |
04 - 06 |
2 |
| Display Graphics |
1 |
04 - 06 |
2 |
| Virtual Museum |
3 |
07 - 09 |
3 |
| Virtual Museum Graphics |
1 |
07 - 09 |
3 |
| User Administration |
1 |
10 - 12 |
4 |
| Exhibition CD |
2 |
10 - 12 |
4 |
| Exhibition CD Graphics |
2 |
10 - 12 |
4 |
| Cataloge |
2 |
13 - 15 |
5 |
| Cataloge Graphics |
2 |
13 - 15 |
5 |