# Kanban Published articles for Kanban. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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. ## 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). ## The Block Protocol for reusable web editor blocks DevFeed: [The Block Protocol for reusable web editor blocks]() Original publisher: [Read original article]() Author: Joel Spolsky Published: 2022-01-27T17:14:00Z Content type: opinion Language: en Sources: [Joel Spolsky]() Topics: [Protocol (disambiguation)](), [Web](), [Open Source](), [Content Management System]() Tags: [content-management-system](), [kanban](), [news](), [open-source](), [web](), [wordpress]() ### AI overview The article proposes the Block Protocol, an open and free standard intended to make blocks reusable across blogs, note-taking apps, and content management systems. It describes an early draft, initial blocks, and a simple editor under development. ### Source excerpt You've probably seen web editors based on the idea of blocks. I'm typing this in WordPress, which has a little + button that brings up a long... Read more "Making the web better. With blocks!" ## How to structure learning for maximum return DevFeed: [How to structure learning for maximum return]() Original publisher: [Read original article]() Published: 2019-04-10T00:00:00Z Content type: opinion Language: en Sources: [Vasya Drobushkov]() Topics: [Learning](), [Development](), [Kanban](), [gist]() Tags: [development](), [kanban](), [learning](), [self-improvement](), [upskill]() ### AI overview The author reflects on several approaches to self-improvement and technical learning, including reading fiction, studying processes, and filling technical gaps. They propose a more structured learning method based on a high-level plan and a tracking tool, comparing Scrum, Kanban, and GIST before selecting GIST. ### Source excerpt Photo by Tim Gouw on Unsplash In IT, it's very difficult to keep up-to-date. A full-time job doesn't give you a chance to upskill or try new things because you're too busy dealing with legacy code, developing features, etc. Yet, self-development is an important thing and I've tried my best over years to make it a habit. For the few past years, I've conducted a few experiments towards self-improvement, and I'd like to share a few of those here. ## Post-agile process agnosticism DevFeed: [Post-agile process agnosticism]() Original publisher: [Read original article]() Published: 2018-10-25T09:27:38Z Content type: opinion Language: en Sources: [Blog by Michael Dubakov]() Topics: [Agile](), [Development](), [meetings]() Tags: [agile](), [collaboration](), [development](), [kanban](), [management](), [meetings](), [processes](), [scrum]() ### AI overview The article criticizes the commercialization and superficial adoption of Agile, arguing that many organizations practice "Fake Agile" by adding rituals such as stand-ups and sprints without embracing Agile principles. It advocates process agnosticism: programmers should not focus on a process's name unless they have the authority to change it, while those seeking control must engage critically with process decisions. ### Source excerpt with Rick and Morty! ## An Opinion on Agile Practices, Meetings, Iterations, and Testing DevFeed: [An Opinion on Agile Practices, Meetings, Iterations, and Testing]() Original publisher: [Read original article]() Published: 2013-04-01T15:41:57Z Content type: opinion Language: en Sources: [Blog by Michael Dubakov]() Topics: [Agile](), [meetings](), [Testing](), [Self-organizing Team]() Tags: [agile](), [email](), [kanban](), [meetings](), [productivity](), [qa](), [scrum](), [unit-tests]() ### AI overview An opinion article reviews a company's experience with agile development, including daily meetings, short iterations, testing, and Kanban. The author argues that several practices reduced productivity or failed to work in that company's context. ### Source excerpt I don't believe in agile development anymore. Our company applied agile practices from day one. We've started agile usage in 2006. We tried almost everything: Extreme Programming, Scrum, Kanban and many many small practices. Did it stick? Hell no. Let's review the lessons. Daily Meetings They are just worthless. We used to gather together at 11 am in a single room and report what was completed, what is not, whether there are some blockers. Well, when there are about 30 people in a room these meetings are not fun. They took up to 10 minutes usually, but sometimes they took as long as 15 minutes (I think this duration just can't be tolerated). After the meeting, people go and grab coffee, chat about problems, chat about ideas... These useless activities distract people and they spend less time on coding. We've replaced daily meetings with a weekly status reports sending via email. The format is very simple with just 7 questions like "Please, enumerate all tasks you've completed last week" and "How you estimate your personal productivity on a scale from 1 (low) to 10 (exceptional)". We collect all emails, process them and have a real stats per person, per week, per project, etc. Really cool! Iterations We tried 1 week and 2 weeks iterations. Neither worked out. With short iterations there was a constant pressure to get shit done and technical debt accumulated like a huge garbage heap. It is impossible to squeeze a good solution into a short timeframe. There're so many meetings like iteration planning, planning poker sessions, iteration demo, iteration retrospective... These meetings are killing productivity, you know. QA were struggling with short iterations as well. It is impossible to test a user story thoroughly in few days. We tried mini-waterfall in a single iteration -- didn't work, testing phase started just 2 days till the end of the iteration with miserable outcome. We tried to write many unit tests and acceptance tests -- didn't help, since requirements were changi ## Why Agile Assessments Can Distract Teams from Productivity DevFeed: [Why Agile Assessments Can Distract Teams from Productivity]() Original publisher: [Read original article]() Published: 2008-10-21T15:41:57Z Content type: opinion Language: en Sources: [Blog by Michael Dubakov]() Topics: [Agile](), [Development](), [Self-organizing Team]() Tags: [agile](), [development-process](), [kanban](), [productivity](), [scrum]() ### AI overview This opinion article argues that generic Agile tests, certifications, and assessments can distract software teams from their actual goals. It recommends focusing on team productivity, software quality, and customer satisfaction, while allowing teams to choose practices that fit their circumstances, including iteration-less or Kanban-based development. ### Source excerpt "Are we agile?", "How agile are we?", "Are we more agile than they are?" Honestly, I am getting tired of these questions. Why do you care? Will it make you happier when you are able to tattoo "100% agile" on your body? Is it a goal to be "agile"? Definitely not! All agile tests are just a garbage. All efforts on agile process certifications/assessments are useless. There are so many factors influencing software development process that make impossible any certification. Your company is special, you have special people in the development team, you have special conditions, rules, and other external factors. CMMI, PMBOK, and other heavy approaches do not help to build legendary team. They only may help to build an average team and eliminate some quite obvious mistakes in the development process. The right question to ask is: "How can we be more productive as a team?". It is your project. It is your team. You have goals to improve team productivity ("Done-Done" stories in a period of time), create outstanding software and make customers happy. Agile Tests that answer question "Are we agile?" shift the focus to the wrong direction. Look, if your team has to pass an Agile "test", they will focus on passing it. That is a plain dumb goal and a waste of time. Let's say a manager reads about a famous agile test and sets the goal to pass it. Development team, as a complex adaptive system, adapts to the rules and environment. It will change development process and apply practices to pass the test as effectively as possible. However the team's productivity may suffer. Why? Simply because the test is too general and can't be applied to any team. Remember, your team is special. Let's take Scrum and famous Nokia test. The first question is "Describe your iterations" and the worst answer to the question is "We do not use iterations". Well, it is a Scrum test and Scrum insists on having iterations (sprints). But what if your team works more effectively without iterations? What if you