How we cut our release cycle in half
We moved from monthly releases to two a week. Here is what changed in our branching, reviews and testing, and what we dropped.
One-click importers, ready-made templates and guided onboarding get most teams fully running on Halo Works on their first day.
Weekly reports build themselves from finished work and land in inboxes every Monday.
SAML sign-in with your identity provider and automatic user provisioning, included in Business.
Cycle time, workload and blockers for every team, refreshed every fifteen minutes.
For solo founders trying it out
For small teams of up to 10 people
For companies that need SSO and audit logs
Release notes, workflow guides and stories from teams who use Halo Works every day.
We moved from monthly releases to two a week. Here is what changed in our branching, reviews and testing, and what we dropped.
Two hundred releases taught us to ship smaller, write the release notes first and never deploy on a Friday afternoon.
From auto-assigning bug reports to nudging overdue reviews, these seven rules save a typical team about five hours a week.
Offline mode, a rebuilt timeline view and built-in time tracking top the list. Here is what is coming and roughly when.
From auto-assigning bug reports to nudging overdue reviews, these seven rules save a typical team about five hours a week.
Two hundred releases taught us to ship smaller, write the release notes first and never deploy on a Friday afternoon.
Lead with the decision you need, keep it under 150 words and link to the detail instead of pasting it in.
Straight answers about billing, data security and moving over from your current tools.
New features, workflow templates and one useful idea for running your team, once a month.
Set up your workspace this afternoon and cancel next week's status meeting.