Senior Design
Due Dates

Due dates may vary from team to team. It is the team's responsibility to set and meet due dates for their deliverables each quarter. Due dates for other specific items are detailed below. Items are due 11pm the day before the team meets with its advisor. For example, if a team meets with its advisor at noon on Tuesdays, the project proposal is due 11pm, Monday of week 2.

Fall Quarter

Note: Each team must set the due date for the technology report and indicate this in the week 3 status report. Each team may have additional deliverables (depending on the project). Due dates for these should be specified in their week 3 status report as well.

Weeks 2, 3, 4, 5, 6, 7, 8, 9, and 10

Note: the week number associated with the status report should match the week of the quarter in which it was submitted. For example, the week 2 status report is due prior to the meeting with your advisor in week 2 and should discuss the progress made by each team member in the previous seven calendar days.

Week 2

Week 3

  • Definition of Done
  • Sprint 1 Plan (both Confluence page and PBIs with estimated tasks in Jira)

Week 6

A portion of the advisor meeting this week will be dedicated to a sprint review where the team will demonstrate the increment delivered at the end of the previous sprint. Another portion of this meeting will be to review the sprint 2 plan. Be sure to come to the meeting prepared to discuss your preliminary plan. Based on feedback from your product owner, there may be slight adjustments to the plan. If no adjustments are made, no additional planning should be needed.

Week 7

Week 9

Friday of week 10

We will not meet this week (I will be at a conference). All of these items are due at 11pm Friday of week 10.

  • Student Outcomes Portfollio
  • Peer Evaluation
  • Team reflections on how you have addressed each of the software engineering elements (Requirements, Software Architecture and Modeling, Design, Testing, Tools, Experimentation and Prototyping, Third Party Components, and Documentation)
  • In addition, all items due for the quarter have a hard deadline of 11pm Friday of week 10.

Note: Sprint 3 starts the day after sprint 2 ends. The remainder of week 10, finals week, and break week will all be part of the first week of sprint 3 which will end at 11pm the day prior to your winter week 1 advisor meeting. Based on the experience of prior senior design teams, it is suggested that students use the remainder of week 10 and finals week to complete the first third of sprint 3.

Winter Quarter

Note: The due dates for a number of deliverables must be determined by each team and included in the week 1 status report. These will include, but are not limited to, the following:

  • Documented software architecture
  • Test plans/results and software quality assurance

Weeks 1, 2, 3, 4, 5, 6, 7, 8, and 9

  • Status Reports (due 11pm prior to meeting with advisor in all but the last week of the quarter).

Week 3

The meeting will focus on the sprint 3 review and sprint 4 planning.

Week 6

The meeting will focus on the sprint 4 review and sprint 5 planning.

Week 8

Student Outcomes Portfollio

Week 9

The meeting will focus on the sprint 5 review and sprint 6 planning.

The end of the first week of sprint 6 is the day prior to the spring week 1 meeting with your advisor. You are highly encouraged to complete work associated with the first third of the sprint prior to leaving for break.

Friday of week 10

  • Presentation
  • Updates to team reflections on how you have addressed each of the software engineering elements (Requirements, Software Architecture and Modeling, Design, Testing, Tools, Experimentation and Prototyping, Third Party Components, and Documentation)
  • In addition, all items due for the quarter have a hard deadline of 11pm Friday of week 10.

Spring Quarter

Teams may choose to propose an alternative development process for the spring quarter. If approved, the due dates described below may not apply.

Note: The due dates for a number of deliverables must be determined by each team and included in the week 1 status report. These will include, but are not limited to, the following:

  • Completed software/hardware
  • User and installation manuals

In addition, each team will participate in the IEEE Milwaukee Section Larry Hause Student Poster Competition. This typically takes place a Thursday night in week 6, 7, or 8.

Weeks 1, 2, 3, 4, 5, 6, 7, 8, and 9

  • Status Reports (due 11pm prior to meeting with advisor in all but the last week of the quarter).

Week 3

The meeting will focus on the sprint 6 review and sprint 7 planning.

Week 5

Week 6

The meeting will focus on the sprint 7 review and sprint 8 planning.

Week 7

  • Final Version of Project Poster (due date may be moved earlier if the IEEE competition is scheduled earlier)

Week 8

Student Outcomes Portfollio

Week 9

The meeting will focus on the sprint 8 review.

Week 10 (due Friday 11pm)

  • Friday: Final Project Report
  • Friday: Peer Evaluation
  • Updates to team reflections on how you have addressed each of the software engineering elements (Requirements, Software Architecture and Modeling, Design, Testing, Tools, Experimentation and Prototyping, Third Party Components, and Documentation)
  • Friday: Personal Growth Evaluation

Week 11

  • Student Projects Show (10:30am-2:30pm Friday of finals week)

Last modified: Tuesday, 05-Sep-2017 04:04:20 CDT