CSCI 340 - Community Project - 65%

Teams

Fundraising Event Planning for CHDC

Chantal Danyluk
Kelsey Dietrich
Lincoln Fischer
Devin Henderson
Callahan Hirrel
Kyle Strege

Online Resident Craft Store for CHDC

Shane Atchley
Anna Holmes
Eric Huynh
Jonathan Kwee
Mason Millsap
Bosco Ndemeye

United Way Volunteer Organization

Mohammad Ali
Taylor Barker
Fish
Blake Hawkins
Michael Spainhour

United Way Community Resources

Taylor Baer
Rader Francis
Jolli Khoo
Kate Sanders
Uzair Tariq
Grace Thomasson

Community Guidelines

Be aware of the power and position you hold
Be transparent about purposes and limitations
Assess community needs, taking into account community partner's views
Acknowledge that you will create burdens for that partner and seek to minimize
Make sure the good you want to produce is a good your partner wants
Do not leave behind a mess
Do not demean or disempower the very people the project was to serve
Do not create expectations you cannot fulfill
Recognize that you likely will not know as much as your community partner about what is risky or harmful for partner's constituents. Follow the autonomous person's most suspect rule: do it because they said so.

Team division

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.

Front-end HTML / CSS
Front-end Javascript / AJAX
Framework / Mobile
Testing

Team Contract

Due Jan 24, signed by all members

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 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. First, the decision-making policy should be by unanimous consent. Software teams that are not unified can easily fracture under a majority-vote process. It is important that every member is working to find agreement, compromise, and unity for decisions affecting your project. If you are struggling to find consensus, I will be available to moderate your discussion. Second, all teams will be using peer evaluation at the end of the semester.

One of your first team decisions will be selecting a project management system. Each member will investigate one of the following options, report back to the team, and the team will decide which to use for the semester. You may use more than one if you see they have different strengths you need.

Task Management Software

Also, sign up for a GitHub account and share your username with your team. You will be using GitHub to store and manage your software over the course of the semester.

First Partner Meeting

Complete by Jan 29
Present Jan 31

Email your community partner with multiple possible times when your team can meet. Find the best times for the most number of people.

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, use cases, entities and relationships you will need to create your project?

You will present your findings to the class in a seven minute presentation, sharing the user stories, use case diagrams, and entity-relationship models you extracted from from your conversation with the partner.

First Meeting Evaluation Rubric

Second Partner Meeting

Complete by Feb 26
Present Feb 28, Mar 2

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.

Second Client Report Rubric

Third Partner Meeting

Complete by Mar 30
Present Apr 2, 4

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.

Final Presentation

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.

Peer Evaluation

At the end of the course, you wil complete an analysis of each team member. 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.