Assignment

HIT 238 Assignment 2 - Development Phase For this assignment, you will build your application. You should have a functional prototype web application from Assignment 1. You will continue developing it as either a web application or a hybrid mobile application. Your work should be completed in your GitHub repository and on a Trello board tracking your sprint progress. Each sprint is another iteration of your development process. You will need to revisit your MVP, implement your changes and test your current product. Post a link to your progress report in the discussion board for that sprint before the due date.

Submission Criteria: At the end of each sprint, you will need to submit a progress report with links to your Trello board, git repository and application. At the end of the third sprint, you will need to present your application to the class.

Trello: 3 x 10 marks Your Trello board should track the tasks you aim to complete in each sprint and your process. Create a list for each sprint and a backlog list. Add cards to each sprint to show which tasks you want to complete in that iteration. Any features you would like to include but aren’t important enough to put in a sprint should go in your backlog. Use labels to indicate your progress on tasks (e.g. “in progress”, “on hold”, “completed”).

Git: 3 x 15 marks All your code should be committed to your git repository. Your code should be committed regularly with meaningful commit messages. Each commit should be logically structured and only address a single task. A good guide is if you have to say you did something “and” did something else, you probably have too much in the commit. Create a new branch for each feature which you can merge into master when it is completed. Do NOT use the same message for many commits. E.g. “Updated styles” as it is difficult to track individual changes. Instead, explain what you did. E.g. “Improved readability of header”.

Progress Report: 3 x 5 marks At the end of each sprint, you will be required to submit a progress report as a google document following the provided template. It should include a single paragraph outlining what happened in the sprint, any problems encountered and lessons learned. List the tasks that have been completed in the sprint as dot points and include links to your Trello board, git repository and your application. If you have spent a long time trying to solve a problem and haven’t committed much code, explain it here. If your application is a web app include a link to the application hosted on GitHub pages, if it is a hybrid/cross-platform application include a link to the APK on Github.

Product Pitch Presentation: 20 marks After you have completed your development phase you will pitch your application to the class. You will have 5 minutes to demonstrate your application. This should be a quick presentation to convince the audience that your application is useful. Demonstrate the core functionality, how easy it is to use and explain why the target audience should use it.

Submission Dates

Development Sprint 1 due Week 9 The progress report for this two-week sprint should be submitted at the end of week 9.

Development Sprint 2 due Week 11 The progress report for this two-week sprint should be submitted at the end of week 10.

Development Sprint 3 due Week 12 This one week sprint is a final chance to tidy up any issues identified from user testing. As there is less time you are not required to implement any new functionality and may focus on improving what you have already implemented. The progress report for this one week sprint should be submitted at the end of week 12

Pitch Week 12 The pitch presentations will occur during the final class in week 12. You will need to submit a link to your application before midnight the night before the class. You will only have 5 minutes to present so be sure to rehearse what you are going to say.