Dynamics: Progress Report of the SU phase

Dynamics
Progress Report of the SU phase	$Revision: 1.6 $	State approved
Date 10-Dec-1998	Author Tom Weckström
Review date 10-Dec-1998	Reviewed by Jouni Malinen
Approval date 10-Dec-1998	Approved by Jouni Malinen

$Id: progressreport3.html,v 1.6 1998/12/10 07:57:56 jkmaline Exp $

Executive summary

This report describes the progress of the Dynamic IP-tunnel project in the Design (SU) phase. This report includes several views of the progress. Compact summaries of the done work hours provide a general view of the project efforts. Detailed lists of the booked hours and tasks provide a good means for investigating the project team activities. These tables may also be used to plan and develop the team organization and effort estimation.

Index

1. State of the Project
        1.1 Introduction
        1.2 Reports of effort in SU phase
            Table 1. The reported hours per A.b code in SU phase
            Table 2. The resources used in the SU phase
            Table 3. The team effort distribution in the SU phase
            Table 4. The workload calendar of the SU phase.

2. Completed Tasks
Table 5. All bookings and hours in the SU phase per A.b/c code, week, day and person.

1. State of the Project

This chapter describes the current state of the project. The progress of the project is briefly described, some of the important events are mentioned and the main problems confronted in the SU phase are listed. At the end of this chapter, many report tables are given about done work in the SU phase.

1.1 Introduction

The Design phase has been completed. The deliverables required in the phase have been written, reviewed and approved. So far the scheduling of the project has succeeded. The project Gantt chart visualizes the project schedule. Minor changes to the appointment dates has been made due to other activities of the team members, but generally, the project is in the schedule.

The text and especially the tables of this document include many terms and abbreviations. For help in terminology, please refer the project terminology specification document.

General improvements of team work, organization and working environment done in the SU phase are:

Reduced meeting time while still maintaining tight communication. On the other hand this has increased the time used to emails or IRC sessions. The team has used Internet Relay Chat efficiently for communicating while working in separate places.
Efficient use of PolyTime. The team members have booked their hours daily. This has increased the project manager's possibility to follow the effort consumption.
We installed the LXR source browsing tool to our development environment.
We have verified in our development environment that the establishment of a simple working tunneling system is possible.
Project team organization was improved. Division into smaller groups of two persons was done to speed up the design of the system elements.

In SU phase the team has completed a number of different design documents. The project area has been studied very carefully. The project team has designed the system elements generally and details have been added as much as it has been possible under the restrictions of the project's SU phase schedule.
The returned documents are:

New Documents

Revised Documents

With the documentation of the SU phase the team can begin implementing the modules immediately. The spirit of the team is to define and design the system well to reduce the problems during later phases in which the cost of redesign is remarkably higher. This spirit has resulted in exceeding of the estimated hours in SU phase.

The effort estimation of the SU phase proved to be over-optimistic. On the other hand, this was done partly consciously to limit unnecessary effort consumption caused by Parkinson's law. One of the reasons for coarsely exceeding the initial estimations may also have been the use of PolyTime. Now each of the team members books his hours more carefully, which reduce the number of unbooked hours. It is important to keep on booking all the effort done for the project.

In addition to studying of the project field, also the design of the system elements took much more time than initially estimated. For the team, one of the main tasks of the SU phase was to examine the current Mobile IP solutions and to find out whether there are any that could be used as a basis to our work. We adopted lots of good ideas, but decided to implement the system entirely by ourselves. This is not the most cost effective way, but that way we can guarantee that we know the functionality of every module in our system.

The average weekly working time for one team member sank from the rough 16 hours of the MÄ phase to approximately 12 in SU phase. The team has worked the total of 928 hours during the project. The estimate for the total effort and cost of the project has thus grown 6,69 per cent from the estimation of MÄ phase and is now between 406500 FIM and 569100 FIM.

We did not have any major problems during the SU phase. Some of the problems we confronted were:

Slight problems in scheduling the meetings. This was due to the busy end of the term. There was no meeting where all the team members would have been present.
The signaling protocol seemed to have some problematic behavior. The problems were solved with simplifications or just assuming that we can relay on the media on some degree.
The error situations of the underlying network have a great impact on the tunneling system and we could not investigate all the possible error situations and how our system should react on them.

