Deliverables
Guidelines
The
project deliverables have been broken down in "logical"
sets. We cannot impose a micro-schedule that would be applicable
to all the teams. You have to be in charge of planning the
delivery of the various artifacts. However, you have to turn
in the set, at the latest, by the due date listed on the class
schedule. You are free to deliver the corresponding set before
the date listed. If you think that your team cannot meet the
deadline for a given set, you have to notify the Teaching
Assistant, at least 1 week in advance, with a valid justification
for the delay. Last minute requests for extensions will be
ignored, and will lead to significant deduction in the number
of points assigned to that set. Consecutive requests for extensions
will also be ignored.
IOC
Working Set
Assigning points to the Construction Set is done for the first
(#1) and last (#n) iterations. You should deliver one construction
set at the end of each iteration. We expect teams to have
between 2-3 iterations, and the points will be divided accordingly:
One iteration is not acceptable. More than 3 iterations may
be overkill.
It
appears as if the "working system" doesn't get any
point. This is not the case. If by the end of the semester,
you do not have a "working" system, you will not
get more than a certain percentage (to be determined by many
factors) of the total points assigned to the Construction,
Transition and Support Set. You are expected to "plan
the flight, and fly the plan". You are mostly following
a design-to-schedule approach: however, if you start significantly
and unexpectedly scaling down the planned capabilities (which
you should have thoroughly identified by the rebaselined LCA),
due to poor project planning or management, your grades on
the Iteration Plans, and Iteration Assessment Reports will
be adversely affected. Similarly, Iteration Plans and Iteration
Assessment Reports that misrepresent the current state of
the Construction will receive very low grades. |
