Von-Seth
commented
1 day ago Work Division:
- Project work is divided into 2 main categories,
- Specialized Work: is subdivided into roles with key responsibilities. This is done by holding specific members accountable to key responsibilities, reducing the chance for repeated and missing work. Project submission, server setup, and specific technology leads are all examples.
- General Work: is any task that can be worked on by any member. Implementing a new feature, debugging, and assisting others in their roles are all examples of what is expected from everyone.
- [NOTE] Not all role responsibilities are solely that of the roles’ holder(s). At times some members will need to take on other roles' responsibilities. If a member’s workload is noticeably less than that of another member's workload, they are expected to reach out and help distribute the work.
- Example of a responsibility only one role states, but every member should try to fulfill:
- Keeping meetings on track
- Example of a responsibility solely that of the role's holder(s): (assuming the role holder(s) were not informed)
- Submitting project files for grading
- In general, if fulfilling another role's responsibility does not confuse or hinder the role holder's ability to work. Then it is safe to fulfill without asking.
- A list of Roles & Responsibilities can be found here, (https://github.com/COMP-4350-Group-8/admin/blob/main/role-responsibilities.md)
- GitHub Issues are used to record work
Also can be found in Sprint 0 document on group drive
Description:\ How are you planning on dividing work in the project?
Items