December 2024 Summaries

Mergify transitioned from a traditional Agile approach to a more structured, project-driven workflow to better balance ownership, clarity, and autonomy while maintaining productivity and motivation. This new system addresses the limitations of a purely task-based approach by grouping related tasks into projects, each lasting two to four weeks, providing clear goals and direction. Key elements include a project brief to outline problems and goals, a project lead responsible for updates and decision-making, and deadlines to encourage realistic trade-offs and prevent overengineering. This approach avoids the tunnel effect, fosters ownership and autonomy, and improves communication by focusing on meaningful discussions rather than constant status updates. While challenges remain, such as defining project scope and ensuring all engineers thrive under this system, Mergify is refining their workflow and exploring ways to enhance cross-functional collaboration and integrate feedback loops, ultimately reflecting their team values and focusing on building great products.

Mergify learned through experience that the process should serve the team rather than dictate its operations, leading them to transition from rigid Agile practices to a more flexible, culture-driven workflow. Initially, the company used a lightweight Kanban system, avoiding the bureaucracy of traditional Agile frameworks like Scrum, which they found diminished motivation and productivity. As they grew, challenges such as ownership and backlog management arose, prompting further refinement of their process to better align with their values of autonomy and collaboration. By prioritizing simplicity and trust, Mergify crafted a workflow that supports their remote team's creativity and independence, emphasizing the importance of tailoring processes to fit the unique culture and needs of a team rather than conforming to industry standards.