Sprint 1
This is a team assignment; each team submits one assignment
Due Date for Preliminary Deliverables: October 15, 22:00:00 EST (No late submissions will be accepted).
Weight: 3% of course grade
Due Date for Final Deliverables: October 23, 22:00:00 EST (No late submissions will be accepted).
Weight: 12% of course grade
Submission format: commit all necessary files to your team GitHub repository by the deadline.
The goals of the project at this stage are:
All work artifacts should be checked into the repository throughout the sprint. Time stamps and versions will be used especially to evaluate process tasks.
The following tasks relate to the scrum process, not the performance of the product itself. Elements that can be documented should be included in your repository by the sprint due date, and all others will be verified by your TA at the weekly tutorial meetings.
Be sure to meet with your Product Champion at least twice: once to prioritize the user stories and once to obtain feedback on the work you have done so far.
Estimate sizes for your user stories. Present the stories to the Product Champion and obtain a prioritization.
Decide which stories will by implemented in this and the remaining sprints.
Take the stories allocated to the current sprint and break them into a tasks. Estimate the number of hours required for each task.
Place the tasks and stories on a Scrum Board. Use this display to track the progress of tasks and stories.
Create a burndown chart. Record progress on the chart as the project moves forward. Calculate estimated and actual velocities.
Keep minutes for your all meetings (planning, scrums, and client). Minutes should include a list of who attended, what decisions were made (and how), and a list of action items (with deadlines and who they were assigned to.) Also, create a spreadsheet showing who attended which meetings. Make each meeting a column in the spreadsheet.
As with the Process Tasks, the Product Tasks are ongoing. They may be checked by the TA at the end or during the sprint.
For every story, there must be either an automated tests or a test plan for manual testing. These should be produced before the application code is written.
Create the functionality for multiple user stories. Every team member must write code.
Produce code that is easy to read and easy to understand. Use comments, developer notes, diagrams, and documentation as appropriate to facilitate comprehension.
Justify your decisions. Why did you select the technologies that you are using? How did you arrive at these decisions? What is the design/architecture of your software? Why this structure, subsystem decomposition, data model, etc?
Write a specification for what you will build for the next sprint. Think about what / how many features (user stories) you should build, what other supporting documentation should be submitted with them, and what criteria should be used to judge success (i.e. how will your TAs mark Sprint 2?)
Preliminary Deliverables: Estimates and priorities of the user stories are due on October 15. The TAs will give you feedback on them during tutorial.
Final versions of all deliverables are due on October 23.
In both cases, submission will be through GitHub.
Create a web page for Sprint 1. From there add links to all elements that you want graded. Many of the links will be to your group's github repository. This includes meeting minutes, notes about your conversations with the customers, test plan, test code, user stories, source code, and any other explicit and implicit deliverables.
The above requirements are subject to changes based on feedback from the course bulletin board. This page will be frozen at midnight on Friday, October 18.