> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/guides/understand-how-engineering-time-is-spent.md). # Understand how engineering time is spent Engineering teams balance roadmap work, maintenance, support, incidents, technical debt, and internal improvements every day. Without visibility into where time actually goes, it becomes harder to set realistic goals and keep the team focused, and reactive work can consume more time than expected. Swarmia helps engineering organizations understand how engineering time is spent so teams can make better prioritization decisions and align engineering effort with strategic goals. ### Start with the focus summary A great place to start understanding how your team spends their engineering time is the [focus summary](/features/focus/focus-summary.md).
It gives you an overview of how engineering effort is distributed across teams, projects, and investment categories over time — measured in developer effort (FTE months). Compared to relying only on an issue tracker, the focus summary reveals where attention goes when many things are in progress at the same time. This helps answer questions like: * Are the projects you expect to be in focus actually getting worked on? * How much time goes to roadmap work versus maintenance? * Are support requests and incidents consuming increasing capacity? * Which initiatives require the most engineering investment? If you’re new to FTE-based reporting, see [Developer effort (FTEs)](/definitions/developer-effort-ftes.md). ### Understand your engineering investments Once work is visible, you can evaluate whether engineering effort aligns with your organization’s priorities. [Investment balance](/features/focus/balance-engineering-investments.md) helps you categorize work according to your strategy and focus, and monitor it over time. Many teams discover that reactive work — bugs, support, interruptions, and maintenance — gradually consumes more time than expected, making it harder to sustain strategic initiatives. Swarmia helps you: * Track the balance between roadmap work and KTLO (“keep the lights on”) work * Understand how investment patterns change over time * Compare focus areas across teams ### Understand your strategic initiatives Some projects are more important than others. [Initiatives](/features/focus/deliver-strategic-initiatives.md) bring together those strategic, cross-team projects most important to your organization. These projects are often difficult to capture fully in your issue tracker because they span teams and boards. Swarmia helps you: * See all the work currently underway in an initiative * Ensure that strategic projects don't lose steam and that target dates are met * Forecast when work is done ### Understand the day-to-day Engineering work doesn’t always happen inside planned roadmap tickets. Interruptions, reviews, production issues, and context switching often stay invisible in traditional project tracking. [Work log](/features/focus/analyzing-the-activity-patterns-on-work-log.md) helps teams understand how work actually happens day to day by combining pull requests, issue activity, and collaboration patterns into a single timeline. This makes it easier to spot patterns like: * Excessive multitasking * Frequent interruptions * Teams spreading effort across too many projects * Long-running projects losing momentum ### Understand focus during sprints For teams using sprint-based planning, the [sprints](/features/focus/sprints.md) view helps visualize sprint-to-sprint performance. You can understand: * How much of the commitment gets completed * How much work gets added after a sprint starts * Whether teams can protect focus during execution ### Turn visibility into better decisions When you know where engineering time goes, it’s easier to plan and prioritize. Teams can protect time for important work, cut down on interruptions, keep maintenance and new work in balance, and ensure engineering effort supports business goals. This helps teams make better tradeoffs and stay on mission. That is what Swarmia's focus features are all about. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.swarmia.com/guides/understand-how-engineering-time-is-spent.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.