180 likes | 731 Views
Lessons Learned by Team ‘Charlie’ Kanitta Moonlapong Chompunut Soijit Nootsara Intapun Walailuck Suwannasopon Date 08-07-2008. Things That Went Well. Coding Planning Well document format Finish the work before the deadline Good configuration management by using SVN.
E N D
Lessons Learnedby Team ‘Charlie’KanittaMoonlapongChompunutSoijitNootsaraIntapunWalailuckSuwannasoponDate 08-07-2008
Things That Went Well • Coding • Planning • Well document format • Finish the work before the deadline • Good configuration management by using SVN
Things That Could Have Gone Better • Better at time estimation for each phases in effort metric • Better at documentation i.e. SRS, ETVX, Traceability metric. • Less rework job • Better clearly requirement for easy to code • Deliver the project on time
Things That Surprised Us • A lot of rework job • The estimated time and the real time are too different. • The total time in the last day is the most time in of all days.
Things That Surprised Us • Although the project delivered and the program work correctly, we have to rework the project again. • Walk-through review is the best way to ensure the procedure before coding.
Lessons Learned • Team work • Time management • SVN using • Documentation (SRS, ETVX, Traceability Metric, Effort Metric) • IEEE 1208 Review
Recommendations • You should change schedule • Skipping of content makes us confuse • Please keep the good case study • Please keep the good project • Please keep good resources on the web site
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.