1. Customer
1.1. Requirement Specification
1.1.1. Exact Requirement/ if one of the function not sure to change, inform it point out early
1.2. 3D Object(texture /Material) with Eng Version
1.3. Screenshot / Capture from Real Environment
2. MD
2.1. Inititating
2.1.1. Machine Support
2.1.1.1. Windows Laptop that can install 3Dapplication
3. QAM
3.1. Initiating
3.1.1. Participate the KickOff Meeting
3.1.1.1. Define Risk Management
3.2. Monitoring & Controlling
3.2.1. Confirm the Tasks and Assign/ Schedule
3.2.1.1. Track the Team Progress with Updated Schedule
3.2.1.1.1. if Delayed, Remind to Team Leader to discuss with member
3.2.2. Control the Test Plan/Bug List and Finding List
3.2.2.1. if delayed/ remind to Team
3.2.3. when customer change the requirement, Hold the meeting with Team
3.2.3.1. to discuss which will impact and what kind of request needs to ask to customer
3.2.3.1.1. Confirm the Deadline Changes
3.2.4. Check the collection of Changed requirement from customer
3.2.4.1. Inspection Process before released to customer
3.2.5. Record the Customer bug and Defect
3.2.5.1. Discuss with member
3.2.6. Hold Team Progress Meeting, if need
3.3. Executing
3.3.1. Control Quality
3.3.1.1. Checking the Pre-Inspection
3.3.1.1.1. Team needs to send the product (function by function/ module by module)
3.3.1.2. Check Team Progress and Performance
3.3.1.2.1. Team Reason/Member Reason
3.4. Closing
3.4.1. Final Inspection
3.4.1.1. Prepare to send Customer Satisfaction Survey
4. Team Member
4.1. Planning
4.1.1. investigate the Document Specification
4.1.1.1. Explain and Discuss how to understand at Kick Off Meeting
4.2. Executing
4.2.1. Follow Team Lead's Schedule and Assign on Time
4.2.1.1. if Delayed, obey the action by TL
4.2.2. Record the Finding from customer and Japan Side separately
4.2.2.1. Confirm with Team Leader and Solve
4.2.3. Update the Progress on Schedule Plan
4.2.3.1. If delayed, give the reason and follow the action by TL
4.2.4. commit the creation at created folder by TL
4.2.4.1. if wrong or forget to collect the old version, Tell the reason
4.2.5. Repaired all bug and finding from QAM and Tester
4.2.5.1. all solution must filled out
5. Tester
5.1. Planning
5.1.1. Investigate the Document to under the project
5.1.1.1. Join the Kick Off Meeting
5.2. Testing
5.2.1. Follow the Testing Plan and Schedule
5.2.1.1. Test (Machine/Laptop)
5.2.2. Record the Bug
5.2.2.1. Confirm all bug has clear or not
5.2.2.1.1. Confirm all bug are modified
5.2.3. Create the Evidence
5.2.3.1. do as Team's request if need
6. Team Leader
6.1. Initiating
6.1.1. analysis the Requirement Documentation with our Request File
6.1.2. Organize the Kickoff Meeting
6.1.2.1. Confirmation the result and risk
6.1.3. Communication with Customer
6.1.3.1. Confirm with customer about Requirement Specification
6.2. Panning
6.2.1. Plan Schedule and Assign Management with Members
6.2.1.1. Share the information to member
6.2.2. Communication
6.2.2.1. Confirm and adjust the Deadline with customer
6.3. Executing
6.3.1. Tracking each member progress with Schedule
6.3.1.1. Take the action with 5 Why tool if Delayed
6.3.2. Team Leader Review
6.3.2.1. Technical and all finding are clear
6.3.3. Sending the Q&A to customer
6.3.3.1. Analysis the Issue and Solution
6.3.4. Checking the Changed Requirement from customer and adjust the schedule date
6.3.4.1. Assign to Member
6.3.5. Build the folder (beget folder by date)
6.3.5.1. if member didn't follow, take the action
6.4. Closing
6.4.1. Confirm the Finding/Bug/Defect from customer and Japan Side
6.4.1.1. Check all are confirm or not