How will you communicate with teammates you depend on? Describe specific tools or settings.
     For synchronous communication, our team will use Facebook messenger. We have all agreed to monitor this system from 8am-9pm, and use it primarily for updating the team on progress towards our weekly goals (see schedule below). When we need to message someone specifically about a dependency one of us may be waiting on, we will use the @ symbol to tag the appropriate user. We decided to use Facebook Messenger because it is cross-platform, and because we all monitor it more frequently than messengers like Slack.

What coordination and planning practices will you follow? Identify daily scrums, sprint planning meetings, ad hoc meetings, or other ways of coordinating work.
    To coordinate work and provide individual updates, we plan to use the first 10 minutes of the time allotted for the daily activity to relay new information. Outside of this time, we plan to meet after lab each week on Tuesday to finalize the work from the prior week, in addition to meeting “online” Wednesdays at 12pm to submit any documents we completed since Tuesday evening. For each upcoming week, we will finalize our sprint for the week on Thursday and to discuss what is expected from each team member.

Who will own each of the components in your architecture?
    For our team, it was easiest to divide the primary development features between three team members and keep one member on design & test. Soobin will be primarily responsible for said design (since she is an incredible designer and less familiar with web development) and test, as will Ivan to an extent. Breaking down individual components, Ju An will be responsible for implementing the Google Vision API and other components related to image processing (since she has solid experience with image processing); Ivan will be responsible for Log In, Sign In, Sign Up, React Router and testing (since he has lots of experience working with Firebase); and Kyle will be responsible for implementing the Homepage and account settings (since he has experience developing landing pages with similar structures). See the schedule at the bottom of the document for a full breakdown of responsibilities in relation to our envisioned time frame.

By what date will you have a fully-built (but likely buggy) release candidate?
     Our goal is to have a fully build website by May 29th. Having a functioning model by this date gives us ample time to thoroughly test our product according to our spec before submitting the final version on June 3rd.

What practices will you use to know if you're making progress toward that release candidate?
    The primary way we will know we’re making progress is by beginning to connect the completed pieces. We plan to incrementally integrate working pieces onto a development branch on GitHub (see the schedule below for dates we plan to have pieces completed by) and test the completed pieces as we go.

What practices will you follow to improve your process if it's not working?
    We will initially know when a process isn’t working by observing a team member falling behind schedule. In the case that someone is behind schedule, we will be reactionary and reevaluate individual workloads to spread out responsibilities as needed. In the case that a team member drops the class, ceases communication, or Google Vision stops working, we will similarly reevaluate individual workload, and potentially rely on other forms of image evaluation if Google isn't an option.

Schedule

Week 1 (5/14)

Ivan

• LogIn/SignUp
• React Router Setup

Kyle

• Homepage

Soobin

• Begin creating stylesheets

Ju An

• Image uploading

Week 2 (5/21)

Ivan

• AcceptTerms

Kyle

• Display Images

Soobin

• Implement stylesheets on completed components

Ju An

• DeleteImage

Week 3 (5/28)

• 5/17 After Lecture: Freeze Requirements Meeting

Ivan

• Forgot Password
• Test

Kyle

• Account Settings

Soobin

• Test completed designs

Ju An

• Color Processing

Week 4 (6/4)

• 6/7: Homework 11 - Final Presentation from 4:30-6:20

Ivan

• Test & Evaluate HW
• Reflection HW

Kyle

• Test & Patch HW
• Reflection HW

Soobin

• Test & Presentation HW
• Reflection HW

Ju An

• Test & Release HW
• Reflection HW