CS375: Software Engineering - Weekly Standup Reflection (10 Points)

Assignment Goals

The goals of this assignment are:
  1. To self-reflect upon your individual contributions to the group
  2. To plan individual and group activities for the upcoming sprint
  3. To ensure that work aligns with your Gantt chart and does not overlap the efforts of another.

The Assignment

What to Do

In the self-reflection, you are to periodically comment on these areas:

  1. Your individual contributions during the prior sprint
  2. Your planned individual contributions during the upcoming sprint
  3. Any technical challenges that you face that are preventing you from achieving your planned contributions to the group
  4. Any areas for personal and professional development that would better enable you to meet your planned contributions on-schedule
  5. Was your group able to produce a prototype for this sprint, or to synthesize existing prototype(s) into a polished design? If so, describe this here.
  6. Provide a screenshot of your Kanban that reflects your Gantt chart tasks and the current state of those tasks. If the Gantt chart does not already assign a point person to each task, indicate that on your reflection report here.

Your discussion of prior and planned individual contributions should align with the project plan and Gantt chart. They should be generally on-schedule, or a group-led revision to the schedule should take place and be documented. In addition, these contributions should not overlap with the claimed contributions of others. In other words, you should comment on what, specifically, you accomplished during the past sprint (and what you plan to accomplish during the upcoming sprint).

Submission

In your submission, please include answers to any questions asked on the assignment page in your README file. If you wrote code as part of this assignment, please describe your design, approach, and implementation in your README file as well. Finally, 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).

Assignment Rubric

Description Pre-Emerging (< 50%) Beginning (50%) Progressing (85%) Proficient (100%)
Self Reflection (100%) The contributions, plans, or reflections are unclear or missing The self reflection indicates a summary of individual progress in the prior sprint that overlaps with the contributions of another. The self reflection indicates a summary of individual activities for the upcoming sprint that overlaps with the contributions of another. The reflection does not thoughtfully comment on technical challenges and areas of personal development. The self reflection indicates a summary of individual progress in the prior sprint that does not overlap with the contributions of another. The self reflection indicates a summary of individual activities for the upcoming sprint that overlaps in minor ways with the contributions of another that can be resolved in a stand up meeting. The reflection includes a thougtful discussion of technical challenges and areas for personal development. The self reflection indicates a summary of individual progress in the prior sprint that does not overlap with the contributions of another. The self reflection indicates a summary of individual activities for the upcoming sprint that does not overlap with the contributions of another. The reflection includes a thougtful discussion of technical challenges and areas for personal development.

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