CSE 4316 - Schedule, Deliverables, and Deadlines

All deliverables must be submitted via Blackboard. No scans of handwritten documents are allowed.

Deliverables submitted late will be penalized, at a rate of 10% of the maximum score per hour. The submission time will be the time shown on Blackboard. Any assignment submitted more than 10 hours late will receive no credit. Exceptions will only be made for documented emergencies, in strict adherence to UTA policy. Computer/network crashes are NOT an acceptable excuse for late submissions (if worried, submit early, you can always revise your submission till the deadline).

Itemized list:

• Deliverable 1 (individual): Due at 11:59pm on Tuesday, 8/27. A short paper about yourself and your goals.

• Topic for Wednesday, 08/28: Building a Team.
  Readings: Chapter 12 (Teamwork), Chapter 13 (Team Structure), including these case studies:
  • Case study 12.1, textbook pp. 274-275.
  • Case study 12.2, textbook pp. 277-278.
  • Case study 12.3, textbook pp. 282-283.
  • Case study 13.1, textbook pp. 297-299.
  • Case study 13.2, textbook pp. 315-316.

• Teams announced on Friday, 8/30.

• Deliverable 2 (team): Due at 11:59 on Tuesday, 09/03. For each of the projects discussed in class on Friday 8/30, indicate the team's thoughts and preferences. Optionally, discuss other project ideas you may have, and also indicate the team's thoughts and preferences on those. Be ready to discuss these thoughts and preferences in class on Wednesday.

• Topic for Wednesday 09/04: Building a Plan.
  Readings: Chapter 7 (Lifecycle Planning), including these case studies:
  • Case study 7.1, textbook pp. 134-136.
  • Case study 7.2, textbook pp. 159-161.

• Deliverable 3 (team): Due at 11:59pm on Thursday, 09/05. Individual skill assessment forms for all teammates, and team skill assessment form. Use this template for individual team assessment. Use this template for team skill assessment. Be ready to discuss the team's strengths and weaknesses in class on Friday.

• Topic for Friday, 09/06: Estimation.
  Readings: Chapter 8 (Estimation), Chapter 9 (Scheduling), including these case studies:
  • Case study 8.1, textbook pp. 164-165.
  • Case study 8.2, textbook pp. 199-202.
  • Case study 9.1, textbook pp. 229-230.

• Projects will be assigned to teams by Wednesday, 9/11.

• Topic for lecture on Wednesday 09/18: Classic Mistakes.
  Readings: Chapter 3 (Classic Mistakes), including this case study:
  • Case study 3.1, textbook pp. 29-37.

• Recurring deliverables, every week, starting Thursday 09/19.
  • By Thurday 11:59pm: submit an individual status report on Blackboard. This report should be a SINGLE document, that includes:
    • What your team asked you to do for the project this past week.
    • Specific times that you worked on this project, and what was done during each time period.
    • The total time you have worked on the project this last week.
    • An executive summary of what you accomplished this past week for the project.
    • A preview of what you plan to do next week for the project.
  • By Thurday 11:59pm: submit a team status report. One submission per team. This report should be a ZIPPED file containing these documents
    • A recent version of your Microsoft Project file.
    • Slides for a team presentation, describing progress for the past week, plans for the next week, and any other important developments/issues with the project. You should explicitly specify what the team overall has accomplished, how much time each individual spent on each task, how much time each individual spent in total for the last week, and what each individual accomplished. The presentation should include a single slide that lists all team members, and specifies how much time each team member spent on the project over the last week.
  • Friday, in class: team presentation (0-20 minutes) based on the slides you have submitted.

• Topic for lecture on Friday 09/20: Risk Management.
  Readings: Chapter 5 (Risk Management), including these case studies:
  • Case study 5.1, textbook pp. 82-83.
  • Case study 5.2, textbook pp. 103-105.

• First draft of System Requirements Specification (SRS): Submit on Blackboard, one per team. Due at 11:59pm on Tuesday, 09/24.

• Topics for lecture on Wednesday, 09/25/2012: Feature Set Control, and Productivity Tools.
  Readings:
  • Chapter 14 (Feature Set Control), including this case study:
    • Case study 14.1, textbook pp. 342-343.
  • Chapter 15 (Productivity Tool Deployment), including these case studies:
    • Case study 15.1, textbook pp. 346-347.
    • Case study 15.2, textbook pp. 368-369.

• SRS Gate Reviews: A presentation of 0 to 45 minutes on each team's SRS document, followed by discussion with the rest of the class.
  • Submit presentation on Blackboard, one per team. Due at 11:59pm on Thursday, 09/26.
  • Present in class on Friday 09/27. If there is not enough time for all teams to present Friday 09/27, presentations will continue Wednesday 10/02.

• Topic for lecture on Friday 09/27: Project Recovery.
  Readings: Chapter 16 (Project Recovery), including these case studies:
  • Case study 16.1, textbook pp. 372-373.
  • Case study 16.2, textbook pp. 385-387.

• Second (and hopefully final) draft of System Requirements Specification: Submit on Blackboard, one per team. 11:59pm on Tuesday, 10/08.

• First draft of Architecture Design Specification (ADS): Submit on Blackboard, one per team. Due date (may be moved earlier): 11:59pm on Tuesday, 10/22.

• ADS Gate Reviews: A presentation of 0 to 45 minutes on each team's ADS document, followed by discussion with the rest of the class.
  • Submit presentation on Blackboard, as part of your weekly team status report. Due at 11:59pm on Thursday, 10/24.
  • Present in class on Friday 10/25. If there is not enough time for all teams to present Friday 10/25, presentations will continue Wednesday 10/30.

• Second (and hopefully final) draft of Architecture Design Specification: Submit on Blackboard, one per team. Due date: TBA.

• Detailed Risk Analysis: Identify the individual components in your project, and the potential risks for each of the components. Describe the magnitude of these risks, in terms of probability and estimated impact, and outline how you plan to address those risks. Submit on Blackboard, one per team. Due date: TBA.

• Teammate Assessment: Evaluate each one of your teammates, as well as yourself. Fill out, for each person you evaluate, the teammate assessment form available from our documents and forms web page. Submit on Blackboard, one per person. Due at 11:59pm on Tuesday, 12/03.