Sprint 2
This is a team assignment; each team submits one assignment
Due Date for Preliminary Deliverables: November 5, 22:00:00 EST (No late submissions will be accepted).
Weight: 3% of course grade
Due Date for Final Deliverables: November 13, 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 milestone due date, and all others will be verified by your TA at the weekly tutorial meetings.
Note: most of the items for this milestone should be things that you would generate anyway through the normal course of development. Just make sure that you document your progress thoroughly and consistently.
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.
If you have not already done so, add the following tools to your process.
If you use third-party tools, be sure to provide your TA with access credentials for the purposes of grading.
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.
Describe what the user can do in your program and how. Provide screenshots and navigation descriptions for the current interface to the program.
Some questions to think about may include (but not limited to): - What will your application be able to do? - What kind of information will it display? - What will the user see at each stage of usage? - What will the screen layout be like?
This document will be used to prepare the User Manual that is expected as part of the final release.
Give a demo to show your software to best effect. The demo should last five minutes, followed by a five-minute question-and-answer period.
Describe any design changes that were made to the structure or data flow of the product.
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: Sprint backlog, burn down chart, scrum board, automated test cases, and test plans are due on November 5. The TAs will give you feedback on them during tutorial.
Final versions of all deliverables are due on November 13.
In both cases, submission will be through GitHub.
Create a web page for Sprint 2. 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, November 8.