The following is a timeline of the Senior Project activities associated with the tasks that all teams are required to do. Your project will also have a project plan in parallel with this timeline that details the tasks which are required for the development of your particular project. These later tasks are the ones of most concern to your project sponsor. To receive high marks on senior project, the team must deliver excellent quality work for both the project-specific tasks and these common tasks.

Fall
Team Activities and Deliverables
Week 1
27 Aug
  • Attend Senior Project Expectations and Meet Your Faculty Coach session.
  • Hold project kick-off meeting with the project sponsor this week or next week.
    • Get enough detail concerning the project to write the project synopsis.
  • Decide on a team name.
  • Begin tracking team time/effort.
  • Deliverables
    • Submit request to SE System Administrator to create team account providing: team name, login-ids of each team member and faculty coach.
    • If you need to have a virtual machine for development work, you can also request that from the system administrator. You will get a bare machine and have to install the tools and frameworks that your project will use.
Week 2
3 Sep
Labor Day (no classes on Monday)
  • Hold project kick-off meeting, if not held in Week 1.
  • Start regular weekly interactions with project sponsor.
  • Deliverables
    • Start project website on an se.rit.edu machine.
    • Inform faculty coach and project sponsor of the URL for the project website.
    • As you understand your project better, you can also request a virtual machine for your development work, or to setup a deployment environment.
    • Publish, on project website, first tracking report of time/effort worked.
Week 3
10 Sep
  • Get approval of project synopsis.
  • Discuss overall project plan with sponsor.
  • Discuss development process options with the sponsor.
  • Begin detailed project discussions.
  • Deliverables
    • Submit project synopsis of no more than 250 words to sponsor and faculty coach for approval.
    • Publish, on project website, team information including approved synopsis.
    • Complete project information survey form.
    • Submit first draft of development process and project plan for review by faculty coach and sponsor.
Week 4
17 Sep
  • Continue discussion of development process and project plan, if needed.
  • Specify development methodology.
  • Specify product/process metrics to be tracked.
  • Deliverables
    • Document development methodology on project website.
    • Document product/process metrics on project website.
    • Domain model on project website.
Week 5
24 Sep
 
Week 6
1 Oct
 
Week 7
8 Oct
Mid-term break week (no classes on Monday and Tuesday)
  • Discuss sponsor's attendance at the interim presentation.
  • Deliverables
    • Mid-term peer evaluation
Week 8
15 Oct
  • Mid-term project review with sponsor and coach
  • Deliverables
    • Interim presentation scheduled
Week 9
22 Oct
  • Motivated by the mid-term project review and peer evaluations, discuss with faculty coach adjustments individual team members and the team will make.
Week 10
29 Oct
 
Week 11
5 Nov
 
Week 12
12 Nov
 
Week 13
19 Nov
  • Deliverables
    • Draft interim presentation
Thanksgiving break (no classes on Wednesday, Thursday, and Friday)
Week 14
26 Nov
  • Give interim presentation this week or next week
  • Attend required interim presentations
Week 15
3 Dec
  • Give interim presentation this week, if not done last week
  • Attend required interim presentations
  • Discuss sponsor's possible attendance at interim reflection meeting
  • Deliverables
    • Iterim presentation evaluations for presentations attended
    • Individual end-of-term peer evaluations
    • Interim team self-assessment
    • Project website up-to-date with all project artifacts, tracking reports, etc.
    • Course evaluation
Week 16
10 Dec
through Finals
  • Attend interim reflection meeting
  • Deliverables
    • Summary of interim reflection meeting
   
Spring
Team Activities and Deliverables
Week 1
14 Jan
  • State-of-the-project discussion with sponsor and coach
  • Deliverables
    • Project plan updated for second term
Week 2
21 Jan
Martin Luther King Day (no classes on Monday)
Week 3
28 Jan
 
Week 4
4 Feb
 
Week 5
11 Feb
 
Week 6
18 Feb
 
Week 7
25 Feb
  • Coordinate with sponsor for attendance at final presentation
  • Deliverables
    • Mid-term peer evaluation
Week 8
4 Mar
  • Attend How to Make a Poster session (Tuesday, 5 March)
  • Mid-term project review with sponsor and coach
  • Deliverables
    • Final presentation scheduled
11 Mar Spring break
Week 9
18 Mar
  • Motivated by the mid-term project review and peer evaluations, discuss with faculty coach adjustments individual team members and the team will make
  • Deliverables
    • Project poster concept
Week 10
25 Mar
  • Deliverables
    • Preliminary project poster
Week 11
1 Apr
  • Deliverables
    • Project poster delivered to Senior Project Coordinator
Week 12
8 Apr
  • Deliverables
    • Poster presentation during Software Engineering Project Day
    • Draft final presentation
Week 13
15 Apr
  • Give final presentation this week, or next week
  • Attend required presentations
Week 14
22 Apr
  • Give final presentation this week, if not given last week
  • Discuss sponsor's possible attendance at final reflection meeting
  • Attend required presentations
  • Deliverables
    • Technical report outline
Week 15
29 Apr
through Finals
  • Attend final reflection meeting
  • Deliverables
    • Presentation evaluations for presentations attended
    • Draft technical report
    • Individual peer evaluations
    • Final project artifacts
    • Final technical report
    • Team final self-assessment
    • Summary of Project Reflection meeting
    • Project website and repository on an se.rit.edu machine up-to-date with all project artifacts, tracking reports, etc.
    • Course evaluations
    • Summary of final reflection meeting
    • Senior survey