Teams must use Scrum. The Product Owner will provide a set of prioritized features for each sprint (i.e., a product backlog). During the sprint planning meetings, your team must determine which features (i.e., stories) will be included in the sprint backlog and create tasks and acceptance criteria for each.
Each team member must use the required tool set.
Note that you must use Java v17 (not higher). If you have installed
a higher version, your code must not use features beyond those in v17
and you must cross-compile your code so that the .class
files are consistent with v17. (See
the
CS Wiki for help.)
Your source code (other than test suites) must not contain any style defects.
Your JUnit tests must be in a package named testing
and each test class must include the word "Test" in its name.
Your final grade on the project will be based on: your team's grades on each sprint, the improvements your team made to the process it used, your individual grades on each sprint, and your assessments of each other (which you will submit at the end of the process).
The process I will use when determining your final grade on the project will be somewhat subjective. I will not use a specific formula or set of weights when calculating final grades. However, the grades you and your team receive on the individual sprints will give you a good idea of the grade you will receive on the final project.
Before the start of class on the day of the final product review you must submit several deliverables. For more information, see the following document:
Copyright 2024