lect18

lect18, Tue 06/01

Work Towards Code Freeze, Ethics of SW Development

Announcements

Full focus on finalizing your product!

Ethics

Slides on the Ethics of Software/Technology Development

Remaining Schedule Reminder:

Code Freeze for your projects will be end of the day this Friday: Friday, June 4th!
All documentation and the presentation video will be due at the end of Tuesday, June 8th.
Project presentations will take place, as long announced and planned, during the final exam slot, June 10th, 4-7pm.

Here, again, is the class grading scheme including the agreed-upon point percentage breakdown for grading the “Final Product” 40% of the course grade:

25% Homeworks
35% Lab Points (including lab09 this week)
40% your final project

Final Project Grading Dimensions:

15% Presentation
5% Idea, and Idea Refinement
25% Functionality, Quality (Reliability & Polish)
- judged by review of demonstration, user manual, peer review, teaching team testing
10% Technical Difficulty Implemented
- judged by review of code/scope taking into account team background/experience etc.
20% Implementation
- judged by review of Github code, PRs, etc.
- use the README.md to make clear the repository structure and guide through implementation effort!
15% Design Process
- judged by Design Document, Kanban Board, Meeting Logs, Github TEAM information, etc. Design Document should steer through the process.
10% Manual

Briefly: Some Lessons Learned

In our teaching team meetings, the staff share some of the lessons learned. We ask you to think of some as well, so that we will have some collective wisdom for future iterations of this class. A few examples to stir your imagination:

During a rebase, just rebase. Don’t make changes (i.e. fix bugs, add features) during a rebase. Only focus on fixing merge conflicts. Make your changes to fix bugs or add features before the rebase, or after the rebase, but not during.
Making sure to listen to your team mates and give everyone a chance to feel like they are a part of the team, because the internal team work and how everyone contributes is crucial to the team’s effectiveness and success.

Let’s take a moment: what are some other lessons you’ve learned this quarter? Please type them type them into the #lessons_learned channel now open in Slack!

ESCIs (Course Evaluations)

You are likely getting many reminders from the automated system about course evaluations (ESCIs). I would like to also remind you to please take a moment before the deadline on Friday June 4th to enter your feedback about the course. It is very important for the university to evaluate the quality of instructor’s teaching (Question A) and the overall quality of the course (Question B).

A project-oriented course such as CS148 emphasizes learning by doing and the experience of working in teams over lectures and traditional exams and homeworks. If you see value in that approach, please do consider mentioning it as there are always debates on the future structure of the curriculum.

Response rate as of 10:00am 06/01/2020:

Course ID	Enrollment Count	Surveys Completed	Percent Completed
CMPSC 148	39	7	17.95%

So please, please, please fill in your evaluations!

Thank you all for taking the time (especially after so many peer eval questionnaires! :))

Today: Work Towards Code Freeze

Standup
Team-based Coordination and Development