Spring 2008 Recommendations
Tou Fang - Team Leader
- I truly think that the Team Leader should have some control of the team through their grades.For example, maybe he/she should take attendance for each meeting or work session, and the attendance should be at least 30%-60% of the grades. What I found was obvious, that those who attend the meeting and work session regularly did more work for the project. I strongly recommend attendance as a grade contribution.
- I think that the lectures are useless, especially at this stage of this particular project. The project is at a stage where it needs technical skills which I believe that the lecture should help with. Neither that or I found the lectures to simply not useful towards this particular project.
- I was not a big fan of the notebook either. I understand the importance behind the notebook, however:
- We are not in the planning stage of the project anymore, so we do not have to take as many notes. I believe that we should still have it,however, it should not be weighted as much.
- The project is already using a similar system, which I believe it is much better. We were already using the trac system which keeps trac of all the work that everybody does by the date and time. Every single changes we made on the track site and the web application was recorded on the trac site. If anything, I think that this record should hold value to the progress of a team member's work.
Michael Cabrera - Financial Officer
Allison Fong - Secretary/Programmer
More documentation because it's hard the read the code, especially when this is your first quarter. Train the new people and assign them a task as soon as possible in the quarter and make sure they understand how to do everything. The transition period for me to really start working on the project was really long, too long. It would also probably be more helpful to have more work sessions and for longer periods of time.
Christopher Burnett - External Relations
Keep better track of task due dates and progress. Follow up on reasons why a task is coming along slowly (is it a knowledge gap? is it a bug of some sort? is there a missing component that the task requires?). Whenever someone comes across a challenge/barrier they should ask for help and if they need to wait till next meeting, then accept another ticket and work on another task. There is enough to be done that even if there is a knowledge gap or problem, someone can work on something else until they get the help they need rather than just waiting for the next meeting.
Henry Koren - Chief Programmer
Long Pham
More training and workshops for new members about computer programming and other skills necessary to be productive and helpful for the project. Learning php and MySQL was difficult when after reading many of the on-line tutorials, which have a lot of information that is not necessarily important for the project. Also better communication between all the members and having set times were everyone involved can meet and avoid stepping on other people's toes when they are coding for the on-line module wold be helpful. Also cut down on the Wednesday meeting to function as a way to check in and update clients rather than use those meeting as a place to debate certain aspects of the project.
Sheng Wang - Programmer
Better communication. I'm sure our group leaders did all they could to bring the group together, but due to my job and classes during meetings, I was not informed of meetings until the day they were held.
Saad Omar - Programmer
Alvin Chen - Programmer
Needs better documentation of code, a lot of the code is hard to understand and just minimal commenting would go a long way. This was my main problem when working on this project, not being able to understand a lot of the code. I also recommend having a meeting time where every member could attend, which would minimize further complications.
