Team Contract
Expected Level of Achievement and Effort
Adrian
Ideally, I would want to get an A on the project, but getting a B would be fine. In terms of time I plan to put in, I intend to put in as much time as needed to complete the tasks I am assigned.
Caleb
I’m comfortable with a B. A is ideal though. Getting a C would be unfortunate. I’ll prioritize this project over other classes as necessary/commit as much time as necessary to complete my tasks adequately.
Lauren
I aim for at least a B, preferably an A. I’m planning to put in as much time as necessary, with an estimate of 10-15 hours per week.
Rachel
For our final project, I anticipate achieving at least a B grade, with the aspiration of earning an A. I am committed to dedicating sufficient hours to ensure we develop an app of which we can be genuinely proud, encompassing all the functionalities we outlined during the design phase. My plan is to invest a minimum of 10 hours per week, with the flexibility to allocate more time as necessary in case I can not complete my part of the project in time.
Personal Goals
Adrian
My goal is to improve/expand upon the skills I learned so far in the class. Notably, I want to improve the structure and cleanliness of my frontend code, to make an app that has a clear and clean component tree. I would also like to stress the database design in this app more than I did in my own app.
Caleb
I want this app to function and look better than my personal project. I’d also like to get more comfortable with web app/database/api development.
Lauren
My personal goals are to put out an app that I can be proud of, and to get more familiar with web app development.
Rachel
I aim to use this team project as an opportunity to deepen my understanding of building a full-stack app in a collaborative setting. I also want to expand upon the skills I learned during my individual project and leverage them to build a more intricate application. Additionally, I want to gain a deeper understanding of constructing both the frontend and backend components from scratch, while also integrating more deliberate and thoughtful design choices into our work.
Team Meetings
Tuesdays and Fridays from 7pm to 10pm at Hayden Library excluding holidays.
Quality of Work
To maintain our quality of work, we will do code reviews after each team member finishes programming a feature or a concept.
Task Assignment
For research and interviews, each team member will interview one person and conduct individual research. Once we reach the design stage, the entire team will work together to design the concepts and wireframes. Once we start working on the backend and frontend of the app, each team member will be in charge of different concepts or features to implement.
If deadlines are going to be missed, the team member should let the rest of the team as soon as possible and, if they have a valid reason, the rest of the team will help finish the task at hand. The person who missed the deadline will make it up in future assignments if possible. If it is not a valid reason or the person misses deadlines frequently, the team will talk with the individual and consult our mentor/TAs/Professor regarding the issue. (P.S. Caleb will be very sad 😦)
Decisions and Disagreements
The team will aim for unanimous decision for making decisions, but if it is not possible we will go with the majority decision. In the case where we can not get a majority decision, we will resort to probability (ie. flipping a coin) or consult the TAs for their opinion and advice.