Skip to assignment content

CS357: Foundations of Artificial Intelligence - Intra-Team Check-In (3 Points)

Purpose, Task, and Criteria

Purpose: To pause as a team, say honestly what shipped and what is at risk, and capture what this team has learned about working together.

Task: Submit one signed team progress report on the form in the Project Thread, and each submit a private team-health pulse.

Criteria: I assess the report's specificity, your answers to the stage prompts, and whether every member signed and sent a pulse. The rubric below breaks it down.

Assignment Goals

The goals of this assignment are:

  1. To report progress and risk honestly as a team (Goal 13)
  2. To use the check-in to improve how the team works (Goals 13, 15)

The Assignment

Use the form and the stage prompts under Intra-Team Check-Ins 1-3 in the Project Thread. Submit one signed report for the team, and each member submits their own pulse privately. Each check-in carries 3 points, assessed within Final Project and Project Thread Milestones.

Submission

In your submission, please include answers to any questions asked on the assignment page, as well as the questions listed below, in your README file.

If you wrote code as part of this assignment, please describe your design, approach, and implementation in a separate document prepared using a word processor or typesetting program such as LaTeX. This document should include specific instructions on how to build and run your code, and a description of each code module or function that you created suitable for re-use by a colleague.

In your README, please include answers to the following questions:

  • Describe what you did, how you did it, what challenges you encountered, and how you solved them.
  • Please answer any questions found throughout the narrative of this assignment.
  • If collaboration with a buddy was permitted, did you work with a buddy on this assignment? If so, who? If not, do you certify that this submission represents your own original work?
  • Please identify any and all portions of your submission that were not originally written by you (for example, code originally written by your buddy, or anything taken or adapted from a non-classroom resource). It is always OK to use your textbook and instructor notes; however, you are certifying that any portions not designated as coming from an outside person or source are your own original work.
  • Approximately how many hours it took you to finish this assignment (I will not judge you for this at all...I am simply using it to gauge if the assignments are too easy or hard)?
  • Your overall impression of the assignment. Did you love it, hate it, or were you neutral? One word answers are fine, but if you have any suggestions for the future let me know.
  • Using the grading specifications on this page, discuss briefly the grade you would give yourself and why. Discuss each item in the grading specification.
  • Any other concerns that you have. For instance, if you have a bug that you were unable to solve but you made progress, write that here. The more you articulate the problem the more partial credit you will receive (it is fine to leave this blank).
  • Please describe any use of outside resources you may have engaged in the completion of this assignment, including the use of generative Artificial Intelligence.

Assignment Rubric

Description Pre-Emerging (< 50%) Beginning (50%) Progressing (85%) Proficient (100%)
Progress Report: shipped, next, and current risks (40%) The report is missing, or it has no specific content. All three sections are present, but they stay general, with no named work or risk. Each section names specific work or risks, though a risk has no plan or an item has no owner. Each section is specific and honest: it names what shipped, what is next and who owns it, and each risk with what the team will do about it.
Stage Prompts: the three prompts for this check-in (30%) The prompts are not answered. One or two prompts are answered, or the answers could describe any team. All three prompts are answered with something that happened on this team. All three prompts are answered with concrete examples, and at least one answer says what the team will change or keep because of it.
Signatures and Pulse: every member signed, and every member sent a private pulse (30%) No signatures, and no pulses. Some members signed or sent a pulse. Every member signed, but a pulse is missing or late. Every member signed the report, and every member submitted a pulse on time.

Please refer to the Style Guide for code quality examples and guidelines.