MS Project Guidance

MS Project Guidance

The MS Proposal Committee met and evaluated the proposals submitted for the Spring '06 semester.

There were 48 submissions. Of these 18 were listed as revise and 6 were rejected.

The problems (not an exhaustive list) with the proposals that needed revision were:

the problem was poorly stated and not understood by the reviewer or absent totally,
there were no deliverables listed,
there was no timetable, and
there was no design or implementation discussed.

Many of the proposals needing revision had no implementation listed as if this were a term paper exercise. The Masters project is not a term paper/state of the art paper. If the student can show in the revised proposal they are implementing a system the project may be approved.

Too many of the students said the equivalent of "this is what I'm going to do and I'll figure it out next semester". This is a sure path to failure and frustration. There must be a preliminary design, a timeline, and a list of deliverables.

One of the rejected proposals listed two students. This is unacceptable. If they are to work together there must be two proposals indicating what the student is responsible for and how the two proposals are to be integrated.