Expectations for Weekly Demos

Here are what we would like to see from you for the weekly (Monday) demos.

Journal entries (individual)

Each team member should have an issue in the group’s issue tracker. Each week, each team member should add at least one comment to this issue to document his or her work for the week.
Each weekly entry should contain a list of the following:

• Links to issues that were created/opened by you
• Links to issues that were closed by you
• Links to each commit made by you

Please format your entry as a bulleted list.

You can create a link to a commit by pasting the first 8 (or so) hex digits of its hash code.

Your journal entries should be complete by midnight on Sunday (so we can use Monday morning to read your entries.)

Demo (individual)

Each class meeting, we will talk to each student individually. Your job is to very briefly (1-2 minutes) demonstrate what you worked on during the previous week, and how your efforts are contributing to the overall success of the project. When we meet with you, you should pick perhaps two or three of your most important contributions (as documented in your journal entry for the previous week).

Ways that you can demonstrate progress include

• Requirements, analysis, and design artifacts: During the early stages of the project, documenting requirements, modeling the problem domain, and developing a system design to meet the requirements are very important in order to create a solid foundation for your system. In addition, as you iterate later in the semester, it is useful to update parts of the requirements and analysis/design models in order to support further progress towards meeting the system requirements.
• Working, tested, integrated code: Assuming that your group has a solid design, this is generally the most important type of contribution.
• Prototype code: A standalone proof-of-concept demo is fine, especially in the early stages of the project. However, all such work needs to be integrated into the main codebase in a timely manner.
• Equipment/apparatus: If your project has external equipment or apparatus, then you can show us progress on its construction and setup. However, time spent on equipment/apparatus should be the mininum necessary to support the needs of the software you are creating.

Team meeting

In addition to the individual meetings, we will generally meet with each group as a whole to discuss overall progress.

Evaluation

For each weekly demo, you (individually) will receive one of the following evaluations:

• Exceeds expectations: We think you are making an extraordinary contribution to your project, and that overall, your team is on course to have a very strong final progress.
• Meets expectations: We think you are making an adequate contribution to your project, and that your team is on track for a solid (but perhaps not exceptional) final product.
• Below expectations: We are concerned that you are not making a sufficient contribution to your team’s project, and that your team’s final product will not meet the minimum expectations.