-
Notifications
You must be signed in to change notification settings - Fork 0
Team charter
GitHub URL https://github.com/deco3500-2019/Lightning-bolt
🤔 Raymond Kiss
⭐ Bachelor of Engineering (Software)
📧 r.kiss@uqconnect.edu.au
📋 Team leader, organises/proofreads paperwork
🤔 Naoya Yamamoto
⭐ Bachelor of Information Technology (Enterprise Information Systems)
📧 naoya.yamamoto@uqconnect.edu.au
📋 Organises meetings and record meeting minutes
🤔 Yun-Tung Shen (Sheryl)
⭐ Bachelor of Information Technology (Software Information Systems & UX Design)
📧 yuntung.shen@uqconnect.edu.au
📋 Ensures other members are on schedule, performs usability testing
🤔 Shawn Xue
⭐ Bachelor of Information Technology (UX Design)
📧 yipeng.xue@uqconnect.edu.au
📋 Organises the Trello board.
We will be using Facebook Messenger as a communication platform with all members in the team. If the primary communication channel (Facebook Messenger) fails, we will be using **Slack **to maintain communication. It is expected that team members have to respond messages within 24 hours if needed.
- Messages/announcements sent via Messenger must be read within 24 hours of sending by all members.
- Meetings will be conducted during workshop sessions (Thursday 10am-12pm), and also conducted on Saturday and Wednesday as necessary.
- Meetings will be held at the University of Queensland or State Library.
- Meetings will be arranged such that at least 3 members are able to attend
- Members will be notified of upcoming meetings at least 24 hours prior to the meeting
- In the case of absence and lateness to the meetings, members are obliged to notify the others through communication channel.
The group will discuss the pros and cons of each opinion and compromise on which is the most beneficial to the project. If team members disagree about the decision, the team will decide by majority vote.
- Work will be distributed through a Trello board. If there are tasks remaining after everyone has finished selecting tasks, they will be distributed more or less at random.
- When a member believes their work is complete, the other members of the team will review the work to determine if it’s of acceptable quality.
- Members must provide status updates on work done 3 days before the due date (e.g. work completed, work in progress, need assistance, etc).
- If a member is unable to complete a task and gives sufficient notice to that effect, the team will develop mitigation strategies as necessary.
Escalation procedure
- Potential solutions will be discussed over online communication channels between the concerned members.
- In the event that a resolution is not reached by the next meeting, the team will discuss potential solutions as a whole and vote on a consensus.
- In the event that a resolution still isn’t reached, the situation will be escalated to a tutor.
Escalation procedure
- The concerned member will be notified that they are behind schedule. Potential solutions will be discussed over online communication channels between the team.
- In the event that the situation is not remedied by the next meeting, the team will discuss potential solutions as a whole and vote on a consensus.
- In the event that the situation is still not remedied, the situation will be escalated to a tutor.
When required, team members should maintain communication and reply to Messenger within 3 days. Tutors will be contacted as the following procedure:
Escalation procedure
- Written email will be sent to the team member(s) after 2 days of no communication to follow up the discussion.
- Team member(s) will be contacted via email and Messenger after 3 days of no communication.
- If the previous contact method fails and/or no action has been taken when required, course staff will be contacted via email to notify the current situation.
Raymond Kiss
Naoya Yamamoto
Yun-Tung Shen (Sheryl)
Shawn Xue
Overview
Team Charter
Proposal
Design Process Overview
Sprint 1
• Sprint 1 Overview
• Literature Research
• Prototype #1
• Interview #1
• Interview #2
Sprint 2
• Sprint 2 Overview
• Prototype #2
• User testing plan
• Research #2
• Use Case Diagram/Scenarios
Sprint 3 and Showcase
• Sprint 3 Overview
• User Testing Evaluation
• Prototype #3
• Research #3
• Showcase Material
• Showcase Feedback
• Work Allocation