Class Meetings
We will be using our weekly class time for team meetings and progress updates. If you are sick or are otherwise unable to attend a meeting, please let your team and me know before class. If you're able and can get a message to me with enough lead time, it may be possible to join via Microsoft Teams. Please do not physically come to class if you are sick, since you risk making the rest of your team sick!
Scrum Meeting
Each Sprint will start with a Scrum meeting. At the beginning of classes that have Scrum meetings, we will all discuss the applications and general plans for the upcoming Sprint. Each team will then meet separately to develop a strategy for working on the Sprint.
Scrum meeting dates are:
- September 2nd
- September 16th
- September 30th
- October 14th
- October 28th
Sprint Presentation
At the midpoint of each Sprint, we will use the class meeting time for everyone to give a brief, informal update about their individual progress on the current Sprint. Plan to give a concise, 2-minute summary of what you're doing and what challenges you're encountering. The purpose of this presentation is to keep everyone up to date with the ongoing work on each project. Since more than one team might be working on the same application, maintaining awareness of what other teams are doing is important.
Sprint Presentation dates are:
- September 9th
- September 23rd
- October 7th
- October 21st
- November 4th
Catch-Up/Wrap-Up Meetings
In the event of unforeseen interruptions (illness of team members, hurricane, etc.), we may have to adjust scrum and presentation meetings for the class or for some teams. If all goes well, we will instead use these dates for wrap-up meetings to identify work that still needs to be done on the applications.
These dates are:
- November 11th
- November 18th
Final Meeting
At the end of the course, each team will give a short (3-5 minute) presentation summarizing what the team accomplished during the Discovery Phase. This presentation is scheduled for class time on December 2nd.
Sprint Report
You will submit a Sprint Status Worksheet at the end of each Sprint. The purpose of this worksheet is to document the work you completed during the Sprint. Remember that measurable, verifiable results are required to show adequate progress in this course. Be sure to generate measurable artifacts (like documentation, test cases, test results, etc.) for activities that are not directly measurable (such as reading, watching tutorials, or doing research).
Submission Requirements
For each Sprint, each person needs to download and complete the following Sprint Status Worksheet. To ensure that your browser downloads the worksheet instead of trying to open it, right-click the following link and choose "Save As," "Save Link As," or similar language from the context menu:
Follow the instructions provided in the worksheet in order to complete it. Export your completed worksheet to PDF format. Upload the PDF document as the submission for the Moodle assignment activity for the corresponding Sprint.
Documentation for worksheet preparation is available for LibreOffice and Microsoft Word Online:
ABET Assessment
This activity supports the following ABET performance indicators:
- PI 1.4: Identify solutions to a problem by applying principles of computing and/or other relevant disciplines. [SLO 1]
- PI 1.6: Analyze a component of a complex problem. [SLO 2]
- PI 2.2: Implement a solution to meet requirements. [SLO 4]
- PI 2.3: Evaluate (a) solution(s) against requirements. [SLO 3]
- PI 3.1: Communicate with clarity. [SLO 6]
- PI 5.2: Participates in group activities according to expectations. [SLO 5]