a. Project Management Document (Team Charter) - BCDross/IST320-group-project GitHub Wiki
Team Members: Darren Ross, Devon Rice, Khalid Mohamed, Khang Tran, May Kwon
Date: 11/01/20
Project Tile: Final Group Project
Lead Contact: Darren Ross
To create a program/site which will enable a user to build and save a deck from a card game and edit the deck as the user needs.
• Project Lead: Darren Ross
• Communications: Khalid Mohamed / Khang Tran
• Scribe: May Kwon
• Merge Management: Devon Rice
Task Assignments: Tasks will be assigned on a first come first go basis, unless somebody either isn’t comfortable with the task given or somebody is more experienced at a task and the group feels comfortable that they do said task.
Communication Platforms: MS Teams and Zoom
Documentation: All code will go onto the GitHub Repository created by Darren.
Link: https://github.com/BCDross/IST320-group-project
Change Management: If somebody wants to change their role within the group, they should let the group know that they want to change their role and what role they want to have in the group. We will note the change in the Team Charter.
• Darren Ross
o C# / .Net Core / ASP.Net Core
o HTML / CSS / JavaScript / ECMAScript / TypeScript / Angular / Express
o Project Management/ Agile/SCRUM methodology
• Devon Rice
o Java / JavaScript / Angular / HTML / CSS
o Project Management
o Group communication
• Khalid Mohamed
o JavaScript / HTML / CSS / C#
o Project Management
o SQL
• Khang Tran
o JavaScript / C# / Problem Solving / SQL / HTML / CSS
• May Kwon
o HTML / CSS / JavaScript / C# / SQL / git
o Communication skills / Critical Thinking / Flexibility
• Meetings: Thursdays at 8:15 to 9:15
• Will meet using MS Teams
• Meetings can be recorded if need be
• Everyone is expected to go to the meeting unless said otherwise
• No set responsibilities for the meetings, the point of the meetings is to check in and see where everybody is at and help each other if needed
• If somebody falls short of expectations, we will figure out why that is the case and try to help them achieve their expectations
Overall Team Commitment:
Everybody should be trying to commit at least an hour or two on the project and trying to get as much work done on the project as possible and giving the project as much attention as they can afford to give.
Individual Commitment:
• Darren – 3 - 4 hours a week on the project. Planning and design contributions. Research contributions.
• Devon - At least 2 hours a week on the project. Programming and maintenance contribution.
• Khalid – At least 1 - 2 hours a week on the project. Responsible for communication and programming.
• Khang – At least 1 - 2 hours a week on the project. Programming and debugging contribution.
• May – 3 - 4 hours a week on the project. Debugging, UX/UI design, frequent note taking throughout the meetings.
If there is an issue (one on one), bring it up:
1st) Talk one on one
2nd) Bring in the group
3rd) Bring in the teacher if needed
(all issues will be documented by the scribe / communications or if one on one between those two)
Team expectations:
- Work with each other to accommodate to other's needs.
- Collaborate in non-attacking tone in order to create a welcoming environment for everyone.
- Compromise for the greater good of the team.
- Once issues are resolve, take a small amount of time to reflect on the issues and how it began, was resolved, and do your best to start on a “new page.”
- If there is an issue with a task assignment, individual will bring it up with the project lead, who will in turn try to assign another in their place or assign help for the task if that works better.
- Issues with deliverables: (all issues documented by the scribe / communication)
- If you are running behind, communicate with the team beforehand.
- With communication and good reason, the team can plan around with no repercussions.
- Without communication the team will get together and find a way to resolve quickly.
- Habitual offenses without good reason will be brought up to the teacher.