add Kimai to tools section (#23)

* add Kimai to tools section

* add Kimai subsection

* update link to How we use Kimai

* rephrase a sentence in How we use Kimai

* update Kimai description in Tools

Co-authored-by: Bernard Halas <bernard.halas@berops.com>

* change How we use Kimai to Timesheets

Co-authored-by: Bernard Halas <bernard.halas@berops.com>

* add Timesheets to ToC and place the section after Communication

* rephrase approach on logging time in Timesheets

---------

Co-authored-by: Bernard Halas <bernard.halas@berops.com>

README.md

@@ -6,6 +6,7 @@
 - [Git](#git)
 - [Development in Go](#golang)
 - [Communication](#communication)
+- [Timesheets](#timesheets)
 - [Your Friday](#yourfriday)
 - [Remote Kanban DevOps house](#remotekanban)
 - [Interviews](#interviews)
@@ -20,7 +21,7 @@ We use:
 - [GitHub](https://www.github.com/berops) for private and public git repositories
 - [GSuite](https://gsuite.google.com) for mailbox, cloud storage and other office tools
 - [Google Cloud Platform](https://cloud.google.com) for hosting our infrastructure
-
+- [Kimai](https://www.kimai.cloud/) for recording worked hours. Find information on usage [here](#timesheets)
 
 <a name="2fa"/>
 
@@ -62,6 +63,10 @@ Our communication "defaults to open". This means that by default every informati
 2. Quality decisions - in a transparent world we're expecting that we get a constructive feedback and we're able to steer the decisions accordingly
 As Slack is our communication tool of choice, we take the advantage of `huddle`s. Anybody is welcome to join any huddle.
 
+## Timesheets
+
+We employ the [Kimai](https://www.kimai.cloud/) time tracking tool to document work hours. Unlike certain real-time tracking tools that monitor time and capture your screen as you work, we log time manually in Kimai. This respects employees privacy, and we can use the time data for payroll and customers invoices, which helps us to be clear about the work that's been done.
+
 <a name="yourfriday">
 
 ## Your Friday