Urgent.News

What's breaking now, across thousands of outlets.

Tech

Kanban After 12 Months Of Interrupt-Driven Work

One year after replacing sprints, our platform team kept the limits and lost the theatre. On 19 August 2025, we deleted the remaining two-week sprint from our platform board while seven tickets were still marked “in progress.” Two were waiting on product teams, one was a certificate renewal nobody had planned, and one was a fairly ordinary Terraform change that had somehow acquired four…

After a year of adopting the Kanban method, the platform team found that limiting work in progress and introducing an expedite lane helped expose hidden work. The team moved away from sprint-based planning, which often became disrupted by incidents and deadlines. The Kanban board demonstrated that the team was dealing with unplanned tasks alongside planned work, revealing a ratio that looked bad but was expected.

They set a limit of eight active standard tickets, with one expedite slot. The team also began categorizing work as "fixed date" or "regular," distinguishing between work dictated by external factors and internal priorities. Initially, the board had three columns: Ready, Doing, and Done. However, a second column called 'Blocked' was added soon after, as it became clear that work in the Doing column was often incomplete.

The team started asking different questions, such as what could be completed before taking on new tasks. This shift led to a reduction in daily stand-up time and a focus on finishing work before taking on new tasks. Throughput averaged 14 completed standard tickets every two weeks, although this number varied. The team learned that having more work in progress generally led to longer completion times, assuming the system was stable.

Engineering managers were instructed not to insert work directly into the Doing column but could request expedite items. Blocked tickets now required a reason, the party waiting, and a follow-up date. The team found that blocked work became more visible and created a sense of accountability.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Understanding OAuth2 the Simple Way

Understanding OAuth2 the Simple Way You are building a side project and want users to log in with their Google accounts instead of making up yet another password they'll forget.

  • OAuth2 enables Google login without new passwords
  • Simplified as handing a digital valet key for specific actions
  • Authorization Code Flow involves four steps for web apps

Week-6, 7, 8

Catching Up: Architecture, Security, and Concurrency in the Heka Auth Service Hey everyone! First of all, I want to start with a huge apology for the radio silence over the last couple of weeks.

Day 30: Hard Reset Forgets on Purpose, and NAT Needs a Guardrail Switched Off

Thirty days in, and today both tasks required deliberately switching off something that exists to protect you. Git refuses to let you overwrite shared history.

  • Git prevented overwriting shared history during hard reset
  • EC2 denied forwarding packets not destined for it
  • NAT instance created to allow private EC2 access to S3

note taking app with auto sync leetcode and local llm model integration

I built this app over the weekend as a side project. 🛠️ The problem was simple: after I submit on LeetCode, going back and forth to write notes and save them is painfully manual.

  • Daily Routine app integrates LeetCode submissions with local LLM model
  • App stores notes, keys, and database on user's machine for data security
  • Features include automatic sync, reports, heatmaps, and calendar views

More from Saturday 22 August →