Final Project: Milestone 1

For this milestone, you will set up your team and then create an initial version of your Textbook Exchange application.

Set up the team

Here are the teams for this project:

• Clint Morimoto (clintmor), Jordan Dumlao (dumloaj), Michael Hoe (mahoe7)
• Rory Andrews (rorya), Micah Tashima (micahtas), Reed Shinsato (rs7)
• Brian Boado (bjboado), Matthew Yee (mgy), Sy Morikawa (sy)
• Josephine Garces (jgarces), Corynne Umeda (chumeda), Michelle Shimoda (mkshimod)
• Gilbert Yim (gyim), Joshua Taylor (jtaylor9), Sam Chun (skchun), Michael Spencer (michael4)
• Aljon Preza (aljonp), Kelsie Yamakawa (kayama), Khongnawang Sorapong (khongnaw)

Your team will create a single repository within the GitHub TextbookMania organization. You must pick a name for your team from one of the 140 HTML Color Names. For example, your repo name might be “LemonChiffon”. Choose carefully: this color must also be in your color palette for your site!

Every team must choose a different color name; check the textbookmania organization for the repos that have been created. If your color has already been chosen for a repo name, you must pick a different one.

Create a new Slack team to support communication for this project. The Slack team name should be tbe-, where is the color name you picked for your repo. Be sure to invite johnson@hawaii.edu to your Slack team so I can observe how you communicate. (You can also use Slack to ask me questions!)

Create the initial set of issues

First, create three milestones for your system in the GitHub Issues page for your repo. Name them M1, M2, and M3, and give them the due dates specified on the Schedule page.

Next, connect your repo to HuBoard, then use it to create and manage the development of your system. 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).

Build the M1 version of your application

By the date associated with this milestone, you should have created and deployed a functional version of your application to meteor.com. All members of your team should have completed and closed a minimum of two significant issues. (Don’t create trivial issues to fulfill this requirement; I will notice and grade accordingly.)

For the first milestone, I do not expect you complete all functionality. Successful teams will be able to demonstrate a “mockup” of the system and a few functioning parts.

I also expect to see communication between group members using Slack. Within the Huboard Integrations page, you can add Slack if you’d like to see HuBoard events show up in your Slack team.

For the first milestone (only), you do not have to create a GitHub page and associated wiki pages for your system.

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 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?

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