1     Organization and Formatting

1.1    General (same as for other B-Sheets; follow this link for easy reference)

1.2    Sheet-Specific — Making it All Fit

The table of contents is fixed in terms of its entries.  Therefore, there should be no need for it to increase in size.  It should also not be decreased in size.  It should also remain in the exact position as received.  There should be plenty of room in the box/area/space provided for the Project Milestones to list the milestones.

Correct-Content Reminder:  Milestones should be major accomplishments, not only “syllabus items,” and definitely not every little step along the way; for instance, the PUD-related milestone would likely be “Problem Understanding Document delivered/released to customer” and not have all the internal submissions as milestones (or sub-milestones, which is not an actual thing).  Note here that your customer does not know all the acronyms, so spell them out here (and put the acronym in parenthesis if you wish to refer to it later by that acronym).  The focus should be on accomplishments over and above the PUD, CSR, PCR, etc.

2     Content Presentation

• There is no specific Page Input textbox/content to be addressed for this page.
• In the pre-titled Project Milestones box, present the milestones.
  • At the Problem Understanding Document (PUD) stage, this includes the customer release of major known deliverables provided in the course schedule (see Canvas course modules) and (more so) other major accomplishments you anticipate/foresee at this point — a couple examples (among others!) to get you thinking: “main system functions defined” and “final system-level solution chosen” and…
  • At the Concept Selection Review (CSR) stage, all Term-I milestones must be identified and documented and you should have a good cut at Term-II milestones as well. A couple Term-II milestone examples (among others!) to prime your thinking: “major components ordered” and “function-level and subsystem testing completed” and …
  • At the Project Continuation Review (PCR) stage, all Term-II milestones must be identified and documented here.
• Present the milestones as follows:
  • Use any desired (hopefully effective) format; tabular might be a good choice (a bullet-point list is in the template, but by no means is that required as the format nor considered the best, just a placeholder).
  • Include target date (such that you adhere to the course schedule and weekly accomplishment targets and goals) and the actual achieved date (to be entered once achieved) for each.
  • The project timeline found in the project brief can be helpful, but copy and paste of it is not acceptable — that is a timeline an much of what is in that table/timeline are not actually milestones! (more than a couple teams have done this, so it has to be stated)
  • Prior to achieving a milestone, keep a space/placeholder for entering the achieved dates as they are achieved — as indicated, the milestone list will continue being refined/updated over time, such as at the CSR and the PCR.
• There is no specific Page Output textbox/content to be addressed for this page.

3     Examples of Great Work

Do a great job and be the first!