My Workflows During the Quarantine

Covid has deeply affected our daily lives. However, in retrospect, it also had a surprisingly small impact on how we get the work done at TIMETOACT GROUP Austria.

We have the less cognitive capacity to focus on work these days. Focus itself is more fragile and schedules are less predictable. Yet the tools, connections, and workflows that we’ve been employing demonstrate resilience in the face of the crisis.

Please note that there are multiple teams working on a variety of projects. Things mentioned below don’t apply to the entire company (teams can steer towards different tools, programming languages, and workflows). 

“We”, for the purpose of this article is “a small team that focuses on data science projects for one particular customer”. 

However, if it is of any indication, I don’t think the workflows have changed drastically for the rest of the company as well.

Project Management

I use a private Notion workspace as a glorified journaling solution to track the progress across multiple projects. For each project there is a separate page in the following structure:

  • Header: 

    • current status summary (once sentence, that is rewritten on any major change);

    • list of JIRA tickets (closed tickets are left but crossed out);

    • links to any Confluence pages, deployments, repositories.

  • Journal - whenever something important happens (communication with some outcomes, project delivery, work milestone), I write down data and a couple of sentences about that. 

All projects are listed within the workspace, using their titles and status icons to distinguish between:

  • ongoing work;

  • waiting for something (feedback from another team, clarification, data upload approval);

  • paused (due to the priority change);

  • project lead;

  • closed.

We usually don't have that many projects being active in parallel (5 is the top), making it trivial to review the progress and sync up with the project stakeholders as needed.

I'm half-heartedly considering reimplementing this setup in a self-hosted Ruby-on-rails app. This would allow us to include more sensitive things in project logs: like data file samples, code snippets. However, links to the data lake work well enough for now.

Work Coordination

Actual work coordination happens in JIRA. Next actionable steps for a project are broken down into tasks. After the necessary requirements are gathered, they are written down in a JIRA task and passed to somebody for the implementation.

We are working in tight contact with the customer, so the planning horizon is usually short - one-two weeks (during the emergencies I’ve seen it go down to a couple of days). There are no explicit iterations, we just focus on maximizing the throughput of work being done.

We have a simple kanban board that tracks the ongoing work. JIRA tickets are referenced in the Project Summary in Notion, making it easier to dive into the task details, if needed for the review.

There are Confluence and Bitbucket - standard setup these days.

Communications

Most of our communication happens in the chats:

  • Teams (company chat);

  • Telegram (our team and important Grafana alerts)

  • Slack -> WebEx Teams (customer chat). 

A few years ago I would've been terrified at the need to run multiple chat clients of various fidelity. These days I find it convenient to have context separated in different chats with drastically different UIs. Focusing is easier this way.

We have a company-wide Teams call on Mondays - to catch up with colleagues around the world, see their faces and hear voices. Plus, it is an opportunity to share some news, exciting hobby project or frustration with a particularly pesky integration.

Then there is a biweekly coordination call with the customer (with a tendency to be canceled, since projects and priorities are usually set clearly enough to get straight to work).

There are occasional unscheduled work-related calls, but they are pretty rare. On average, I jump to a call once per two weeks, just to spend 10-15 minutes clarifying the big picture across projects or troubleshooting some specific edge case.

During the COVID lockdown, we started doing semi-regular "coffee" calls with the team. Their purpose is to take a break, connect and think aloud through the problems or next steps we are going to take.

Development Environment

These days most of my time is usually spent outside of the coding. It is talking, writing or troubleshooting things. These activities could be done with an iPad (with a mechanical keyboard) or even a phone (Google Pixel 3a, in my case).

I find that I'm using my phone for work more frequently during the COVID-lockdown. With it you need just one hand to answer a question, pass the information or assist a team-mate (the other hand could still be used to prevent 1yo from doing whatever he intends on doing).

When actual development has to be done, it always happens on 13' MacBook Pro (2015, without the touch bar). Software being used: iTerm2, vim, GoLand, and PyCharm. 

A surprisingly large portion of work happens within the browser: Google Cloud Platform, Apache Airflow, Jupyter notebooks, Jenkins, Grafana, Confluent Kafka, Kubernetes Dashboards and (of course) StackOverflow. Safari is my main browser, while the Firefox (with Containers extension) is used to manage separate login contexts.

I still use Emacs org-mode to handle timesheets, no actual development happens there.

There is a special place in my heart for Wireshark. A non-trivial amount of problems is network-related. Besides, there was that case when two Kafka clients (both non-librd) exhibited exactly the same bug in client-server interactions. Only the Wireshark helped to identify the root cause while keeping the sanity.

Wireguard and mosh play a particularly important role in the work - I have a dedicated work server with 8 cores and 16GB of RAM. It is located in Germany (close to the actual work site) and runs resource-intensive docker builds or computations.

