# team Published articles for team. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Government Digital Service move 'grinds gears' in UK's e-government DevFeed: [Government Digital Service move 'grinds gears' in UK's e-government]() Original publisher: [Read original article]() Author: Lindsay Clark Published: 2026-09-17T09:15:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [digital](), [Development]() Tags: [digital](), [government](), [public-sector](), [strategy](), [talent](), [team](), [tech](), [uk]() ### AI overview Experts fear a loss of talent after the team responsible for technology strategy was moved to a third department in three years, creating friction in the UK's e-government efforts. ### Source excerpt As team responsible for tech strategy shunted to third department in three years, experts fear exodus of talent ## AWS reimagines the getting started experience DevFeed: [AWS reimagines the getting started experience]() Original publisher: [Read original article]() Author: Micah Walter Published: 2026-09-16T17:50:14Z Content type: release Language: en Sources: [AWS News Blog]() Topics: [Amazon Web Services](), [AWS IAM](), [configuration](), [App]() Tags: [announcements](), [aws](), [aws-management-console](), [configuration](), [developers](), [free](), [getting-started](), [launch](), [news](), [permissions](), [project](), [team]() ### AI overview AWS announces a simplified getting-started experience with sensible defaults, managed project environments, simplified permissions, and $100 in Free Tier credits for most new customers. Customers can later activate advanced AWS features without migrating. ### Source excerpt AWS has reimagined the getting started experience with smart and sensible defaults to help developers get started fast so that they can focus on building. New customers can sign up and get started right away with $100 in Free Tier credits, managed project environments, and simplified team and resource permissions. If their workload evolves, customers can activate advanced features to access the full breadth and depth of AWS in one step, with no migration required. ## Khan Academy's Engineering Principles DevFeed: [Khan Academy's Engineering Principles]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-06-06T22:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [context](), [Concurrent Programming]() Tags: [communication](), [company](), [context](), [eng-leads](), [engineering](), [news](), [team]() ### AI overview Ben Kamens explains how growing companies can reduce the impact of communication failures by documenting shared engineering principles. Khan Academy's principles give team members context for making decisions amid ambiguity and changing priorities. ### Source excerpt ⭐ Read about our 2019 revision of the principles! ⭐ By Ben Kamens You know those super-frustrating movie ... Read more ## Time Management at Khan Academy DevFeed: [Time Management at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-07-25T22:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [To-Do](), [Job]() Tags: [email](), [engineering](), [learn](), [management](), [meetings](), [news](), [team](), [time-management](), [web-frontend](), [work]() ### AI overview Khan Academy employees share approaches to managing their time, including weekly Trello to-do lists, scheduling uninterrupted work around meetings, and organizing tasks around energy and responsiveness needs. ### Source excerpt By Multiple Everyone at Khan Academy received a plea recently: I'm hoping to organize a blog post that ... Read more ## Switching to Slack DevFeed: [Switching to Slack]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-11-09T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Slack](), [migration](), [notifications](), [systems](), [Documentation]() Tags: [administration](), [chat](), [connectivity](), [delivery](), [documentation](), [engineering](), [infrastructure](), [integration](), [migrate](), [news](), [notifications](), [organization](), [remote](), [slack](), [switching](), [team]() ### AI overview Khan Academy describes its decision to migrate team chat from HipChat to Slack after connectivity, message delivery, and notification problems affected reliability, especially for remote workers. The article outlines cultural, administrative, organizational, and integration-related costs that make chat-platform migration difficult. ### Source excerpt By Benjamin Pollack Khan Academy recently made the decision to migrate our team chat from HipChat to Slack. ... Read more ## Presentation: Lead Without a Ladder: How I Climbed Into Engineering Leadership DevFeed: [Presentation: Lead Without a Ladder: How I Climbed Into Engineering Leadership]() Original publisher: [Read original article]() Author: Pauline Jepp Published: 2026-09-15T09:10:00Z Content type: opinion Language: en Sources: [InfoQ]() Topics: [engineering-leadership](), [systems]() Tags: [alignment](), [careers](), [chief-engineer](), [culture-methods](), [engineering](), [engineering-leadership](), [infoq](), [leadership](), [mentorship](), [presentation](), [qcon-san-francisco-2025](), [qcon-software-development-conference](), [safety](), [team](), [transcripts](), [trust]() ### AI overview Pauline Jepp discusses how systems thinking, rock climbing, and flocking behaviors inform engineering leadership. She covers balancing team autonomy with alignment, supporting mentorship and other invisible work, and transitioning from hands-on engineering to leadership while maintaining organizational trust and psychological safety. ### Source excerpt Pauline Jepp explains how systems thinking, rock climbing, and flocking behaviors apply to engineering leadership. She shares strategies for balancing team autonomy with alignment, supporting invisible work like mentorship, and navigating transitions from hands-on engineer to engineering leader while maintaining organizational trust and psychological safety. By Pauline Jepp ## Inside the AI Stack of an $8.3B AI Company's Product Team | Together AI DevFeed: [Inside the AI Stack of an $8.3B AI Company's Product Team | Together AI]() Original publisher: [Read original article]() Author: Aakash Gupta Published: 2026-09-14T23:05:28Z Content type: article Language: en Sources: [Product Growth]() Topics: [Artificial Intelligence](), [context](), [repo](), [context window](), [Developer experience](), [GitHub](), [Linear]() Tags: [ai](), [context](), [context-window](), [developer-experience](), [github](), [linear](), [product](), [repo](), [team](), [tools]() ### AI overview The article examines Together AI's AI-oriented product team and describes four parts of its working stack: a shared context repository, reusable skills for research and product documentation, an orchestrator for product leaders, and agent evaluations. It explains how shared context files and workflows support collaboration across product areas, including automated weekly status updates using Linear, GitHub, and strategy documents. ### Source excerpt I got a truly AI-pilled product team to demo the 4 key tools in their stack ## Every service needs an owner DevFeed: [Every service needs an owner]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-09-12T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [systems](), [incident]() Tags: [catalog](), [customer](), [incident](), [on-call](), [ownership](), [platform-engineering](), [production](), [reliability](), [service](), [service-catalog](), [sre](), [startups](), [team]() ### AI overview The article argues that growing organizations need a focused service catalog to make production ownership visible. It recommends recording each service's customer outcome, owning team, current on-call contact, deployment path, health dashboard, runbook, and dependencies, and maintaining those records as part of engineering work. ### Source excerpt A useful service catalog is not an inventory project. It is a public record of who owns a customer outcome when the system is healthy and when it fails. ## 'Ship a good game, learn from it, and build from there:' Lessons from going indie after a decade at id Software DevFeed: ['Ship a good game, learn from it, and build from there:' Lessons from going indie after a decade at id Software]() Original publisher: [Read original article]() Author: Chris Kerr Published: 2026-09-10T18:56:42Z Content type: news Language: en Sources: [gamedeveloper]() Topics: [Game Development](), [Development](), [cloud-infrastructure]() Tags: [business](), [careers](), [company](), [development](), [doom](), [game-development](), [games](), [industry](), [marketing](), [money](), [production](), [publisher](), [team]() ### AI overview Game Developer interviews Tony Garza and Richard O'Neal about leaving id Software, founding the indie studio Turnkey Games, and developing the horror adventure Apart. They describe bootstrapping the company, growing the team gradually, controlling overhead, and directing spending toward development and essential business costs. ### Source excerpt We sit down with Doom Eternal art director Tony Garza and fellow id alum Richard O'Neal to hear about their journey into the world of indie development through Turnkey Games. ## How engineering teams can measure AI coding ROI with cost attribution and outcome metrics DevFeed: [How engineering teams can measure AI coding ROI with cost attribution and outcome metrics]() Original publisher: [Read original article]() Author: Kelsey Rosen Published: 2026-09-08T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [ai-coding](), [Ground truth / benchmark quality](), [coding](), [Finance]() Tags: [ai](), [ai-coding](), [analysis](), [blog](), [coding](), [cost](), [datadog](), [engineering](), [governance](), [harness](), [incident](), [lifecycle](), [measurement](), [metrics](), [numbers](), [production](), [team](), [tokens](), [tooling](), [workflow]() ### AI overview A Harness panel discussion outlines ways engineering organizations can measure AI coding ROI. The panel recommends attributing costs to specific work, combining throughput metrics with qualitative evidence, and using governance and process changes to interpret results. ### Source excerpt Harness panelists share practical strategies for measuring AI coding ROI, from granular cost attribution and lifecycle metrics to budgeting, governance. | Blog ## What 143 platform teams told us about keeping infrastructure alive DevFeed: [What 143 platform teams told us about keeping infrastructure alive]() Original publisher: [Read original article]() Author: Oliver Thylmann Published: 2026-09-04T10:15:45Z Content type: opinion Language: en Sources: [Giant Swarm Blog]() Topics: [Platform Engineering](), [Kubernetes](), [cloud-infrastructure](), [Security](), [observability]() Tags: [aws](), [azure](), [bare-metal](), [infrastructure](), [kubernetes](), [observability](), [open-source](), [platform](), [platform-engineering](), [security](), [survey](), [team](), [tech]() ### AI overview Giant Swarm surveyed 143 platform and infrastructure professionals about the ongoing work required to keep production platforms running. The article argues that this platform integration tax is primarily a time cost, with security, reliability, cluster management, and observability consuming engineering capacity. ### Source excerpt The hidden cost of platform engineering isn't building your stack. It's keeping it alive. Giant Swarm surveyed 143 platform teams to find out. ## Focus and followthrough are the moat DevFeed: [Focus and followthrough are the moat]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-08-27T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Development](), [SRE]() Tags: [development](), [focus](), [production](), [projects](), [sre](), [team]() ### AI overview An opinion piece about how a small startup team uses focus, sprint planning, prioritization, and regular stakeholder communication to finish work despite having more requests than capacity. ### Source excerpt Because starting is easy and finishing is hard. ## WorkOS Applied AI Showcase July 28 2026 - Moving to an AI-native Organization DevFeed: [WorkOS Applied AI Showcase July 28 2026 - Moving to an AI-native Organization]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-14T13:36:57Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Artificial Intelligence](), [Low-Code / Internal Tools](), [AI-assisted coding](), [Containers](), [MCP](), [Command-line interface](), [incident](), [Security](), [datadog](), [Pull Request](), [Slack](), [GitHub]() Tags: [agent](), [agents](), [ai](), [applied-ai](), [cli](), [coding](), [coding-agents](), [containers](), [datadog](), [demo](), [event](), [github](), [incident](), [internal-tools](), [mcp](), [organization](), [pull-request](), [slack](), [talks](), [team]() ### AI overview WorkOS's Applied AI Showcase in New York presented five internal tools--Horizon, Blog Bot, the CLI, Wallaby, and Atlas--through live demos and talks. The article explains how the Applied AI team helps non-engineering functions build AI-powered workflows and systems. ### Source excerpt WorkOS is becoming an AI-native organization. The Applied AI Showcase in NYC on July 28th 2026 showed exactly how with live demos and talks from the Applied AI team. ## Introducing Delta DevFeed: [Introducing Delta]() Original publisher: [Read original article]() Author: Nathan Sobo Published: 2026-08-12T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [coding](), [App](), [real-time](), [Git](), [Software](), [Code]() Tags: [agent](), [agents](), [build](), [coding](), [developers](), [git](), [multiplayer](), [real-time](), [review](), [software](), [team]() ### AI overview Zed introduces Delta, a private-beta multiplayer environment for coding with agents and reviewing their work. Delta connects code, conversations, worktrees, and real-time collaboration through DeltaDB while remaining compatible with existing Git repositories. ### Source excerpt A multiplayer environment for coding with agents, from the creators of Zed. ## How Wix Built a Code Migration Platform to Automate Cross-Team Repository Changes DevFeed: [How Wix Built a Code Migration Platform to Automate Cross-Team Repository Changes]() Original publisher: [Read original article]() Author: Wix Engineering Published: 2026-07-22T14:10:18Z Content type: article Language: en Sources: [Wix Engineering]() Topics: [migration](), [Code]() Tags: [automatic](), [code](), [developer](), [engineering](), [infrastructure](), [migration](), [organizational](), [platform](), [process](), [projects](), [scale](), [team]() ### AI overview Wix describes building a Code Migration Platform to reduce the coordination burden of large-scale code migrations. The platform is intended to identify affected repositories, apply changes automatically, and track migration work centrally. The article says Wix initiates 50 migrations annually, affects hundreds of repositories per migration, touches 6,000 repositories each year, and spends 25% of organizational developer time on migrations. ### Source excerpt No one wakes up excited to do a code migration. Deprecated libraries, method version upgrades, infra changes - they happen constantly, they affect dozens of teams, and they always arrive at the worst possible moment. A small technical change somehow becomes months of coordination. Slack threads. Priority negotiation. Manual tracking. Reminders. Many google sheets. For years, I managed cross-team projects at Wix, and migrations were always the hardest part. Not because they're technically... ## Documentation team funding DevFeed: [Documentation team funding]() Original publisher: [Read original article]() Author: NixOS Published: 2026-07-10T12:00:00Z Content type: news Language: en Sources: [NixOS Announcements]() Topics: [Documentation](), [Nix](), [Deployment](), [navigation]() Tags: [2025](), [announcement](), [community](), [continuous-deployment](), [deployment](), [documentation](), [funding](), [improvements](), [navigation](), [nix](), [onboarding](), [team]() ### AI overview The NixOS Foundation is renewing its effort to improve Nix documentation and is seeking donations for a documentation team. Proposed funding would support a paid maintainer, framework evaluation, page splitting, continuous deployment, faster feedback, navigation, and redirects. ### Source excerpt tl;dr: There is a renewed effort to improve documentation, head to https://opencollective.com/nixos/projects/nix-documentation or contact foundation@nixos.org to chip in with funding! With the 2023 crowd-funding in documentation funding, we've seen some improvements, but a lot more is needed to make significant progress towards improving the overall experience with Nix documentation, including onboarding and discovery. Especially newcomers frequently struggle with our documentation, get frustrated and notice gaps, and have a hard time adopting Nix. In addition, in the Nix community survey 2025 we see that most people want excess funding to be allocated to improving documentation. While the NixOS Foundation doesn't have that much excess funding, @hsjobeki has stepped up to pick up leadership of the documentation team with support by @friedow. While they're volunteering their own time to lead the team, they'd like to have access to funding for not just ensuring that stuff gets done, but also maintained over time. They've collaborated to agree on a documentation vision (initial announcement) to work towards. For that reason, we're asking individuals and companies to donate to the renewed documentation team OpenCollective, so that we can reach the funding goals (more details on OpenCollective): (1.000 EUR /month) Paid documentation maintainer (4.000 EUR ) Framework evaluation (15.000 EUR ) Page splitting in nixos-render-docs (8.000 EUR ) Continuous deployment & Reduce feedback times (8.000 EUR ) Navigation & redirects If a company is interested in providing a significant amount of funding and would like a contract and invoice, please reach out to foundation@nixos.org. Furthermore, if you'd like to support documentation in non-monetary ways, feel free to join the Matrix channel and/or bi-weekly meetings (see "Nix documentation meeting" in the NixOS Calendar), or see where you can help from updates in the discourse category. You can also read and discuss this announcement on Discourse. ## Your company can pay for Into AI (here's how) DevFeed: [Your company can pay for Into AI (here's how)]() Original publisher: [Read original article]() Author: Dr. Ashish Bamania Published: 2026-07-04T13:12:53Z Content type: article Language: en Sources: [Into AI]() Topics: [Artificial Intelligence](), [Development]() Tags: [subscription](), [team](), [technical]() ### AI overview This promotional article explains how readers can ask their employers to reimburse an Into AI subscription, including forwarding a payment receipt or using an email template. It also mentions a 30% discount for group team subscriptions. ### Source excerpt A ready-to-send email template to expense your subscription. ## SDET Lean Coffee #1: With AI, what is useful testing and what is workslop? SQGNE, June 2, 2026 DevFeed: [SDET Lean Coffee #1: With AI, what is useful testing and what is workslop? SQGNE, June 2, 2026]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-06-02T20:35:29Z Content type: opinion Language: en Sources: [T.J. Maher]() Topics: [Testing](), [Agile](), [sqgne](), [Development]() Tags: [agents](), [agile](), [agile-testing](), [ai](), [sqgne](), [team](), [teams](), [testing](), [work]() ### AI overview A report on the first SDET Lean Coffee organized by the Software Quality Group of New England. Attendees discussed useful testing practices with AI, AI-generated workslop, AI workflows, the testing of AI agents, and the pressures faced by software testers. The article also explains the Lean Coffee meeting format and announces the next session. ### Source excerpt With AI, what is useful when it comes to testing and what is workslop? How do you create workflows in AI? With AI producing massive amounts of code, how can a tester keep up? These are some of the topics attendees decided to talk about in our first ever SDET Lean Coffee, as part of the Software Quality Group of New England ( sqgne.org ). We exchanged war stories, horror stories, shared insights, and provided a bit of group therapy as we talked about the stress involved being the main support role of the software development team. A surprise guest was Lisa Crispin (LisaCrispin.com), author of "Agile Testing: A Practical Guide for Testers and Agile Teams". Lisa has been working with DORA, Google Cloud's DevOps Research and Assessment division. Recently, Lisa gave a talk teaming up with the "Beyond Quality" podcast, sharing what she has been doing "AI, testing, and the DORA AI Capabilities Model" at Lisa's site at https://lisacrispin.com/2026/04/20/ai-testing-and-the-dora-ai-capabilities-model/ discussing: The Dora AI Capabilitues Model How we need to test AI agents since AI agents can degrade over time What is a "Lean Coffee"?"Lean Coffee is a structured, but agenda-less meeting. Participants gather, build an agenda, and begin talking. Conversations are directed and productive because the agenda for the meeting was democratically generated". This format arose over fifteen years ago, when "Jim Benson and Jeremy Lightsmith wanted to start a group that would discuss Lean techniques in knowledge work - but didn't want to start a whole new cumbersome organization with steering committees, speakers, and such. They wanted a group that did not rely on anything other than people showing up and wanting to learn or create", according to LeanCoffee.org. When Is The Next SDET Lean Coffee? SDET Lean Coffees for the SQGNE will (usually) be held the first Tuesday of each month at 12:00 pm to 1:00 pm EDT. Interested in attending the next session Tuesday, July 7th? Register at the Soft ## Five rules for running an incident DevFeed: [Five rules for running an incident]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-05-27T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [incident](), [Learning]() Tags: [customer-experience](), [incident](), [incident-management](), [on-call](), [outage](), [postmortem](), [production](), [recovery](), [reliability](), [root-cause-analysis](), [rules](), [signal](), [speed](), [sre](), [team]() ### AI overview This opinion article presents five rules for handling production incidents: assess severity by customer impact, use an Incident Commander, mitigate before investigating root cause, maintain regular communication, and use postmortems for learning and accountable follow-up. ### Source excerpt The difference between a 10-minute incident and a 3-hour outage is rarely technical. Five things I wish every on-call team locked in before their first big page. ## AI Coding Tip 021 - Avoid Comprehension Debt DevFeed: [AI Coding Tip 021 - Avoid Comprehension Debt]() Original publisher: [Read original article]() Author: Maxi Contieri Published: 2026-05-23T15:24:29Z Content type: tutorial Language: en Sources: [Maximiliano Contieri - Software Design]() Topics: [ai-coding](), [coding](), [Learning]() Tags: [ai](), [ai-coding](), [audit](), [code](), [coding](), [debug](), [implement](), [onboarding](), [production](), [quality](), [team](), [technical](), [tests](), [velocity]() ### AI overview This tutorial explains how merging AI-generated code without understanding it creates comprehension debt: a growing gap between the codebase and what the team can genuinely explain and maintain. It recommends requiring explanations, documenting AI-made architectural decisions, testing understanding without the AI chat, and adding comprehension checks to pull requests. ### Source excerpt TL;DR: Merging code you don't understand creates comprehension debt that compounds until your team can no longer maintain it. Common Mistake ❌ You ask the AI to implement a feature. The code looks cl ## Managing Humans DevFeed: [Managing Humans]() Original publisher: [Read original article]() Author: Tom Published: 2026-05-14T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [Software Engineering](), [engineering-culture](), [Development]() Tags: [book](), [business](), [engineering-manager](), [humor](), [improvements](), [innovation](), [leadership](), [management](), [meetings](), [processes](), [software-engineering](), [team](), [technology]() ### AI overview A review of Michael Lopp's Managing Humans, focusing on leadership lessons about managing different team member profiles, channeling conflict productively, driving continuous change, and deciding who should attend meetings. ### Source excerpt Managing Humans Biting and Humorous Tales of a Software Engineering Manager Author: Michael Lopp If you manage people, this book is worth reading. Rather than offering complete solutions, it presents the author's gut feelings based on his experience with what works and what doesn't. It's written lightly, with plenty of humor and healthy doses of sarcasm that make it engaging without being cynical. ## Protocol Cluster Updates: May 2026 DevFeed: [Protocol Cluster Updates: May 2026]() Original publisher: [Read original article]() Author: Will Corcoran; Kev Wedderburn; Fredrik Published: 2026-05-11T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [client](), [Post-Quantum]() Tags: [ethereum](), [hardening](), [interop](), [leadership](), [norway](), [research-development](), [team](), [updates](), [upgrade]() ### AI overview This May 2026 update reports on an Ethereum core developer interop in Svalbard, where teams worked on hardening and preparing for the Glamsterdam upgrade. It highlights progress on the 200M gas limit floor, ePBS, EIP-8037, and Hegotá groundwork, and announces a transition in Ethereum Foundation Protocol cluster leadership. ### Source excerpt A semi-regular gathering of Ethereum core devs from various client teams, or interop, recently took place in Svalbard, Norway. Over the week-long event, teams focused on hardening and preparation for the next upgrade, Glamsterdam. Several important milestones came out of the week, including: 200M gas limit floor established:... ## Podman Standups! DevFeed: [Podman Standups!]() Original publisher: [Read original article]() Author: tsweeney Published: 2026-05-01T17:21:55Z Content type: article Language: en Sources: [blog.podman.io]() Topics: [podman](), [GitHub Issues]() Tags: [2026](), [cncf](), [community](), [events](), [github-issues](), [podman](), [red-hat](), [team](), [uncategorized](), [video]() ### AI overview The Podman project is moving its recurring standup meetings to the CNCF calendar so the wider community can join. Meetings will occur on Mondays and Thursdays, beginning May 4, 2026, with status roundtables followed by optional discussion topics. The existing Podman Community Cabal meeting will end after May 5, 2026. ### Source excerpt The standups are coming, the standups are coming! Come one, come all to the Podman Standup Meetings! For the past many years, the Podman team at Red Hat has held standup meetings on Mondays at 10:00 a.m. Eastern, and also on Thursdays at 11:00 a.m. Eastern. (Currently UTC-4, then UTC-5 once the USA goes to [...] ## Using a Bitbucket Dashboard Game to Improve Pull Request Reviews DevFeed: [Using a Bitbucket Dashboard Game to Improve Pull Request Reviews]() Original publisher: [Read original article]() Author: Tom Published: 2026-04-19T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [pull-requests](), [bitbucket](), [DevOps](), [App](), [Web]() Tags: [api](), [best-practices](), [bitbucket](), [blameless-culture](), [developer](), [devops](), [gamification](), [html](), [kanban](), [people](), [pr-reviews](), [productivity](), [pull-requests](), [review](), [software-engineering](), [team](), [team-culture](), [web]() ### AI overview A team struggled with delayed pull request reviews that blocked colleagues and caused work to drift between sprints. They built a Bitbucket-based dashboard that ranked developers by outstanding reviews and displayed it on a shared TV, using humor and social pressure to encourage the team to review pull requests before standup. ### Source excerpt A story of how a team used "The Wall of Shame" to turn a bottlenecked PR review process into an engaging game. [Next page]()