Final Sprint #2 Progress Presentation

The purpose of this lab is to present your team's progress and get feedback. By accepting feedback from others, you can often get new ideas or be emboldened to try something new to improve. That is the fundamental goal of Agile and embodied in the Sprint Retrospective, considered by many to be the most important activity in Scrum.

Submission

As a team: use GIT to push your team's presentation files to the folder doc/presentation3 on the master branch of the provided, shared, ooga_teamNN repository using the commit message "lab_presentation3 - everyone's NetIDs".

As an individual: complete three copies of this feedback form, one for each other team's presentation, to help them improve their work (and yours based on other students feedback).

Team Requirements

Your presentation must be limited to 15 minutes using Zoom synchronously during the lab period with everyone from your team expected to be present your goals and progress since starting to implement the project.

Start by showing off the features of your running program:

• run the program from the master branch through a planned series of steps/interactions (including showing how bad data or interactions are handled)
  NOTE, as each feature is shown, someone on the team should briefly describe how work they did over the past week relates to it
• show example data files and describe how they are used within your program (focus on the file content rather than the code that uses it)
• show a variety of JUnit (at least 5) and TestFX (at least 3) tests (including both happy and sad paths) and discuss how comprehensively they cover the feature(s) and why you chose the values used in the tests

Then present what was learned during this Sprint and the implementation plan for the next Sprint:

• describe how much of the planned features were completed this Sprint and what helped or impeded progress (or if the estimate was just too much)
• describe two specific significant events that occurred this Sprint (one positive and one that caused issues) and what the team learned from each
• describe what worked regarding your teamwork and communication, what did not, and how Gitlab's project management features are helping in that regard (if at all)
• describe what evidence you have that your teamwork has improved so far and something specific that is planned for improvement next Sprint
• what features are planned to be completed for the final version (taking into account what was, or was not, done this Sprint), who will work on each feature, and any concerns that may complicate the plan

Materials developed specifically for your presentation can include files such as code, images, UML diagrams, or written text (using Markdown, Javadoc or a wiki page on Gitlab). PowerPoint slides are discouraged because they are completely separate from the project and unlikely to be maintained even if they are added to the repository, but here are some tools to convert Markdown to a slide style format.

Individual Requirements

When you are not on the team presenting, provide feedback that is focused on the content rather than the quality of the presentation itself (e.g., things you did not understand, felt were incomplete, or ideas you had to improve their work).

After each presentation, a few people will be asked to share their feedback synchronously while the remainder of the feedback will be sent electronically. You are especially encouraged to share things you intend to borrow for your own team (from their project design or features to their presentation style or teamwork ideas).