SE3020
Software Design Lab

Introduction

Please see the shared syllabus on Dr. Hasker's shared SDL page for an overview of the process.

For next offering: Point to se3020 syllabus instead of se3010 syllabus

In particular, please review the third Sprint guidlines on the Syllabus. This sprint is similar, but without the wrap-up activities: There is no presentation, no individual contribution report, and no peer evaluation this sprint.

Individual Meetings

Please schedule a meeting with me during Week 1 through Outlook. (See instructions linked from my schedule page). Please schedule a half-hour meeting and plan so that we can end early if possible. I will try to do likewise.

Deliverables

Closing PBIs

All PBIs must be closed by Monday evening of Break (December 2nd) (Yes! During break! If you want me to move the deadline up so you don't have to work over break, please ask.) Any PBIs closed after this date should be reported as incomplete in the sprint retro. This is especially important as you start to compute velocities next sprint.

Review and Retro

Please submit exactly ONE pdf per team containing both the review and retro in a single document. Please coordinate with your team to ensure that this document is submitted and that it is what the team wants submitted.

Please follow the document provided on Dr. Hasker's site. This site also includes markdown templates that could be helpful.

This sprint, the review and retro are due Week 4 Wednesday in esubmit.

For this sprint, give your feedback on the instructor and the course in the retrospective. Suggestions for improvement are particularly important early in the quarter.

Please submit the report as a PDF. The review/retro esubmit page is now posted.

Please reference PBI #'s when refering to PBIs in your report:

  • Include issue numbers and descriptions in the summary at the beginning of the report.
  • Include issue numbers and pull request numbers for the PRIMARY PBIs that you contributed to.
  • Include pull request numbers that you contributed in a SIGNIFICANT way to the review of

Also, when describing your contributions to pull requests, please clearly distinguish whether you created the pull request or contributed to its review.

Highlighted changes added 12 Dec 2019