Final Project: Milestone 2

For this milestone, you should strive toward two goals:

1. Improve the functionality and quality of your application.
2. Improve your software engineering process.

These are closely related: if you improve your software engineering process, you are almost guaranteed to improve the functionality and quality of your application!

The M1 assessment includes suggestions on how to improve your product and your process. Make note of them and try to apply them during this milestone.

As in the last milestone, you are expected to document all tasks using GitHub issues, and use HuBoard to manage your workflow. Recall the following Project Management Guidelines:

• Meet every 2-3 days to update tasks.
• Each task (issue) should not take more than 3 days to complete. (If it does, then edit the task to be simpler).
• All significant tasks (taking longer than a few minutes) should be documented in an issue.
• All issues have an owner.
• All team members should always have a current task to work on as well as an upcoming task (once the current one is completed).

For this milestone, you should deliver a “release” of your system, which includes:

• A GitHub page documenting your system with links to your wiki pages.
• Wiki pages for your User Guide, Developer Guide, and Contact us.

Submission instructions

On the date associated with this experience on the Schedule page, your team will make a 10 minute oral presentation of the status of your project. This presentation should include:

• A demo of your GitHub Page and wiki pages for your system.

• A demo of your system. The version you demo must be deployed to meteor.com.

• A review of your system’s HuBoard. Show what issues were completed during this milestone, and what you have scheduled to do next. Each team member should describe the issues they were assigned and how they completed them.

• A review of your Slack Team. Show what channels you created, and what conversations occurred during this milestone. Did you integrate HuBoard? Did it prove useful?

• How you improved your software engineering process since the last milestone.

• What you’ll do differently for the next milestone. How will you improve your system and your software engineering process for the next milestone?