# cycle time Published articles for cycle time. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Automated Code Review: The 6-Month Evolution DevFeed: [Automated Code Review: The 6-Month Evolution]() Original publisher: [Read original article]() Author: eadams@hubspot.com (Emily Adams) Published: 2026-03-02T17:46:43Z Content type: article Language: en Sources: [HubSpot]() Topics: [Code review](), [AI-assisted coding](), [Claude Code](), [GitHub](), [Kubernetes](), [Java]() Tags: [agents](), [ai](), [automated](), [claude-code](), [cli](), [code](), [code-review](), [coding](), [coding-agents](), [cycle-time](), [developer-experience](), [engineering](), [engineering-infrastructure](), [github](), [human-review](), [java](), [kubernetes](), [pull-request](), [pull-requests](), [quality](), [workflow]() ### AI overview HubSpot describes a six-month evolution of its automated code review system. The system uses AI to review pull requests, provide feedback grounded in HubSpot-specific norms, and reduce the time engineers wait for feedback. The article says Sidekick reduced feedback time by 90%, with a peak reduction of 99.76% in September, and traces a shift from a Kubernetes-based system powered by Claude Code toward a framework native to HubSpot's Java stack. ### Source excerpt As HubSpot engineers have increasingly started writing more and more of their code with both local and cloud coding agents, we've noticed that now more than ever, code review is taking up a large portion of cycle time on new changes. ## Why focused coding time may be limited to a few hours per day DevFeed: [Why focused coding time may be limited to a few hours per day]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-01-29T16:02:51Z Content type: opinion Language: en Sources: [Tech World With Milan Newsletter]() Topics: [coding](), [meetings](), [Computer science]() Tags: [burnout](), [coding](), [context](), [cycle-time](), [developer](), [meetings](), [strategies](), [techniques]() ### AI overview This commentary argues that developers may have only three to four hours of high-focus coding capacity per day. It discusses cognitive limits, interruptions, meetings, flow, and deep-work strategies, while recommending practices such as time-blocking, batching communication, async defaults, and no-meeting days. ### Source excerpt Most of us have felt it: after a few solid hours of coding, your brain starts shutting down. ## Using Kanban Metrics and Reports to Identify Team Improvement Opportunities DevFeed: [Using Kanban Metrics and Reports to Identify Team Improvement Opportunities]() Original publisher: [Read original article]() Author: dennikolaev (hh.ru) Published: 2025-02-21T14:00:30Z Content type: article Language: ru Sources: [HeadHunter RU]() Topics: [Kanban](), [jira]() Tags: [cycle-time](), [datadriven](), [delivery](), [discovery](), [jira](), [kanban](), [lead-time](), [tag-22e9d0410dcb](), [tag-694195a2e09b](), [tag-8720e37629f7](), [tag-add1155413d1](), [tag-b92bf5906bbd](), [tag-e7d8489b7f64]() ### AI overview A project manager at hh.ru explains how to use Kanban-oriented metrics and reports to analyze team efficiency and identify improvement opportunities. The article covers lead time, cycle time, percentiles, classes of service, and reports from an internally customized Jira-based system. ### Source excerpt "Как и на какие метрики смотреть в поисках зоны роста команды?" -- на эту тему менеджеры проектов в нашей компании задумываются регулярно, так как менеджеры отвечают в том числе и за эффективность процессов. Правильный ответ на вопрос будет зависеть от контекста команды, заказчиков, продукта, рабочего процесса и много чего еще. Но можно выделить ряд метрик и отчетов, построенных на этих метриках, которые будут универсальны, и которые можно брать за основу для анализа. А поскольку hh.ru -- компания, которая несколько последних лет применяет Kanban-метод, то и метрики ниже будут сильно пересекаться с тем, что этот метод предлагает. Меня зовут Денис Николаев, и я менеджер проектов в hh. В этой статье покажу, на какие основные отчеты смотрю я. Также добавлю примеры того, на что обращать внимание в этих отчетах, чтобы в дальнейшем работать над повышением эффективности. Читать далее ## Value-Stream-Oriented Kanban DevFeed: [Value-Stream-Oriented Kanban]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-04-20T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Kanban](), [Agile](), [Software as a service]() Tags: [agile](), [burnout](), [business-developer-productivity-engineering-leadership-kanban-product-management-engineering-ex](), [business-value](), [cpu](), [cycle-time](), [flow](), [kanban](), [metrics](), [parallel](), [saas]() ### AI overview The article argues that Kanban should be oriented around customer-focused value streams rather than individual subtasks. It contends that measuring task-level flow can create an illusion of productivity while multiple initiatives delay meaningful delivery, and recommends prioritizing fast business value over maximizing utilization. ### Source excerpt Value-Stream-Oriented Kanban Many teams, especially in the startup environment, move away from Scrum and use a leaner Kanban-based approach. This is a good thing. I don't think Scrum is a suitable framework for modern, fast, agile companies. - Especially not in the SaaS field (the reasoning behind this statement will become another article, eventually). ## trivago Tech Camp 2017 DevFeed: [trivago Tech Camp 2017]() Original publisher: [Read original article]() Author: Tom Bartel Published: 2017-09-14T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Development](), [Software Engineering](), [web applications](), [PHP](), [MySQL](), [API](), [Symfony](), [JavaScript](), [Python](), [Open Source]() Tags: [2017](), [api](), [automation](), [cycle-time](), [development](), [education](), [engineering](), [engineering-culture](), [javascript](), [mysql](), [open-source](), [php](), [python](), [software-engineering](), [symfony]() ### AI overview trivago Tech Camp 2017 brought ten students from eight countries to the company's Düsseldorf headquarters for two weeks of real-world software engineering work. The projects improved internal workflows, automated manual tasks, and included an open-source software project. ### Source excerpt At the end of August 2017, ten students set foot in the trivago headquarters in Düsseldorf to be part of the first ever trivago Tech Camp. Two weeks were packed with real-world challenges, guest lectures, Q&A sessions, and tons of other opportunities to learn. In the end, a lot of working software was delivered. ## Building Stronger Agile Teams Through Team Setup, Alignment, and Outcome Measurement DevFeed: [Building Stronger Agile Teams Through Team Setup, Alignment, and Outcome Measurement]() Original publisher: [Read original article]() Author: Johannes Theilmann (johannes.theilmann@upday.com) Published: 2017-03-03T04:00:00Z Content type: article Language: en Sources: [Upday]() Topics: [Agile](), [Self-organizing Team](), [meetings](), [Canvas](), [jira](), [Slack]() Tags: [agile](), [business](), [cycle-time](), [deploy](), [devops](), [meetings](), [metrics](), [product-owner]() ### AI overview An upday Product Owner describes a checklist for setting up stronger Agile teams, including defining goals, agreeing on team structure, aligning on tools and roles, prioritizing projects with CD3 and WSJF, and measuring outcomes through cycle time, deployment frequency, feature lead time, team happiness, and meeting volume. ### Source excerpt At upday we challenge ourselves to achieve technical excellence and a strong understanding of business needs. Due to external and internal circumstances we have quite a volatile team setup. At least each quarter we change either the team members, the PO or the whole structure of our teams - from horizontal to cross-functional to fluent and back again. However our goal is to have stable teams with a clear business orientation while also enabling team members to grow technically and to support each other (eg. reviews, testing, tech discussions). It is the challenge for each team member to adapt quickly to new teams, different skill sets and goals. I would like to share how we approach building stronger teams and to have a checklist for myself when a new team is set up: As a Product Owner I want to set up teams quickly and efficiently in order to get them up 'n' running fast and deliver the highest business value. Acceptance Criteria: Project goals are set for the next quarter Team set up is agreed with agile coach / scrum master / team-cut captain Team alignment canvas session defines: communication tools (Slack, Skype, email etc.) planning and progress meetings (Jira, Trello) roles, component owner, facilitator, lead team agreement Depict the process the team is improving on a story map map projects Calculate the CD3 (cost of delay divided by duration) and WSJF (weighted short jobs first) with the team. PO-team choose projects based on CD3 and/or WSJF Feedback from stakeholders is collected on a confluence page Epics for projects define clearly user/business value and metrics, objectives and key results (OKRs) to measure the success of an epic. External team members are invited to groomings to make upcoming changes transparent early on and to final reviews to identify potential follow up stories We already made several experiments with the team setup without really being able to measure the outcomes. We also realised that not all our needs are covered by the existing