Harvest: Reporting Hours
Love your job. Report your time accurately.
Understanding the investment of our time is the foundation of a polished process in the company. Some of the examples of a good usage of these reports are:
Time spent on projects: development, UX/UI, QA, PO/SM, shadowing.
Helps us keep our projects on time and within budget.
Resources utilization and allocation.
Vacation, sick leave, etc.
Rules#
Each person must report ALL of the hours worked
during the week. They should always add up to a minimum of 40 hours/week.
If you are on vacation, sick leave, personal day, etc.
use the Talos Digital > Holidays / sick leave / vacation project to log your hours. This will ensure we see your 40 hrs that week.
The description fields on time entries are NOT
optional, they're required.
Entries should be specific to a task and include a
brief note or ticket reference.
Entries should NOT be a large block of time without
details. In other words, break up your 8-hour day.
Fill in your entries DAILY. Much easier than trying to
remember what you did 5 days ago.
Watch out! do NOT "Submit for Approval" until you
finish the weekly hours report.
You have to SUBMIT your weekly timesheet every
Friday.
IF YOU DON'T HAVE PROJECT ASSIGNED, SAY SO.
Internal meetings to discuss an approach or
brainstorming on a project are usually reported under "Development".
Important: Every Monday we check all timesheets and we expect to see a minimum of 40 hours for each of you, so make sure you do it right.
Example of Descriptions
JIRA ticket link & number
Fixing an issue
Specific features
When you are using an external tracking system (provided by Client)
Make sure the entries are identical in both the externaltracking system and Harvest.