1.2 Reports of effort in SU phase

Table 1 shows the general effort consumption in the SU phase. The reported hours are shown at A.b code level, and the total sum is calculated.

SU phase: All done work and A.b/c Estimate At Complete

Ab-code ATD AEAC AETC Total 373,00 266,00 -107,00 3.1 Meetings 60,25 90,00 29,75 3.2 Documentation 61,00 41,00 -20,00 3.3 Architecture design 4,75 5,00 0,25 3.4 Protocol design 5,50 12,00 6,50 3.5 Mobile Node design 25,75 7,00 -18,75 3.6 Foreign Agent design 31,00 10,00 -21,00 3.7 Home Agent design 27,00 10,00 -17,00 3.8 Support tools design 6,00 6,00 3.9 Testability design 12,25 10,00 -2,25 3.10 Alpha prototype design 19,50 8,00 -11,50 3.11 Demonstration planning 4,00 4,00 3.12 Tik-76.115 lectures 1,75 10,00 8,25 3.13 Studying the project field 68,00 18,00 -50,00 3.14 WWW-administration 5,00 6,00 1,00 3.15 Project management 8,25 10,00 1,75 3.16 Document reviews 23,75 9,00 -14,75 3.17 Other activities 6,25 6,00 -0,25 3.18 Equipment administration 7,00 4,00 -3,00

Table 1. The reported hours per A.b code in SU phase
[Source: JPT, SU All done work vs AE]

Table 2 illustrates the conventional effort report. It shows the reported hours for each SU phase A.b/c code. Hours are summed up at three levels: total, A code and A.b code levels. The attempt to share the workload uniformly among all team members has some positive results. The workloads of the team members are not very close to each other, but a situation where workloads are even better harmonized, may be too hard to achieve compared to the gain the team gets from it.

SU phase: Hours per A.b/c-code and person

Abc-code ATD AEAC AETC TWE BAN DFO JHA JMA KMU Total 373,00 266,00 -107,00 72,75 61,50 62,50 49,25 76,00 51,00 3 Design phase (SU) 373,00 266,00 -107,00 72,75 61,50 62,50 49,25 76,00 51,00 3.1 Meetings 60,25 90,00 29,75 15,50 6,75 9,50 4,00 13,00 11,50 3.1/1 Team meetings 41,00 50,00 9,00 8,00 4,50 9,50 2,50 9,00 7,50 3.1/2 Customer meetings 11,25 12,00 0,75 2,50 2,25 1,50 2,50 2,50 3.1/3 Course inspection meetings 8,00 10,00 2,00 5,00 1,50 1,50 3.1/4 Team inspection meetings 18,00 18,00 3.2 Documentation 61,00 41,00 -20,00 13,75 14,25 13,75 9,25 10,00 3.2/2 Technical design definition 45,25 18,00 -27,25 8,00 14,25 13,75 9,25 3.2/3 Progress report 3,00 5,00 2,00 3,00 3.2/4 Functional definition 0,25 5,00 4,75 0,25 3.2/5 Testing plan SU 7,50 5,00 -2,50 7,50 3.2/6 Other documents 5,00 8,00 3,00 2,75 2,25 3.3 Architecture design 4,75 5,00 0,25 3,75 0,50 0,50 3.3 Architecture design 4,75 5,00 0,25 3,75 0,50 0,50 3.4 Protocol design 5,50 12,00 6,50 1,50 4,00 3.4 Protocol design 5,50 12,00 6,50 1,50 4,00 3.5 Mobile Node design 25,75 7,00 -18,75 0,50 22,75 2,50 3.5 Mobile Node design 25,75 7,00 -18,75 0,50 22,75 2,50 3.6 Foreign Agent design 31,00 10,00 -21,00 18,50 12,50 3.6 Foreign Agent design 31,00 10,00 -21,00 18,50 12,50 3.7 Home Agent design 27,00 10,00 -17,00 18,75 8,25 3.7 Home Agent design 27,00 10,00 -17,00 18,75 8,25 3.8 Support tools design 6,00 6,00 6,00 3.8 Support tools design 6,00 6,00 6,00 3.9 Testability design 12,25 10,00 -2,25 12,25 3.9/1 Test module design 3,75 4,00 0,25 3,75 3.9/2 Organization of the testing 4,75 3,00 -1,75 4,75 3.9/3 Test case design 3,75 3,00 -0,75 3,75 3.10 Alpha prototype design 19,50 8,00 -11,50 12,50 7,00 3.10 Alpha prototype design 19,50 8,00 -11,50 12,50 7,00 3.11 Demonstration planning 4,00 4,00 3.11 Demonstration planning 4,00 4,00 3.12 Tik-76.115 lectures 1,75 10,00 8,25 1,00 0,75 3.12 Tik-76.115 lectures 1,75 10,00 8,25 1,00 0,75 3.13 Studying the project field 68,00 18,00 -50,00 9,75 17,25 27,00 2,00 7,50 4,50 3.13 Studying the project field 68,00 18,00 -50,00 9,75 17,25 27,00 2,00 7,50 4,50 3.14 WWW-administration 5,00 6,00 1,00 0,50 3,75 0,75 3.14 WWW-administration 5,00 6,00 1,00 0,50 3,75 0,75 3.15 Project management 8,25 10,00 1,75 7,50 0,75 3.15 Project management 8,25 10,00 1,75 7,50 0,75 3.16 Document reviews 23,75 9,00 -14,75 18,00 5,75 3.16 Document reviews 23,75 9,00 -14,75 18,00 5,75 3.17 Other activities 6,25 6,00 -0,25 1,50 1,00 0,75 3,00 3.17 Other activities 6,25 6,00 -0,25 1,50 1,00 0,75 3,00 3.18 Equipment administration 7,00 4,00 -3,00 7,00 3.18 Equipment administration 7,00 4,00 -3,00 7,00

