SE3010
Software Design Lab

Introduction

In this sprint, you will define the scope of your project through the develepoment of mock-ups and explore key technologies through individual technical spikes.

Please see the shared syllabus, in particular, Weeks 1-4 on the schedule, as these give detailed instructions for the first sprint.

Deliverables

Closing PBIs

All PBIs must be closed by Monday evening of Week 5 (5 Oct 2020).

Individual Technology Spikes

Each student should arrange a half-hour individual meeting with the instructor, preferably during the last week of the Sprint (Week 4), but also possibly during the week that follows (Week 5). These do not need to be demoed to the product owner. Please send me an Outlook invitation during a free time on my schedule.

If you anticipate not being able to complete your technical sprint, please contact me at the beginning of Week 4 to arrange details.

By Monday of Week 5 (This deadline is required even if you plan to demo in Week 5) each student will submit a brief report documenting:

  • the goal
  • technologies tried and used
  • how to build the system and test that it works
  • lessons learned

This report will be submitted to esubmit as a PDF.

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.

You may omit any aspects of the report that have no application. For example, in the first sprint, there is no need to talk about improvements you made to your process during the sprint.

Your review and retro document should include screenshots or photographs of your storyboards, low-fi mockups, and high-fi mockups (see Weeks 2-4 in the main syllabus.)

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 5 Wednesday (7 Oct 2020) in esubmit.

Please submit the report as a PDF. the esubmit page is TBA.

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, if applicable, pull request numbers) for the primary PBIs that you contributed to in your individual summary of contributions.
  • If applicable, include pull request numbers that you contributed in a significat way to the review of in your individual summary of contributions.

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

Page posted 10 Sept 2020