Like many development teams, we have a lot of work to do - pretty much all the time. We work in short weekly sprints, called ‘heats’ (like heats - when a swimming event has more swimmers than available lanes….) The heat Every week we release a minor version update and work a week ahead of schedule to plan for our next release. To ensure we are all aligned with Swimm’s strategic direction, the squad meets together to define KPIs and discuss goals and priorities. • Sundays at Swimm: •  - We stress-test new versions about to be released; this now includes expanding coverage of automated tests.; • Mondays at Swimm: •  - We plan the week and start the sprint (Heat): developers work on aspects of the code needing attention, ; • write documentation,: •  and research new technologies.; • Tuesdays at Swimm: •  - We move on to development according to our product roadmap. We start with a daily sync, and then each developer dives into research and development through the rest of the week.; • Wednesdays and Thursdays at Swimm: •  - These days you can find us getting our hands dirty developing new features and fixing bugs. • Sundays at Swimm: •  - We stress-test new versions about to be released; this now includes expanding coverage of automated tests.; • Mondays at Swimm: •  - We plan the week and start the sprint (Heat): developers work on aspects of the code needing attention, ; • write documentation,: •  and research new technologies.; • Tuesdays at Swimm: •  - We move on to development according to our product roadmap. We start with a daily sync, and then each developer dives into research and development through the rest of the week.; • Wednesdays and Thursdays at Swimm: •  - These days you can find us getting our hands dirty developing new features and fixing bugs.;Major releases Every two months, we release a major version update that focuses on several larger additional features in Swimm’s product. Between the majors Between two major releases, we have “between the majors” - an R&D-focused development week. We call it “Dire Straights” even though it’s actually an enjoyable week. We use the time to make improvements and optimizations, do large refactors of the code base, and introduce new technologies, upgrades, and resolve technical debts. Swimminars Every two weeks, a Swimm team member gives a Swimminar (Swimm seminars) about something (pretty much really anything) related to our Swimm product - but which is not part of our daily work. Check out our blog for some examples of our recent Swimminars.