Disco is both an agency and a product company, so we've worked hard to find a development process and cadence that both serves the needs of our client but also respects the time and space needed for deep development work.

While we don't follow any particular Agile sect, as you'll see in our Principles of Project Delivery we have taken on board many of the original Agile Manifesto principles.

A typical cycle workload

Here's a (real-world) typical workload for a developer over a three week cycle:

• Dig into some issues preventing the synchronisation of order fullfillments for a high-volume merchant;
• Fine-tune some Postgres SQL queries causing performance problems in an application for a merchant with 500,000+ orders records;
• Complete the migration of credit card tokens from a bespoke system to Submarine, our payment platform product;
• Review various PRs from other team members;
• Start work on a brand-new Rails app using Webpacker, React and Polaris that will allow a client to manage their product cost of goods;
• Prepare a development plan for an upcoming project to build out a customer loyalty program for a site with hundreds of thousands of customers.

A typical cycle calendar

Here's that same developer's calendar for the same cycle:

• Week 1 (Jog Week)
• Week 2 (Sprint Week 1)
• Week 3 (Sprint Week 2)