November 2025 Summaries

Swarmia, a tool designed to optimize engineering workflows, is used by its own engineering organization to enhance collaboration and efficiency, particularly as the company has expanded across multiple product teams. The platform adapts to each team's unique workflows, offering features like Slack notifications and a pull requests view to streamline the code review process, which currently averages a cycle time of 29 hours. Swarmia facilitates cross-team collaboration by automatically notifying relevant teams of changes to shared code through GitHub integrations. It also provides an investment balance view to track how engineering time is allocated, helping teams maintain focus on customer-facing goals versus internal improvements. The initiatives view and retrospectives assist in tracking strategic projects and improving processes, while developer experience surveys offer qualitative insights into tool effectiveness and areas needing attention. Swarmia's flexibility allows teams to tailor its use to their specific needs, and the company offers a 14-day free trial for those interested in exploring its potential benefits.

Swarmia's approach to hackathons, integrated into their bi-annual company offsites called SwarmUp, emphasizes cross-functional collaboration and rapid experimentation without the pressure of immediate production readiness. During these events, every team member, regardless of role, can pitch ideas, and teams form around the most popular concepts to experiment and innovate. This inclusive culture fosters an environment where projects can quickly move from concept to prototype, sometimes becoming customer-facing features, like Hugo's AI-powered tool for linking pull requests to issues. The hackathons highlight gaps in the company's prioritization process, enhance understanding of their product, and validate their product philosophy by demonstrating that giving employees the autonomy to tackle problems leads to valuable solutions. Swarmia supports this innovative spirit year-round by reserving time for exploration and using feature flags to safely test new concepts, ensuring a continuous loop of idea generation and implementation.

Story points, originally created to provide an abstract measure of effort in software development without committing to specific timelines, have become a contentious issue in engineering organizations, often leading to miscommunication and misaligned expectations. They are criticized for conflating complexity, time, and risk into a single number, which creates ambiguity and false precision. This has led to the misuse of velocity for comparison, encouraging teams to inflate estimates to protect perceived output, ultimately diverting focus from delivering actual value. Instead of relying on story points, measuring work cycle time and analyzing developer activity, such as through Swarmia's FTE model, provides more accurate insights into productivity and effort distribution. This shift allows teams to forecast completion dates based on historical data rather than unreliable velocity estimates, enabling more meaningful conversations about improving workflow efficiency. By focusing on actual work progress and bottlenecks, teams can better address systemic issues and enhance their ability to deliver value, moving away from the outdated reliance on story points towards a more data-driven approach to project management.