Assigment #7: Progress report + Third Sprint Plan
In class, you will show me the status of your milestone 2 features (with respect to the done criteria of your second sprint plan), after which you will update their status in the Requirements document.
Individually, let me know how much time you spent thus far on the project in general (and in particular the second sprint), and how much time you plan to spend on the third sprint. This includes meetings with your project partners inside and outside of class, and any activity in support of the project, including research and documentation.
As a group, hand in a report that discusses:
- progress, issues/risks, outcomes (testing and documentation as per the done criteria, including rationales for design decisions, at least one of which was informed by experimentation or by scholarly research), and next steps:
- Third Sprint Plan:
- What are the goals for the third sprint? Create a list (backlog) of user stories (at least for the third sprint, corresponding to the milestone 3 features of the requirements document): A short description of functionality from the user's perspective:
| As a... |
I want... |
so that... |
| type of user |
some desired outcome |
some reason |
| another type of user |
another desired outcome |
another reason |
| ... |
... |
... |
- Technology choices (hardware and software) and tools for program development (design, implementation, testing, version control, etc).
- Provide rationale for all decisions.
- Done criteria: how will you know when your features are done?
Each sprint ends with a potentially shippable product.
- Testing level:
- Which 2 or 3 features will be formally tested (e.g. unit testing) ? What is the plan for testing, i.e. what are you going to test and how?
- User acceptance tests / approval by customer...
- Documentation level: what kinds of documentation do you plan to do?
- design documentation (e.g. ER / UML diagrams;
include discussion of issues, and evaluation of alternative solutions, i.e. rationale for your design decisions;
at least one significant decision is informed by experimentation or by scholarly research.
)
- code documentation (e.g. javadoc, preconditions and postconditions...)
- user documentation/manual (what does the user need to know to use your system, step-by-step, with screen shots to help illustrate)
- Quality attributes = non-functional requirements, including readability (e.g. descriptive identifiers), ease of maintenance (method decomposition, separation of model and view), and any others that are applicable.