Table 2. The resources used in the SU phase.
[Source: JPT, SU: Hours per abc-code and person]

Table 3 describes the team effort distribution during the weeks of the SU phase. The sums for each week and the total sum are shown. The first week of the SU phase seems to have gone in making other things that had to be postponed during the MÄ phase. As you can see, the work load could still be balanced more towards the beginning of the phase. The weekly hours are clearly biased towards the end of the phase. All in all the scheduling in the SU phase has succeeded.

Team hours in SU phase per week and day

Day of week ATD Total 373,00 Week 45 16,25 Wednesday 3,50 Thursday 10,50 Friday 0,25 Sunday 2,00 Week 46 35,75 Monday 12,50 Tuesday 1,50 Thursday 15,25 Friday 1,00 Saturday 4,00 Sunday 1,50 Week 47 53,50 Monday 0,50 Tuesday 2,00 Wednesday 14,75 Thursday 11,75 Friday 2,50 Saturday 7,00 Sunday 15,00 Week 48 91,00 Monday 5,25 Tuesday 11,00 Wednesday 5,25 Thursday 16,25 Friday 15,50 Saturday 20,75 Sunday 17,00 Week 49 134,25 Monday 41,50 Tuesday 24,25 Wednesday 15,00 Thursday 25,50 Friday 3,25 Saturday 10,25 Sunday 14,50 Week 50 42,25 Monday 16,75 Tuesday 8,50 Wednesday 14,00 Thursday 3,00

Table 3. The team effort distribution in the SU phase.
[Source: JPT, SU: Team hours per week & day]

Finally, Table 4 reports the work load for each team member during the SU phase. The reported hours are shown per week and day and the A.b/c code of the reported hours are given. The hours are summed up per person, week and day. Also the total sum is given. Because Table 4 is quite exhaustive, we represent it in a separate document.

Table 4. The workload calendar of the SU phase for each person.
[Source: JPT, SU: workload calendar]

2. Completed Tasks

This section lists the tasks completed during the SU phase. Briefly, all the activities named in the WBS have been completed. In the SU phase, the activities were mainly not divided into smaller tasks, but the team members booked their done work according to the activities' A.b/c codes. Hence, the booking texts may be understood as tasks.

Table 5 shows the reported tasks in the SU phase. The bookings are shown per week, day of the week and person. For each booking, the associated A.b/c code, booking text and reported hours are shown. The hours are summed up by day of the week and week. Also the total sum of the reported hours is shown. Because Table 5 is quite exhaustive, we represent it in a separate document.

Table 5. All bookings and hours in the SU phase per A.b/c code, week, day and person.
[Source: JPT, SU: Abc&bookins &h / w,d,prs]