Maintain project timekeeping and any project-related expense records in a consistent format throughout the course.
Timekeeping should follow the agreed project convention:
- grouped by sprint where helpful
- one entry per task or meeting
- date + short activity description + time spent
- 30-minute precision
A good entry should be specific enough to show what was done, for example:
- implement single-turn API client interface
- attend sprint review session
- define structured logging format
- refine project issues
Deliverable
Up-to-date timekeeping records for all team members and an expense record if any costs occur.
Acceptance criteria
- Team members use a consistent logging format.
- Time is logged with 30-minute precision.
- Entries are specific enough to describe the actual work performed.
- Timekeeping remains up to date throughout the project.
- Any project-related expenses are recorded separately if applicable.
Maintain project timekeeping and any project-related expense records in a consistent format throughout the course.
Timekeeping should follow the agreed project convention:
A good entry should be specific enough to show what was done, for example:
Deliverable
Up-to-date timekeeping records for all team members and an expense record if any costs occur.
Acceptance criteria