You will fill multiple roles in your team. Each member will have a first and a second priority role, to be decided upon by the team. One person cannot have both of the front-end options as their first and second, these must be distributed to all team members. As the project progresses, these roles should be seen as guidelines rather than strict rules, and your responsibilities should be fluid to match the situation.
Your team will need to create a team contract. This will be the governing document for your team. It will help you establish the structure, procedures, expectations of participation, accountability, and consequences for breech of contract.
Here is an excellent template from a similar course at Georgia Tech for a team contract that you should use in devising your own contract.
Note that there are two options on the contract where there will be no choice.
To manage a large project, we will be learning and using multiple pieces of project management software, each of which is useful for different situations. Sign up for an account on each of the following websites. Each team member should investigate one in particular and report back to the group in your first team meeting about its usefulness.
Your first meeting with your community partner will focus on gathering requirements for the project. You should leave the meeting with a clear idea of the system they want to make. Do they need a web app or mobile app, or both? What are the stories and use cases you will need to create your project?
You will present your findings to the class in a seven minute presentation, sharing the user stories and use case diagrams you extracted from from your conversation with the partner.
First Meeting Evaluation Rubric
In your second meeting with the client, you will work to clarify and solidify the requirements for your project. You will present them will mockups and HTML/CSS demos of the webpages you believe will enable them to carry out their described use cases and user stories.
You will then present on the results of your meeting, working the class through any revisions and expected next steps in your process.
Following your presentation, make a Jekyll blog post about your personal role in your team project so far, your contribution to the second client meeting, and your future plans to assist your team in completing this project.
In your third meeting, you will be able to present your client with some basic working webpages and implementations. Not all elements are expected to be complete at this meeting, but the client should be able to click, type, and select options on a subset of the website with a properly working backend database management system.
You will return to the class and present the results of your meeting, the demos you executed, the lessons learned, and a breakdown of steps needed to complete your project by the final exam period.
Following your presentation, make a Jekyll blog post about your continued role in your team project so far and how it has evolved, your contribution to preparation and execution of the third client meeting, and your future plans to assist your team in completing this project.
During the final exam period, your team will present and demonstrate the complete prototype you have built. You should plan for a 20 minute presentation and at least 2 minutes for questions.
At the end of the course, you wil complete an analysis of each team member, to be sent privately to Dr. Goadrich.
This analysis should include a separate paragraph for each team member, including yourself. Each paragraph should describe how that team member contributed to the project in concrete terms (this person did XX), and it should also provide some analysis of that person's strengths and/or weaknesses - in terms of quality of contributions as well as teamwork skills.
I am looking specifically for positive aspects as well as constructive criticism that might help the classmate work better in future teams. The analysis for each team member would ideally be at least 5 or 6 sentences long, longer would be welcome.
This project will be approved as an SW Odyssey Project, which requires a reflection component to help you process and understand the experience in context. Your SW reflection will be your final Jekyll blog post for the course.
Here are some questions to get you started writing your SW reflection blog post for our database project working with community partners, taken from the Odyssey reflection prompts. Feel free to expand beyond the questions listed here as you process your experience.