All this setup has worked rather well before the COVID lockdown started, and it keeps on working fine. In the upcoming months, I (hopefully) don’t expect to see any major changes in the way the work is done. 

Blog 5/25/21

From the idea to the product: The genesis of Skwill

We strongly believe in the benefits of continuous learning at work; this has led us to developing products that we also enjoy using ourselves. Meet Skwill.

Headerbild zu Smart Insurance Workflows
Service

Smart Insurance Workflows

Using a design thinking approach, we orient workflows to the customer experience and design customer-centric end-to-end processes.

Referenz

Consulting on the ivv collaboration strategy

The future collaboration of ivv is characterized by modern communication and collaboration tools. It is defined for cross-organizational work in association and with external parties.

Referenz

The digital customer file with IBM Content Manager

The prefabricated house specialist SchwörerHaus KG has relied on IBM technology for many years to set up a digital customer file.

Unternehmen 1/19/23

Sustainability in the TIMETOACT GROUP

Sustainability is one of the big topics of our time and we also want to get involved and face up to our responsibility as TIMETOACT GROUP. Find out everything about our sustainability activities here.

Blog 10/11/22

Introduction to Functional Programming in F# – Part 5

Master F# asynchronous workflows and parallelism. Enhance application performance with advanced functional programming techniques.

Kompetenz 8/5/21

Shaping the future with technology

ARS Computer and Consulting is one of the leading companies in the field of software engineering. Our mission: The Art of Software Engineering. This includes high-quality consulting and successful projects for the agile development of high-quality software.

Referenz 2/24/22

Modern and user-friendly service portal

TIMETOACT implements a new service portal for FitX with Jira Service Management, replacing the former system in a short time. With the modern and user-friendly Atlassian tool, problems, malfunctions and damage can be easily reported and specifically processed in all 95 fitness studios in the future.

Referenz 4/13/23

The new Idea and Innovation Management of the DDPS

The new solution is available to employees in the familiar portal and in the same design. It is very easy to use and adapted to the needs of the role holders. It was easy to move away from the old platform. The switch to the new solution is rated very positively by all roles.

Blog 8/10/22

So, I wrote a book

Join me as I share the story of writing a book on F#. Discover the challenges, insights, and triumphs along the way.

Blog

Working across the Atlantic: an interview with Bill

What is it like to work for a German company as an American? We asked our American teammate Bill. The change from American to German work culture can be an exciting challenge. In our latest interview, Bill shares how he experiences these cultural differences, what has surprised him, and how he has integrated into the German way of working. Dive into the exciting dynamics of intercultural work!

Branche

Digitization of the energy industry

The energy sector is undergoing an unstoppable process of change. Progressive digitization and the energy transition are causing traditional system and process boundaries to disappear.

Branche

Healthcare

IT and digitalisation are too often seen in Germany as pure cost drivers, without taking into account the revenue opportunities and potentials. We know the challenges in the healthcare sector and help you find the best IT solutions.

Headerbild zu IBM Cloud Pak for Data Accelerator
Technologie

IBM Cloud Pak for Data Accelerator

For a quick start in certain use cases, specifically for certain business areas or industries, IBM offers so-called accelerators based on the "Cloud Pak for Data" solution,

Referenz

Smarter mobility with the portal switchh

Subway, S-Bahn, bus, car, ferry or bicycle: The pilot project "switchh" of HOCHBAHN in cooperation with Europcar and Car2Go makes Hamburg mobile.

Two people discussing in front of a computer
Lösung 2/14/22

The COBOL Survival Team for IBM i (AS400)

COBOL developers on IBM i (AS400) are a rare commodity. PKS provides a powerful team especially for this application!

Training

Getting More from Jira Workflows (Cloud)

Over the course of the "Getting More from Jira Workflows (Cloud)" training participants will learn about common status and transition properties and advanced workflow functionalities and how to configure them.

Training

Getting More from Jira Workflows (Cloud)

Over the course of the "Getting More from Jira Workflows (Cloud)" training participants will learn about common status and transition properties and advanced workflow functionalities and how to configure them.

Headerbild zu Digitale Transformation bei Versicherern
Leistung

Mastering digital transformation in insurance

Versicherer haben daher bereits die Chancen und Notwendigkeiten der Digitalisierung größtenteils erkannt. Trotzdem ist noch viel zu tun, denn Digitalisierung funktioniert nicht von einem Tag auf den anderen – besonders bei Versicherungen, bei denen es viele altmodische und langsame Prozesse gibt.

Referenz 3/28/22

24/7 support guarantees stable operation of the intranet

The experts took over the operation of HCL Connections in the fall of 2020 and have since ensured the fail-safe stability of the platform.

Bleiben Sie mit dem TIMETOACT GROUP Newsletter auf dem Laufenden!