ARION
Digital Presence & Branding
SPARK
Marketing & Growth Systems
OLIVER
Operations, Admin & Execution
STELLA
Data Intelligence & Analytics
FORGE
Custom Apps & Integrations
ARGUS
Automation & Orchestration
SPARK — Marketing & Growth Systems
Turn contacts into loyal customers with automated, data-driven marketing.
FORGE — Custom Apps & Integrations
Build exactly what your business needs, connected to every tool you use.
ARGUS — Automation & Orchestration
The intelligence layer connecting every platform, automatically.
One login. One data model. Six platforms. Zero app-switching. Explore the full ecosystem →
Build Your Brand
Presence, Visibility & Growth
Build Your Foundation
Operations, Process & Workflows
Build Your Clarity
Reporting, KPIs & Data Strategy
Build Your Engine
Integrations, Automation & Tech
HomeSignal › How We Run Engineering Without Sprints, Standups, or Story Points

How We Run Engineering Without Sprints, Standups, or Story Points

Jordan Rivera··1 min read·3 views
Signal
DevOpsDockerDX

We didn’t set out to eliminate standups. We set out to eliminate wasted time, and standups were the clearest example of it we had. Fifteen engineers, fifteen minutes each morning — that’s nearly four engineer-hours per day of synchronous time spent on status updates that could be read asynchronously in three minutes.

What We Use Instead

Daily written updates, asynchronously. Each engineer writes two to three sentences: what they shipped yesterday, what they’re working on today, anything blocking them. Takes five minutes to write, takes three minutes to read the whole team’s updates. Net time saved: 60%.

Replacing Sprints With Shape Up

We run six-week cycles with two-week cooldowns, loosely inspired by Basecamp’s Shape Up methodology. Work is shaped and approved before any engineer touches it. This eliminates the mid-sprint scope creep and the sprint review theater that consumed hours of engineering time every two weeks.

The Result

We shipped more in the first two quarters of this system than in the previous two quarters of traditional scrum. More importantly, engineers reported higher satisfaction and less cognitive overhead. Process should serve the work, not consume it.

Jordan Rivera
Jordan Rivera
Senior software engineer focused on AI/ML infrastructure and developer tooling.

Related Posts