Time and Capacity

Corrective work consumes time that the delivery team needs to explain. A time entry records the team member, work date, hours and project, with an optional task reference. The description states what the person worked on. Billable or Non-Billable provides the classification used in the team’s effort review. Task actual hours remain a separate measure alongside the time booked through these entries.

Submitted entries pass through the Time Entry Approval workflow. It automatically approves an entry when its hours are positive and it is still Submitted, then records decision and operation evidence. Invalid hours or an entry that no longer has the required state produce a failed attempt. The team should inspect that result before assuming an entry was accepted.

• Effort capture. Developer records the work date, positive hours and the project receiving the effort. Link the corrective task when appropriate and describe the work performed. Check that the task belongs to the same project before relying on the entry in project reporting.
• Submission result. Move a prepared entry from Draft to Submitted and read the resulting operation evidence. A successful validation advances it to Approved. A failed attempt needs investigation; the team must not infer a rejection decision merely from a failed receipt.
• Workload context. Delivery Lead and Project Manager compare assigned task estimates and actual hours with each team member’s weekly capacity. Check the dates and active workload before interpreting the comparison. A total of assigned effort can span several weeks and needs that context before a staffing decision.

Agree how people describe time spent investigating, implementing and checking a defect. Decide when they book the work and how they choose the project and optional task. Define Billable and Non-Billable for your operating process, and keep this classification consistent when reports are reviewed.

Clarify how task actual hours and booked time are maintained. Do not assume they are interchangeable or that changing one automatically updates the other. Agree the period used for workload discussions and the way weekly capacity is recorded for each team member. Confirm who investigates failed time-entry operations and how corrected entries are submitted without losing the earlier attempt’s evidence.

The Developer records the time spent correcting the checkout discount defect, with the checkout project and corrective task selected. The work date and description explain the effort. On submission, positive hours pass validation and the entry becomes Approved. Project Manager inspects the resulting decision and receipt, then compares the booked effort with the task’s actual hours.

Repeat the case with zero hours. The workflow should record the failed attempt without a successful approval. Then invoke the check against an entry that is already Approved; it no longer meets the Submitted-state guard. Finally, examine the Developer’s assigned task estimates against weekly capacity. Review the task dates before deciding whether the apparent workload represents the current week or work planned over a longer period.

• Timesheets Awaiting Approval — Submitted entries waiting for the validation result or investigation of an unsuccessful attempt.
• My Time Entries — A team member’s dated effort records with project, task and result state.
• Team Capacity — Weekly capacity alongside assigned work and recorded effort for staffing discussions.

Rehearse time submission and validation and include the resulting effort position in project delivery review.