Project Files - Organizing your Team and Project!
This project teams will organize both their Microsoft TEAMS Directory and github repository to prepare them for the semester. The key components of this assignment are to draft and organize the following:
- TEAM Charter Draft this “living” document that outlines your teams logistics. Please use this link to help build your charter and put the official copy in the top level of your TEAMS private folder.
- Agreements Required NDA/IP agreement templates for your team can be found in your Teams Public Folder. Follow the Professional, Legal, and Ethical Responsibilities and scroll to the bottom of the page for a video on how to properly read and sign the required documents.
- TEAMS Public Folder This is a sub-folder in the General channel and is used to share non sensitive files with your classmates. This folder is ONLY for temporary files and should not be the primary home for anything important. Move files from here to the Private folder if it is important.
- TEAMS Private FOLDER Use this folder to store your primary team organizational documents. This includes the team charter, project data, meeting minutes, NDA/IP agreements, Weekly 3x3 Reports, report drafts, milestones, etc. Details about how to set up this folder can be found in this link
- Git Repository Use this folder to track your teams software. We expect all teams to use good software management practices when dealing with code and a good version control system is key. Details about how to set up your git repository can be found I this link
Organizing your files in a logical and clean manner is expected. Instructors should never have to question what they are referencing or have trouble finding documents.
Submission
Draft all documents and put them in the required locations.
If you have an IP and NDA agreement have one (and only one) person from your team email the correctly signed documents to your instructors and your community partners. These MUST be professional emails. You can ask an instructor to check it before hitting send.
Evaluation and Rubric
Project will be evaluated primary on a teams ability to read and following directions.
Make sure your instructors and classmates have the correct permissions to access, clone your repositories and provide the full git command/instructions in your team charter.
Your instructor will evaluate your assignment by reviewing the following:
- Review of team charter
- Checking pdfs of NDA and IP agreements (if required)
- Forking and cloning your repository using the link in your team charter
- Verify repository/files are hosted properly per NDA/IP agreements
- Reviewing of your git log
- Review of your repository README.md file
- Review of your repository LICENSE.md file
- Checking for reasonable .gitignore file
You will be graded on how well directions were followed and the professionalism of the submission.
Points will be taken off if your signed NDA/IP agreemnts are unprofessional.
The following is an approximate rubric that will be used as a guild for evaluating this assignment.
| Meets Expectations | Needs Improvement | Incomplete | ||
|---|---|---|---|---|
| Repository README | Includes description of class and project (10 pts) | Present but lacking detail (5 pts) | Missing (0 pts) | |
| Repository gitignore | Present and includes approriate filetypes (5 pts) | Present but lacking important details (2 pts) | Missing (0 pts) | |
| license | Present and correct (10 pts) | Incorrect license or doesn’t meet NDA/IP agreement (5 pts) | Missing (0 pts) | |
| Repository forking/cloning | Repo can be forked and cloned from link in team charter (10 pts) | Repo premissions are incorrect (5 pts) | Repo cannot be forked/clones (0 pts) | |
| NDA/IP Agreements | Complete and correctly located (10 pts) | Not correctly located or nonprofessional (5 pts) | Missing (0 pts) | |
| Team Charter Content | Charter includes all required sections and contact info (45 pts) | Charter missing at least one required element (35 pts) | No charter provided (0 pts) | |
| Team Charter & Repository Formatting | Overall repository well-organized (10 pts) | Some repository organizational issues (5 pts) | Major missing or incomplete components (0 pts) |
Post-Evaluation
Review feedback from instructors and ensure that any requested changes are made.