Project Milestones (Page 4 of 4) in pdf

Grade

Criteria

Good report, all milestones met

Good report, milestones not met, but delay is clearly/strongly justiﬁed, e.g., signiﬁcant work done

but task became larger than expected or there was a bug

Approach to ﬁnding the bug was systematic and clearly explained

Bug demonstrable and well understood, i.e., bug is found and ﬁx is known

Suitable adjustments to milestones have been made

Good report, milestones not met, some work done or bug encountered

Good debug strategy in place, but bug not yet found

Suitable adjustments to milestones have been made

No report, some work done but milestones not met and probably could have been met with more

effort or unsolved bug encountered

Good debug strategy in place

Adjustments to milestones presented

No report, some work done but milestones not met and should have been easily met with a little

effort or unsolved bug encountered

Poor debug strategy being used or proposed

Or, no adjustments to milestones presented

No report or non attendance or no milestones met or no work done

Notes:

1. All reports are due prior to the weekly scheduled lab demo. Otherwise, there will be a ”Late Report (-2)” grade

deduction.

2. If students cannot demo their weekly progress at the original scheduled time, then the students must arrange

another time with their respective TA to demo their progress for full marks.

3. The weekly report is due at midnight on the day before the (non-modiﬁed) weekly scheduled lab demo.

4. Adjustments to the milestones must be approved by the TA.

Overall Project Strategy

Your overall project grade will depend on how well you meet your original milestones, or, if you encounter difﬁculties,

how well you make adjustments by the end of the project. It is most important to be able to show something working

by the ﬁnal demonstration.

Choose your project in a way that you can afford to slip (four-letter word that managers hate to hear) a few weeks

and still show something that works at the end.

This means that you should have several working stages, each with some additional functionality or features. If

you have some unforeseen delay, you should be able to still show something that works in the end, even though it is

not the full project you initially proposed. This is an important part of planning a project: get some basic stuff working

as soon as possible. Add fancy features, optimize your circuits, and make it beautiful later. Time to market (time to

marks?) is often more critical (how to make money) than being perfect (the dreaded perfectionist engineer). It is better

to build something that works with basic functionality, than build something pretty that does nothing.

Project Milestones Page 4