1. Dedicated resource agreement
1.1. 1. General Info
1.1.1. 1.1 Level resource
1.1.1.1. Senior
1.1.2. 1.2 Type resource
1.1.2.1. Dev
1.1.3. 1.3 Rate
1.1.3.1. 18 USD/hour
1.1.4. 1.4 Working Location
1.1.4.1. Resource work at CM's office
1.2. 2. Business
1.2.1. 2.1 Contract Duration
1.2.1.1. At least 3 months contract
1.2.2. 2.2 Workload
1.2.2.1. At least 100h/month
1.2.2.2. Payment for 100h/month
1.2.2.3. If workload is larger than 100h/month
1.2.2.3.1. Normal date: rate x1
1.2.2.3.2. OT
1.2.2.4. Reset workload every month
1.2.3. 2.3 Payment
1.2.3.1. Payment 100% early of the month
1.2.3.1.1. Example
1.2.3.2. Process confirm timesheet
1.2.3.2.1. CM will submit timesheet of the previous month before 2nd of the next month
1.2.3.2.2. PM / Contact point of TCC will check and approve the timesheet within 3 working days
1.2.3.2.3. If total effort is <= 100h
1.2.3.2.4. If total effort > 100h
1.2.3.3. Reminder
1.2.3.3.1. If the payment is late more than 3 working days, CM will send a reminder #1
1.2.3.3.2. If the payment is late more than 5 working days, Cm will send reminder #2; and resource of CM will pending until the payment is processed
1.2.4. 2.4 Contact point
1.2.4.1. CM
1.2.4.1.1. Business
1.2.4.1.2. Technical
1.2.4.2. TCC
1.2.4.2.1. Business
1.2.4.2.2. Detail
1.3. 3. Operation
1.3.1. 3.1 Scope of Work
1.3.1.1. CM Dev
1.3.1.1.1. Review and give ETA of each ticket
1.3.1.1.2. Discuss with CM' tech lead about solutions (if any)
1.3.1.1.3. Implement task
1.3.1.1.4. Unit test task and comment with screencast and test link to the ticket
1.3.1.1.5. Check and fix feedbacks from TCC Team
1.3.1.1.6. Answer the question of TCC Team as a highest priority ticket
1.3.1.2. TCC
1.3.1.2.1. Work with end-client to collect requirements
1.3.1.2.2. Assign task to CM Dev
1.3.1.2.3. Describe the task and expected result of the task
1.3.1.2.4. Confirm ETA or Deadline with CM Dev
1.3.1.2.5. Planning task weekly/monthly for CM Dev
1.3.2. 3.2 Process to receive and implement tickets
1.3.2.1. Step 1: TCC Team create a new ticket on Jira
1.3.2.2. Step 2: CM Dev check and give ETA of ticket
1.3.2.3. Step 3: TCC Team check and discuss ETA/Deadline with CM Dev if needed
1.3.2.4. Step 4: CM Dev implement the ticket
1.3.2.5. Step 5: CM Dev log work to the ticket right after finish implement ticket
1.3.3. 3.3 Task assigning
1.3.3.1. Jira provided by CM
1.3.4. 3.4 Workflow of ticket
1.3.4.1. Note: Ticket workflow
1.3.5. 3.5 Monitoring
1.3.5.1. Nhu Le will check the Ticket Board every week and remind the CM Dev if any ticket is missing
1.3.5.2. CM and TCC will have an Skype group for priority of ticket and urgent request (just to notify)
1.3.6. 3.6 Response time
1.3.6.1. Chat
1.3.6.1.1. Within 1 working hours
1.3.6.2. Email / Jira
1.3.6.2.1. Within 2 working hours
1.3.6.3. Jira ticket
1.3.6.3.1. Make sure all questions are made and answered on the same day
1.3.7. 3.7 Reporting
1.3.7.1. Daily via Jira task update/comment
1.3.7.2. Weekly via timesheet
1.3.8. 3.8 Estimate time for new project
1.3.8.1. Within 1 working day if the project is small (the estimation effort will be counted to the timesheet of the resource)
1.3.8.2. Within 3-5 working days if the project is large and complex (the estimation effort will be counted to the timesheet of the resource)
1.3.9. 3.10 Communication
1.3.9.1. Jira
1.3.9.1.1. Confirm scope, timeline
1.3.9.2. Chat
1.3.9.2.1. Summary priority and notify
1.3.9.2.2. Tool
1.3.9.3. Phone
1.3.9.3.1. Urgent only
1.3.9.3.2. CM
1.3.9.3.3. TCC