Team Directory Organizations

Use your team directory as the operational home for logistics and deliverables.

Minimum Team Folder Layout

Team_Folder/
  README.docx
  Team_Management_Files/
    Team_Charter.docx
    Weekly3x3/
    MeetingNotes/
    Signed_Agreements/
  Project_Deliverables/
  Data_Files/

Adapt naming to your project, but keep this structure easy to scan.

Standards

• Use consistent names (no ambiguous file titles)
• Put newest/high-priority docs where people can find them quickly
• Use date prefixes when useful (YYYYMMDD)
• Keep one obvious location for recurring documents

Required Habits

• Keep README updated as folder structure evolves
• Keep team-level documents separate from individual scratch work
• Store files where instructors can review progress without hunting

1. Teams Folder

Your instructor should have already created a folder for your team. Organize this folder in a way that makes sense to you and your team. However, you must include files to help the instructors (and your teammates) navigate the folder and quickly find what you need.

This week we just need you to create a folder for your signed NDA/IP agreements (if you have them) as well as a complete “Team Charter” document from the in-class activity on Wednesday. As the semester moves forward the structure of your folder should look something like:

Team_Folder:
    README.docx
    Team_Managment_Files
        TEAMNAME_TeamCharter.docx
        Singed_Agreements
            <<NETID>>_Signed_NDA.pdf
            <<NETID>>_Signed_IP.pdf
            <<NETID>>_Signed_NDA.pdf
            <<NETID>>_Signed_IP.pdf
            ...
        Weekly3x3
            <<NETID>>_3x3s.docx
            <<NETID>>_3x3s.docx
            ...
            TEAM_3x3.docx
        MeetingNotes
            Team_meetings_Agenda_and_Notes.docx
    Project_Deliverables
        Propoal.docx
        Proposal_Storyboard.ppt
        Proposal_Video.mp4
        Closed_loop_Storyboard.ppt
        Closed_Loop_Video.mp4
        Final_presntation_Storyboard.ppt
        Final_presentation_video.mp4
        Media_Release.docx
        Project_Slide.ppt
        TEAMNAME_Final_Report.docx
    Individual_TeamMember_files
        <<NETID>>
        <<NETID>>
        ...
    Data_Files
        DataFile1.csv
        DataFile2.csv

The README files are extremely important and should be the first “touch point” in your files. Assume that people new to the folders will start there. Use that to guild people to the other parts of the project. All files should be documented and clearly labeled. There should be no confusion about what a file is and why it is in the folder. Use YYYYMMDD in filenames to denote Year (YYYY), Month (MM) and Day (DD). Use your MSU NetID to indicate files authored by individual team members and use your short team name to designate files for your team turned into the instructor. The only exception to the previous guildline is that anything in the Individual_TeamMember_files will mostly be ignored and should be used by team members to share files with each other.