Project 1: Community Project

Teams

Family Promise of Pulaski County

  • Ketsia Dusenge
  • Thomas Moslander
  • JC Ntambara
  • Riley Skief

Faulkner County Museum

  • Ted Bjurlin
  • Jacob Collier-Tenison
  • Scott Cooney
  • Henry Jackson

SOS Hendrix Resources

  • Zach Bernheimer
  • Amelia Jones
  • Sarah Wright

Faulkner County Juvenile Court

  • Justin Grubbs
  • Johannes Mayrhofer
  • Hayden J Moussa
  • Joseph Washum

Commencement Seating Chart

  • Colten Berry
  • Noah Chaffin
  • Ian Walker

St. Joseph Bazzar

  • Taryn England
  • Tucker M. Groves-Benedict
  • JP Lyon
  • Caden McCarty

Music Event Attendance

  • Elliot Allen
  • Ryan Fuller
  • Mason Mason

iSeeGreen Plant Identification

  • Kate Jackson
  • Fin Lockert
  • Simon Reid

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 Responsibilities

You will fill multiple roles in your team. The roles below must be distributed across team members, but the tasks for roles should not be exclusive, you should all help each other. 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.

  • Client Communication
  • Team Organization
  • Front-end HTML / CSS
  • Front-end Javascript / AJAX
  • SQL Schema Design
  • Framework / Deployment

Team Contract

  • Due Sep 28, 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 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.

  • 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.

Your team contract should be written as the Readme.md Markdown file in a shared GitHub repository. One member will create the repository, and all team members should be added as contributors. In addition to the contract details listed above, each member should write and commit to the Readme.md file a paragraph detailing their responsibilities as decided above and how they plan to contribute to a positive team experience and resolve conflicts over the semester.

Project Management Software

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.

First Partner Meeting

  • Complete by Oct 6
  • Present Oct 9, 11

Send a professional email your community partner with multiple possible times when your team can meet. When you hear back, find the best times for the most number of people, and confim the meeting time with your partner. CC Dr. Goadrich on your emails.

Your first meeting with your community partner will focus on gathering requirements for the project. You should ask

  • What does your organization do?
  • What information do you manage?
  • How do you manage it currently?
  • Who needs to access your data and how?
  • What pieces are the highest priority?
  • How will this project help your organization?

You should leave the meeting with a clear idea of the system they want to make. What are the stories and use cases you will need to create your project?

You will present your findings to the class in a six minute presentation, sharing the user stories and use case diagrams you extracted from your conversation with the partner, along with an initial database schema or entity relationship diagram.

First Meeting Evaluation Rubric

Mockups Day

  • Present Oct 25

After with the client, you will work to clarify and solidify the requirements for your project. You will present other groups in the class with mockups and HTML/CSS demos of the webpages you believe will enable you to carry out your client’s described use cases and user stories.

Following this presentation, make a Jekyll blog post about your personal role in your team project so far, your contribution to creating the mockups and demos, and your future plans to assist your team in completing this project.

Second Partner Meeting

  • Complete by Nov 10
  • Present Nov 13, 15

In your second 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 second client meeting, and your future plans to assist your team in completing this project.

Second Client Report Rubric

Final Presentation

During the final exam period, your team will present and demonstrate the complete prototype you have built. You should plan for a 15 minute presentation and at least 2 minutes for questions.

Final Client Report Rubric

Time Presentation
2:00 Music Event Attendance
2:20 SOS Hendrix Resources
2:40 Faulkner County Museum
3:00 Faulkner County Juvenile Court
3:20 Family Promise of Pulaski County
3:40 Commencement Seating Chart
4:00 St. Joseph Bazzar
4:20 iSeeGreen Plant Identification

Peer Evaluation

At the end of the course, you will 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.

SW Reflection

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.

  • What skills and talents are most valuable in carrying out the social change work you are doing with your community partner? How well do those skills mesh with the talents or limitations you have come to see in yourself through the experience?

  • Consider the social, environmental, or spiritual need on which you are focusing for this Odyssey project. Do you feel that the approaches to creating social change employed by your community partner are effective ways of creating change in this area? Why or why not?

  • Have any of your fundamental values, social ideals, or significant beliefs been challenged or confirmed through this experience? Have you found any of your academic coursework helpful in understanding what you have observed and experienced? Anything you learned in class that you would directly challenge now that you have had this experience?

  • There are many social, political, environmental, or community issues on which you might work in the years ahead. How has this experience reshaped your views on the public issues that call you to action?

Grading

A Complete final project will

  • demonstrate participation in all client and group meetings
  • contribute to and follow the obligations specified in your group contract
  • describe numerous user stories and detailed use cases using a Trello board
  • design intitial prototypes in Moqup for all necessary project webpages
  • expand user stories into Github milestones and subdivide them into achievable issues
  • develop a working initial prototype demonstrating substantial progress toward turning your Moqups into code
  • iterate a final prototype that is polished and published on Azure
  • present your final prototype and development process to your client and peers
  • contain significant and regular contributions on Github
  • submit an authentic and comprehensive evaluation of your peers and yourself
  • complete an in-depth refection post on your SW Odyssey project experience
  • include an hours log with 30+ hours of work documented

A Partially Complete final project will

  • demonstrate participation in most client and group meetings
  • contribute to the obligations specified in your group contract
  • describe user stories and use cases using a Trello board
  • design intitial prototypes in Moqup for most necessary project webpages
  • expand user stories into Github milestones and subdivide them into issues
  • develop a working initial prototype demonstrating progress toward turning your Moqups into code
  • iterate a final prototype with limited functionality that is viewable on your local computer
  • present your final prototype and development process to your client and peers
  • contain multiple on Github
  • submit an evaluation of your peers and yourself
  • complete a refection post on your SW Odyssey project experience