Professional practice TEAM REPORT planning a training event

Professional Practice TEAM REPORT Planning a training Event Teacher: Ngo Ngoc Tri Team members: Tran Quang Huy Nguyen Duc Dung Thatsadaphone Inthatpakdy Class: GCD0825 ASSIGNMENT FRONT SHEET Qualification BTEC Level HND Diploma in Computing Unit number and title Unit 3: Professional Practice Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student names & codes Group number: Class Final scores Signatures Tran Quang Huy HUY Thatsadaphone Inthatpakdy BEE Nguyen Duc Dung DUNG Assessor name GCD0825 Ngo Ngoc Tri Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism I understand that making a false declaration is a form of malpractice P1 P2 P3 P4 P5 P6 M1 M2 M3 M4 D1 D2 D3 OBSERVATION RECORD Student Description of activity undertaken Assessment & grading criteria How the activity meets the requirements of the criteria Student signature: Date: Assessor signature: Date: Assessor name: Student Description of activity undertaken Assessment & grading criteria How the activity meets the requirements of the criteria Student signature: Date: Assessor signature: Date: Assessor name: Student Description of activity undertaken Assessment & grading criteria How the activity meets the requirements of the criteria Student signature: Date: Assessor signature: Date: Assessor name: Student Description of activity undertaken Assessment & grading criteria How the activity meets the requirements of the criteria Student signature: Date: Assessor signature: Date: Assessor name:  Summative Feedback: Grade:  Resubmission Feedback: Assessor Signature: Date: 28 | P a g e Day 3: Teambuilding These slides we create by Google Slides: https://drive.google.com/file/d/1rRRnwu7NboOj2eWPgMUGvgn7B-zBW4-g/view?usp=sharing 29 | P a g e 30 | P a g e 31 | P a g e 32 | P a g e 33 | P a g e 34 | P a g e Day 4: Hackathon These slides we create by Google Slides: https://docs.google.com/presentation/d/1Gyyl25fBbglXJZkJA6J7M6K_GZNdeEPx5VXcndlpceI/edit?usp= sharing 35 | P a g e 36 | P a g e 37 | P a g e 38 | P a g e CHAPTER 4: PROJECT CLOSURE Lessons learned Lessons Learned 1.1 Did the delivered project meet the specified requirements and goals of the project? Was the customer satisfied with the end product(s)? If not, why not? The goals of the project were to introduce the IoT industry to the employees, train the work’s skill, let the employees familiarize to the work environment and celebrate team building The director was satisfied with the employees’ skills after training 1.2 Were costs budgets met? If not, why not? The budgets were over 1.900.000 VND than expected 1.3 Was the schedule/timeline met? If not, why not? Some the schedule of the project was later than scheduled 1.4 Were risks identified and mitigated? If not, why not? The problem of equipment failure has been proposed and the event has encountered some equipment problems, but those problems have been resolved quickly because of the identified risks 1.5 What bottlenecks or hurdles were experienced that impacted the project? The devices of the hotel had problems (Internet, light, electric), it took times for repairing A coach was busy, come later make the schedule become longer 1.6 What could be done differently on the project? Organize a Hackathon: all teams use C#, JS, HTML/CSS, C++, Python to code Present the IoT product to choose which team is the best Reward for the best team Table - Lessons learned (its.sfsu, n.d.) 39 | P a g e Closure Checklist Closure Checklist # Item Yes/ No Comments (if any) 11 12 13 14 15 16 Completed any outstanding tasks Completed any pending deliverables Identified and documented all outstanding issues Assigned unresolved issues to relevant resources Obtained Project Sign-Off Paid all invoices Held lessons learned meeting with the team Communicated project’s closure with the stakeholders Gathered all project metrics Archived information in project repository Stored all hard copies in designated areas Released project team Closed the project formally Celebrated success! Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Table - Closure Checklist (its.sfsu, n.d.) 40 | P a g e CONCLUSION The event was going on as expected despite some unexpected incidents But the organizers have also achieved the right goal from the beginning that is to provide knowledge about IoT and knowledge of professional practice for employees After this event, Gree Tech employees will work and operate better, the company's productivity will be higher 41 | P a g e References its.sfsu (n.d.) Retrieved from its.sfsu: https://its.sfsu.edu/sites/default/files/SFSU%20Project%20Close%20Checklist%20Template%20v 0.4.docx nyu (n.d.) Retrieved from nyu: https://www.nyu.edu/content/dam/nyu/hr/documents/Project_Charter_Template.doc teamgantt (n.d.) Retrieved from teamgantt: https://www.teamgantt.com/free-gantt-chart-excel-template 42 | P a g e ... Guide places and seats Introducing event content and speaker and staff will give the agenda paper The speaker will talk about c programming Mini game Break and have lunch Take attendance Training. .. 41,800,000 CHAPTER 2: PROJECT PLANNING Project Gannt Chart Figure - Team Gannt chart (teamgantt, n.d.) Figure - Team Gann chart schedule 7|P age Schedule days event Day No Time Activity Note... food quality first Low After event Customer care issues Event Staff and Venue Staff Medium Should be patient and create a professional attitude Low During event External factors Internal factors