This sprint, we will focus on design and process. Just as in Sprint 2, you should have a list of goals set in your planning documentation/system. Choose a set of those items to commit to and finish before the sprint’s end.

What to do

  1. You should continue to create a detailed plan recorded in GitHub Projects. There should be a recorded history of your finished tasks. Do not delete things when they are done. Mark them as accomplished!

  2. Read through some designs at OO Design's catalog of patterns and find one that fits someplace in your project. You are probably alreday using one without knowing it. Write a document in /doc/ that describes which design patterns you can find or fit in your setting. It’s valid that you may not be able to find any that you already use, but very unlikely that you cannot find an improvement to your design that incorporates one or more of the patterns. This document should be written in english with complete sentences and include:

    • an introduction with a description of the patterns you use currently,

    • a section that details a list of the patterns which may fit well into your design,

    • and a plan of how intend to continue designing modules.


  1. A marked set of tasks to be finished in this sprint updated in GitHub Projects

  2. Delivered code that meets those tasks

  3. A document, /doc/ explaining patterns seen in your project or that you will/have added.

  4. A docs/ document containing the minutes of your sprint ceremonies - TO BE DONE EARLY IN WEEK.


Out of 20:

  • (-[0,5]) Any outstanding issues from previous sprints are worth up to 5 points (25%!) off regardless of current cumulative score. You must fix outstanding issues.

  • (-[0,5]) Misuse of git or other tools

  • (-[0,5]) Any single group member not participating

  • (8) Design patterns document

    • (2) doc/ exists

    • (4) has a reasonable amount of information

    • (2) is formatted in markdown

  • (4) Github Projects is up to date

  • (8) Work towards the items changed in Github Projects has been accomplished.

    • (4) There should be a reasonable amount of code written

    • (4) The pull request system has been used