Evaluation SCM Practical work 16th May 2006 ------------------------------------------- The SCM practical work turned out to be a succes. Here are some notes on the schedule and some remarks from the lecturers and students. Schedule 9:00 Start 9:15 Writing SCM plan started at most groups 10:00 Groups start with digitizing the SCM plan so far 10:10 "You must check in your SCM plan now!" + RequestA 10:45 Most groups have finished Request A 11:10 Three groups have Request B+C now 11:45 Last 2 groups receive Request B+C 11:50 Request D to everyone 12:15 "Please Finish and print your SCM plan" 12:30 Evaluation in Lecture Room 13:00 The end Remarks by lecturers: - SCM plan writing takes too long - Request B+C was given late to some groups - More emphasis on merging is requested by students - Work of one group was not satisfactory - Two groups were well-organised and moved ahead - Groups that worked in parallel finished more requests - Recording of Actual Streaming can be done better (at least one group was confused because they were not aware of the current codeline situation) - Some groups lost time on Java programming/Unix commands - Commandline or graphical that's the question - Performance of graphical (Eclipse) was slow but workable - Number of problems with CVS commands was smaller than expected Some pre-conclusions: - Two practice blocks for this work is better - One with more CVS stuff + merging - One with SCM planning (Note: All work related to SCM planning (and requests) should be in one block) - Three phases of requests? - 1 one warming-up request - 2 three parallel requests (create three branches) - 3 one merge request to merge the three branches Remarks by students - Preparation of initial SCM plan before the start - Much work - More merging - Practice in the lecture is good - CVS learning -> warming-up too simple - SCM plan is important - Split work on CVS and SCM plan -> separate practice ? - week 1 basics of CVS / initial SCM plan - week 2 company simulation