팀에 작업 트래커가 있어도 내가 개인 작업 로그를 유지하는 이유

Source: Dev.to

In every project I maintain a simple table for myself: the planned work for the week/sprint and what I actually completed. Even when the team uses a task tracker, this personal log provides several benefits.

Visibility and self‑reflection

• Management visibility – The log can be shared to show workload and hours if needed.
• Personal insight – It helps me see my accomplishments over time, especially when day‑to‑day tasks feel routine.

Real‑world example

Last year I joined a development team to handle DevOps tasks and started keeping this table:

• First three weeks – While onboarding on my own, I built a modular CI/CD pipeline template from scratch. It became the company standard: a catalog of separate actions that can be assembled like building blocks, requiring only a short list of variables from developers.
• Architectural decision records – I introduced and established the practice of recording ADRs for infrastructure and DevOps work, along with templates for standard projects across different languages and frameworks.

These contributions were evident only when I reviewed my personal log; the team’s task tracker did not capture them clearly.

Recommendation

• Maintain your own activity log – Tasks in a shared tracker can become visually lost among sprints, columns, and numerous tickets. Some real work never makes it into the tracker.
• Data‑backed conversations – Although it requires a small amount of extra time, a personal log stays with you and highlights the actual work you’ve done, providing concrete data for performance discussions.