Some of these initial requirements will be duplicatedfrom CSC454/2527, you can use those materials. The repository must be set up like a company not a course. I do not want to see folders names “Assignment 1”, etc. except for the GitHub Release in the submission.
While you may use a different medium in real-life, the intention in using a repo for this course is to allow you to version control your content. This will enable everyone to see the evolution of your company over time.
This repo is your homebase. When you have a decision, log it. Make use of issues, wikis, and projects as you see fit. However, make sure you describe how your team uses various communication methods in either the README or the Team Principles and update it with new decisions. Failure to describe this in the README will force the teaching staff to try and figure it out myself and will result in a lower communications grade.
Let the process evolve over time. Reflect on your processes, change them, record them.
There are two exceptions:
While you can work the way you want (except for the exceptions noted above), I’ve found this setup to be pretty useful for a “team repo”:
|Issues||Track questions and product roadmaps. These make a great decision log|
|Pull Requests||When you don’t like something, find an outdated line or link… change it using a PR. Tag others on your team to review. Aim for a 24-48H turn around on reviews for that.|
|Wiki||While these can be helpful, please do not use them as they are hard to find for our apps and team management tools|
|In-Repo Docs||General documentation can be laid out in markdown files in a folder structure that makes sense|
This repository (for CSC491) will be setup like this, but may evolve over time.
You will elect a “leader” in your team. This person will be responsible for making product and business decisions for the build and making sure the build stays on track. While this leader can be from either class, the person will be required to manage the CSC491/2600 side so it may make sense to make this “decision person” from the CSC491/2600 side.
In your submission, tell us who your “leader” is. Note: this person will potentially change throughout the term.
You must create a release on your repo. This will give us a snapshot in time and allow us to grade it.
Assignments are always due at 11:59:59pm Eastern Time.
Second, you must submit the release on the LearnSoftware application. You can find the submission location here: https://learnsoftware.engineering/my_assignments
|Company Logo & Name||Good logo/name that represents a modern idea||15.0|
|Team Profiles||Team profiles include photos and profile links of all teammates, clearly lists expertises, and a short biography||15.0|
|Leader Selection||Tells us who they chose and why, what is their role for your team?||5.0|
|Team Principles||The team principles doc is a 1-page doc that covers: expectations of the team members, expectations for communication, roles and responsibilities, work delegation, etc.|
The document will cover the entire team including CSC454/2527 students. An example can be found here
This scale is used for each line of the rubric above.
|Outstanding||100% of pts|
|Strong||80% of pts|
|Acceptable||60% of pts|
|Insufficient||40% of pts|
|Unacceptable||0% of pts|