Skip to content

rmezapi/a99-Team-27

 
 

Repository files navigation

a99 Final Project

Summary

COMP426 final project template boilerplate. All your code and documentation goes here. Change this text to be a brief description of your final project. Put the name of your project in the header above. You will change everything below to be the main technical documentation, as outlined below.

First steps

Other steps that you will need to take after your team has accepted the assignment:

  1. Choose a license and update the LICENSE file accordingly.
  2. Edit this README.md file and use it as the main location of your technical documentation with links out to information contained under /docs/.
  3. Create a /docs/ directory for more elaborate documentation of your API, planning notes, etc.
  4. Make sure that all of your team members have access to the repository as administrators.
  5. Create a project under the Projects tab. Use this to manage your planning. Create a To-do list, etc. Explore the tools available and user them to manage your project.
  6. Assign team roles and include a listing of those roles in this README.md file or in another file under /docs/.
  7. Then put your entire development workflow in this repository.
  8. Use Pull requests to propose changes and incorporate them into your code from various team members.
  9. Use Issues to identify and track bugs and also to communicate about various aspects of the project.

Team mangement

Plan to meet with your team ASAP. Talk through identifying roles within your team.

Try to figure out what each of you are good at/enjoy doing and try to work out roles that incorporate that.

Some basic roles you will want to consider:

  1. A review manager - someone to review pull requests and merge or reject them and manage the related discussions
  2. A plan manager - someone to keep an eye on the overall plan and keep the project tab/to-do list up to date
  3. A documentation manager - someone to keep the documentation in order and identify what is missing and needs to be documented
  4. A release manager - someone to manage the packaging and release process for your prototype package
  5. A project manager - someone keeping track of all the moving parts and make sure that everything that needs to happen is happening.
  6. Roles for team members to take charge or different parts of the project. Possible roles:
    1. Front end lead
    2. Back end lead
    3. Database lead
    4. Design lead
    5. Etc.

You will notice that there are more roles than people in your group. That is because you will all be doing a hybrid job of managing a thing while working on other things.

Assignment instructions

And that is about all you need to get started.

Good skill and be creative!

About

Team 27 Final Project

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 74.0%
  • HTML 26.0%