LESSONS LEARNEDBY TEAM ‘CHARLIE’

KANITTA MOONLAPONG CHOMPUNUT SOIJIT

NOOTSARA INTAPUNWALAILUCK SUWANNASOPON

DATE 08-07-2008

THINGS THAT WENT WELL

1. Coding2. Planning3. Well document format4. Finish the work before the

deadline5. Good configuration management

by using SVN

Ap

ril 21

, 20

23

THINGS THAT COULD HAVE GONE BETTER

1. Better at time estimation for each phases in effort metric

2. Better at documentation i.e. SRS, ETVX, Traceability metric.

3. Less rework job4. Better clearly requirement for easy to

code5. Deliver the project on time

Ap

ril 21

, 20

23

THINGS THAT SURPRISED US1. A lot of rework job

2. The estimated time and the real time are too different.

3. The total time in the last day is the most time in of all days.

Ap

ril 21

, 20

23

THINGS THAT SURPRISED US

4. Although the project delivered and the program work correctly, we have to rework the project again.

5. Walk-through review is the best way to ensure the procedure before coding.

Ap

ril 21

, 20

23

LESSONS LEARNED

1. Team work2. Time management3. SVN using4. Documentation (SRS, ETVX,

Traceability Metric, Effort Metric)5. IEEE 1208 Review

Ap

ril 21

, 20

23

RECOMMENDATIONS

1. You should change schedule2. Skipping of content makes us

confuse3. Please keep the good case study4. Please keep the good project5. Please keep good resources on the

web site

Ap

ril 21

, 20

23

FINAL THOUGHTS

What one aspect of this project would you change if you could? Why?

Estimate time and reduce a rework job because the job will finish quickly.

What one aspect of this project would you keep unchanged? Why?

Team members because we are so team work.

Ap

ril 21

, 20

23