The document outlines a training program for project leaders on how to effectively review and manage timesheets, with a duration of one hour and conducted by Nguyen Thu Ha. It provides objectives, processes for recording and approving timesheet entries, common reporting practices, and addresses frequently asked questions. Key processes covered include project tracking, task management, and maintaining accuracy in reporting time spent on various project activities.

1. Timesheet training for Project Leader Version: 1.0 Author: Nguyen Thu Ha April 2005 Instructor: Nguyen Thu Ha Head of PQA Department © <year> FPT-SOFT 04e-BM/NS/HDCV/FSOFT

2. Introduction Duration : 1hours Purpose : Guide on how to review Timesheet Attendees : Project leaders

3. Objectives After the course, student will achieve (be able to): Review project timesheet Use the information from Timesheet to manage project effort.

4. Why? Ensure correctness and completeness of effort information to manage projects and improve processes Who? PL/PD When? Before 10:00 am every Monday Frequently Asked Questions

5. Actors Actor Action Staffs Record PL/Manager Review PQA Review & approve Senior Manager View http://fsoft-fms:9080/FSOFTInsightWeb/Fms1Servlet?reqType=1603

6. Work flow Reject Create Project Record Review/Approve by PL Approve by QA Report

7. What to record Date Project Process Work Description Time Work product KPA (entered by QA) http://fsoft-fms:9080/FSOFTInsightWeb/Fms1Servlet?reqType=1603

8. How to record (1) Project – What project your effort spent for Project: activities for specific projects Group: activities at Group-level, not specified for any project. Misc: others. Process – What activity you did Refer to next slides

9. How to record (2): Software Process Contract management: - Develop, review, approve Proposal - Contract relating activities … Requirements : - Identify or study Customer requirements - Develop, review & approve URD, SRS, Use case... - Develop Requirement prototype … Design : - Develop, review & approve Design document: ADD, DDD - Develop Design prototype

10. How to record (3): Software Process Coding : - Develop, review, approve Coding convention - Code Develop User manual, System description Deployment : - Develop Release note, Installation guide Pack the software package Deliver or deploy the software Conduct user training related activities Customer Support - Support after releasing software to customer

11. How to record (4): Software Process Test - Create & review Test Plan Develop, review, approve Test case, test data (Test tools) Execute test Make Test report Prevention - Develop DP Plan & Kick-off meeting Implement DP activities Causal analysis meeting Maintain DP Log

12. How to record (5): Software Process Configuration management Develop CM plan Set up environment and project directory Keep track status of CIs Baseline activities and report Project management - Develop, review, approve PP Project tracking, meeting and report Subcontract management

13. How to record (7): Other processes Training Study/learn technologies/processes/skills used for the projects Conduct training for team member Evaluate/report the training result

14. How to record (8) Type of Work - Study - Create - Review: review WPs created by OTHERS , not YOU - Test Correct: repair YOUR defects, not OTHER’S Work product - Work Order; Project plan - URD; SRS - ADD/DDD - Use manual; Software package - Test plan; Test case & test data; test tools - Release note; installation guide ....

15. How to Review & Approve Choose project name Choose TS records Review & update (if any) Approve TS Reject

16. How to Review & Approve Completeness Compare against project tasklist/schedule Report\Weekly\Lack of timesheet Report\Summary report\Account and date Correctness Verify against guideline, actual task assignment Approve by PL

17. How to use Report Summary report Summary report Report by Process and Type of work Work product and Type of work Kpa and Type of work Account and date Weekly report - Lack of Timesheet Pending Timesheet Inquiry report

18. Common TS defects Wrong logging 1. Code and unit test 2. Test and fix bug 3. Study or Review WPs 4. Translate mail 5. Working time: 4-8-12 Lacking 1. Review effort 2. CM effort: baseline, set up env, install tools

19. Resources & references Reference Fsoft RADIO Timesheet guideline Timesheet user manual http://fsoft-fms:9080/FSOFTInsightWeb/Fms1Servlet?reqType=1603

20. Questions and Answers