Project Charter


Overview & Purpose

  1. Choose three words to describe the spirit in which your group will work together. 
    Synergy, diligence, and connoisseurship.

  2. How will you communicate with each other (e.g., text messaging, email, Google group, Trello, etc.)?
    We will use facebook messenger to communicate with each other.

  3. Where will you store your files (e.g., Dropbox, Google Drive, server, Github etc.)?
    We will be storing all of our files on a team Google Drive Folder.

  4. When you work on a document collaboratively, how will you ensure that you don’t overwrite each other’s changes?
    Change-logs and version control

  5. How often will you meet outside of class? Where will you meet? Do you need a regular meeting time? If you’ll schedule meetings as necessary, what days and times are generally good for people?
    Once a week at the Research Commons. Regularity is always nice. We’d most likely create a poll on whenisgood.net.

  6. When are people planning to be out of town or especially busy? How can you work around this?
    No one has mentioned anything about planning to be out of town, but we will plan accordingly.

  7. Assign the following roles to project member(s). Please note that no single team member is responsible for any of these roles; rather, the specialist coordinates activity related to this work and assigns tasks to team members. If your team has more than six members, multiple people may be assigned to one role. If your group has fewer than six members, please combine two roles.

    • Project Manager (Larry Eames): Pays close attention to schedule and milestones. Alerts the team to possible roadblocks or time-crunches. Ensures that communication among team members is efficient and harmonious. Keeps track of all project documentation. Takes notes at meetings. Communicates team needs (for example, additional training on a tool) to the professor, TA and/or IT Assistant. Communicates with the subject-matter expert. Submits milestones on time via Canvas -
       
    • Web Specialist (Barnabe Ibarra): Oversees the design and structure of the site on Omeka. Works with the CMS (or HTML files) to ensure that the site performs to the team’s specifications. Installs any required updates to the CMS. Archives the project and submits the files to the professor by the end of the quarter

    • Data Visualization Specialist (Sergio Navarro): Oversees the project’s data visualizations. Ensures that data is in the right format. Learns how to use (and teaches teammates how to use) the appropriate tools. Fine-tunes data visualizations and adds them to site 

    • Content/Data Specialist (Colin Sugamura): Oversees the authoring of the site’s main narrative and ensures that the data visualizations and maps integrate neatly with the written content. Writes section headers and captions. Obtains necessary images and embeds them in the site. Oversees the creation of the “About” page -
      Oversees the cleaning, refining, and augmenting of the group’s dataset. Teaches other team members how to use OpenRefine. Ensures the data is standardized, usable, and well-formatted -

  8. Do all decisions need to be unanimous or is “majority-rules” OK?
    The overall Omeka site will be a majority rules based decision, while each team member will be responsible to gather the data they choose from their assigned section.

  9. How will you prevent meetings from going off-track?
    We can develop meeting itineraries or begin the meeting creating one.

  10. What are group members’ pet peeves from previous collaborations? How will you avoid these?
    One member said they prefer regular meetups because it helps with accountability. Another said, that clear communication is key when trying to produce good material. The third member said they do not like it when a person does not participate with the rest of the group because it just makes things more difficult for others. Lastly, the last team member said that it is never a good idea to leave things for the last week.

  11. What will happen to the project when you’re done with it? Will you maintain it, or let it expire?
    After the project is done, our team is going to evaluate whether to maintain the project at the end of the quarter.