Traverse Technologies

We work on 1 week cycles. Meeting on Monday morning where we write down all features and goals we want to accomplish. Daily stand up on progress and requests for help if you are stuck. Friday postmortem meeting on a) either completion of feature or b) discussion on what challenges remain to finish it next week (or to make the issue smaller).

We use a) a Digital Twin document and b) Pivotal Tracker as our main sources of spec clarity. The entire company is an attempt to automate and mimic real physical world manual processes so the Digital Twin spec is the end user requirements equivalent of documentation. Pivotal tracker is the means to break down the larger user story into small pieces of the exact work that has to be completed.

• We have to deal with very large weather datasets and also very large permutations of project configuration possibilities.
• We have to understand non software real world physical processes (both technical and social) that are not daily-life-intuitive (e.g. bird counting as part of environmental impact analysis) and translate them into interfaces and automation that helps our end users.
• We have to string many different domains of expertise together - some are very large and specialized stand alone software such as modelling of power systems, Microsoft Excel etc.
• We have to interface with data collection devices - be it normal camera capture, LIDAR, land surveys with calibration points, rain gauges etc. and ensure seamless and consistent data formats and ingestion interfaces.
• There is a huge amount of statistics and probability involved.