Week 7 Sprint Report

The sprint report is a concise summary of your team's activities, accomplishments, and challenges during the sprint. It helps in tracking progress, identifying issues, and planning future actions.

Steps for Completion

Update your Project Wiki with a dedicated page containing the following information. If you adopted the provided wiki repository, a template has been provided.

  1. Collect Information:

    • Coordinate with your team members to gather information about their completed tasks.
    • Ensure each member provides a brief summary and relevant links to their work artifacts (e.g., GitHub commits, Figma files, Google Docs, YouTube videos).

  2. Writing the Report:

    • Task Accomplishments:
      • For each completed task, write a one-sentence summary.
      • Include links to the artifacts or evidence of the completed work.
      • Format it in a tabular form with columns for 'Who', 'Link(s)', and 'Task Description'.
    • Challenges and Blockers:
      • Describe any challenges the team faced during the sprint.
      • Clearly mention any blockers, specifying who is affected and the nature of the blocker.
      • Do you need assistance with overcoming the blocker?
    • Plan for Next Week:
      • Outline the tasks and features your team plans to work on in the next sprint.
      • Assign tasks or features to specific team members when possible.
    • Additional Observations:
      • Include any other notes, observations, or reflections that are relevant to the sprint’s progress or team dynamics.

  3. Formatting and Clarity:

    • Ensure the report is well-structured and easy to read.
    • Use clear and concise language to convey information effectively.
    • Adhere to the provided template for consistency.

  4. Review and Submission:

    • Before submission, review the report as a team.
    • Ensure that all information is accurate and that every team member agrees with the content.
    • Submit the report as per the instructions and within the deadline.

The sprint report is a collaborative document. It should accurately reflect the team's collective efforts and challenges. Regular and honest communication within the team is key to preparing an effective sprint report. This report is not just a requirement but a tool for reflection and improvement. Engage with the process thoughtfully.

Evaluation Rubric

Completeness of the Sprint Report

  • Exceptional (5 points): The report thoroughly covers all required aspects, including detailed task summaries, complete links to artifacts, comprehensive description of challenges and blockers, and a clear plan for the next week. Additional observations or reflections are insightful and relevant.
  • Proficient (4 points): The report adequately addresses all key components with sufficient detail. Minor elements may be less developed, but the overall report is informative and useful.
  • Adequate (3 points): The report includes most required elements but may lack detail in some areas, such as incomplete task summaries or vague descriptions of challenges.
  • Needs Improvement (2 points): The report is missing significant details in multiple sections, such as incomplete lists of tasks, few or no links to artifacts, or a lack of clear planning for the next sprint.
  • Unsatisfactory (1 point): The report fails to address several critical sections, providing minimal or irrelevant information, making it ineffective as a sprint review tool.

Quantity of Work Completed

  • Exceptional (5 points): Demonstrates a high volume of work, with each team member contributing significantly. The tasks completed are substantial and indicate strong team effort and productivity.
  • Proficient (4 points): Shows a good amount of work completed, with most team members actively contributing. Tasks are relevant and align with project goals.
  • Adequate (3 points): Reflects a moderate amount of work, with some team members contributing more than others. Some tasks may lack in significance or impact.
  • Needs Improvement (2 points): Indicates a below-average volume of work, with minimal contributions from team members. Tasks completed are not sufficient for the sprint’s objectives.
  • Unsatisfactory (1 point): Shows very little work completed, with few contributions from team members. The quantity of work is insufficient for project progress.

Writing Quality (The 7 Cs of Communication)

  • Exceptional (5 points): The report is exceptionally well-written, demonstrating clarity, conciseness, concreteness, correctness, coherence, completeness, and courtesy. The writing is engaging, well-organized, and free of errors.
  • Proficient (4 points): The report is well-structured and clear, adhering to most of the 7 Cs. It may have minor errors or lapses in one or two of the 7 Cs but remains effective in communication.
  • Adequate (3 points): The report meets basic standards of the 7 Cs but may have issues with conciseness, concreteness, or minor grammatical errors. The writing is functional but not exemplary.
  • Needs Improvement (2 points): The report has several issues in clarity, coherence, or correctness. Writing quality detracts from the report's effectiveness, with multiple errors or structural issues.
  • Unsatisfactory (1 point): The report demonstrates poor writing quality, lacking in several aspects of the 7 Cs. The document is difficult to understand, poorly organized, and contains numerous errors.

Total Possible Points: 15

Submitting Your Work

Your work must be submitted Anchor for degree credit and to Gradescope for grading.

  1. Export a copy of your Sprint Report as a PDF.
  2. Upload the PDF to Gradescope via the appropriate submission link for the course.
  3. Upload the PDF to Anchor using the form below.

Note: Anchor submissions can occur at any time during the term, but it is critical that you upload all of your work to Anchor before the last day of the term. Gradescope submissions must be submitted before the deadline (or the late deadline, if applicable).