SE3030
Software Design Lab

Introduction

Since sprints are three weeks long, there is one additional week that does not fall during a sprint. This quarter, we will place this week in Week 10 and use it for course wrap-up.

Requirements

These activities (listed on the main syllabus) must be completed during the week:

  • Submit your individual contribution report. (Due Week 10 Wednesday. Monday of Finals Week.)
  • Submit your peer evaluations. (Due Week 10 Wednesday. Monday of Finals Week.)
  • Submit your Sprint 3 review and retro. (Due Week 10 Wednesday).
  • Meet with the product owner and identify priorities for the next year, if applicable. Be especially careful to identify when the system can be published for more general use, at least as a prototype.
  • Review the project's Readme file and other documentation to ensure each document is current. This is expecially important in the last sprint of the year!
  • Complete any outstanding PBIs or strengthen testing as appropriate.
  • Perform exploratory testing and document standing issues.

Individual Contribution Report for the quarter

This is a contribution report summarizing the entire quarter. Each student should prepare their own report and submit it to esubmit separately.

Please follow the detailed instructions found on Dr. Hasker's page.

Please submit the report as a PDF.

Peer Evaluations

Please submit the peer evaluations through the link found in the Canvas assignment.

Optional Week 10 Development Activities Report

There is no deliverable due for any Week 10 development activities the team may perform. If your team completes any major PBI work during this week, you may wish to reflect it in your review and retro for Sprint 3, or if the work is completed after Wednesday, email me an optional report on the work accomplished. Individuals may also wish to update their contribution reports within esubmit. If you do so, please include a Canvas comment on the changes you made from your previous submission so I don't miss the update.