Fall-Week 5 Senior Project Work

Senior project this week was relatively interesting.

First off, the Tuesday meeting on 6/30 went OK, but it really revealed just how dangerous some of our clients can be in ways. The main problem with this happens to be that during each meeting, not only is there substantial requirements creep/churn, but the clients have a tendency to not only hijack the meetings, but to also want to be, for lack of better words, "too deeply" involved with aspects of the project. This has to deal with many ideas, such as having requests for having code editable by people with no technical skills, while still having it function properly. Likewise, creating or embedding editors into the system that will allow these people to do this, none of which is really that easy or feasible.

From there, our adviser and group has decided many of the following:

1. We must have an agenda clearly created and maintained, ready to be presented on the Monday before the client meeting of the week. This will be done by gathering up accomplishments and concerns on Sunday and Monday.

2. Meetings will be limited to no longer than 1 to 1.5 hours of discussion. The first hour should be nothing but presentation of what has been accomplished and review / feedback with respect to those issues. Following this, there will be a meeting break and the last .15 to .5 hours will be spent on feedback or client concerns. This will allow for a follow-up reflection directly after the meeting.

For this week, the experienced web developers have planned on editing and creating several of the pages and functionality sets that have to deal with the people / project aggregation part of the system. Aside, I will be attempting to get my hands into the code and create the basic models for the system.