# 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. ## The Agent Board: Kanban for Machines; Durable Coordination for Agents That Outlive the Conversation DevFeed: [The Agent Board: Kanban for Machines; Durable Coordination for Agents That Outlive the Conversation]() Original publisher: [Read original article]() Author: Tyler Hunt, Donald Nguyen, Gurbinder Gill Published: 2026-11-04T05:00:00Z Content type: article Language: en Sources: [arXiv: Artificial Intelligence](), [arXiv: Distributed Computing]() Topics: [Multi Agent Systems](), [agent to agent communication](), [Persistence](), [Agent Harness](), [async]() Tags: [agent](), [agents](), [block](), [board](), [cs-ai](), [cs-dc](), [events](), [fields](), [handler](), [harness](), [kanban](), [kernels](), [language-models](), [large-language-models](), [mirrors](), [policy](), [post](), [roles](), [semantic](), [single-threaded](), [substrate](), [team]() ### AI overview The Agent Board is a durable shared task table for coordinating agents across turns, agents, and external systems. Agents can post or watch tasks and block without holding a process; the Board Keeper brings in external events, matches them to waiting tasks by interpreting their prose, and can allocate agents by role. Loadable policy kernels assign meaning to statuses and roles, but the board itself does not enforce those conventions. In three small simulated pilots, board wait cost stayed flat as wait length increased, while naive polling grew about 165-fold; a plain external watcher was cheaper. The Board Keeper produced no false wakes but missed 3.6% of real wakes. ### Source excerpt arXiv:2611.04100v1 Announce Type: cross Abstract: Harnesses for large language models have converged on a single-threaded shape: one agent, one history, one machine, one sitting. That shape fails work that spans many agents, outlives any one model call, or waits on systems that are not agents. We describe the Agent Board, the coordination substrate in the Corvic harness. The board is a durable, shared table of semi-semantic tasks: a few exact fields the system routes on, and a free-form body that only language models read. Agents post tasks, watch tasks, and block on them, ending their turn and holding no process until a matching post wakes them. A system agent, the Board Keeper, acts as the interrupt handler for the board: it carries events from non-agent parts of the harness onto the board, matches them to waiting tasks by reading their prose, and allocates new agents for tasks that name a kind of agent rather than an instance. Loadable coordination policy kernels give statuses and roles meaning for a given pattern of work, without the board enforcing them. The design mirrors the kanban board a human team puts on a wall. We argue it is what persistent agent products such as Meta Muse, OpenAI dots and SpaceXAI Grok Bot need once an agent must wait, hand off work, or work with agents from another vendor. We view the board as an operating-system scheduler for agents and state where the analogy breaks. We separate what the mechanism guarantees from what it leaves to convention, and report a trace from a live board and three small simulated pilots. In the pilots, the wait cost of the board was flat in wait length while naive polling grew about 165-fold, but a plain external watcher was cheaper than the board. The Board Keeper matched prose waiters with no false wakes but missed 3.6 percent of real wakes. ## Kanzo: A Lightweight Self-Hosted Kanban Board for Humans and AI Agents DevFeed: [Kanzo: A Lightweight Self-Hosted Kanban Board for Humans and AI Agents]() Original publisher: [Read original article]() Author: Jeremy Published: 2026-10-31T11:12:43Z Content type: article Language: en Sources: [Noted]() Topics: [Kanban](), [AI Chat](), [To-Do]() Tags: [agent-integration](), [agents](), [ai](), [ai-coding-assistants](), [claude-code](), [cloud-services](), [codex](), [data-storage](), [export](), [git](), [image](), [integration](), [kanban](), [lightweight](), [mcp](), [rust](), [self-hosted](), [self-hosted-task-management-to-do-lists](), [sqlite](), [synchronization](), [web-interface]() ### AI overview Kanzo is a self-hosted Kanban task manager that stores data locally in SQLite and runs as a small Rust executable, with no external database or cloud service required. Its built-in MCP server lets compatible assistants, including Claude Code and Codex, interact with the same board by taking assignments, moving tasks, and posting progress comments; people can follow activity in the browser interface. Kanzo also supports syncing boards between computers through a private Git repository. The excerpt lists search, image attachments, Markdown and JSON exports, and Linux, macOS, and Raspberry Pi support. It says the AGPL-3.0 application has no built-in authentication, so the web interface should stay on a trusted network or have additional access controls. ### Source excerpt Kanzo is a lightweight, self-hosted Kanban task manager built with Rust and SQLite. It features built-in AI assistant integration through MCP, Git-based synchronization, and a simple web interface for managing projects without external databases or cloud services. ## The best free project management software in 2026 DevFeed: [The best free project management software in 2026]() Original publisher: [Read original article]() Author: Kiera Abbamonte Published: 2026-10-30T14:44:00Z Content type: article Language: en Sources: [Zapier]() Topics: [task management](), [Kanban](), [To-Do](), [jira]() Tags: [2026](), [app-picks](), [best](), [board](), [but](), [calendar](), [fine](), [flexible](), [free](), [kanban](), [keep](), [like](), [management](), [need](), [others](), [paper](), [pen](), [project](), [project-management](), [project-management-software](), [software]() ### AI overview The article evaluates hosted project management tools with free plans for unlimited projects, team collaboration, flexible views, scalability, and integrations, based on hands-on testing. Trello is best suited to visual Kanban workflows; its free plan allows 10 boards and 10 collaborators but limits project views to Kanban. Asana offers list, board, and calendar views, but its free plan is capped at two users. Wrike provides spreadsheet-like tracking for unlimited users and projects, with up to 200 active tasks; Gantt charts and time tracking require a paid plan. Airtable allows extensive customization and includes 500 AI credits per editor monthly, but takes more setup and caps free bases at 1,000 records. Jira targets smaller Agile development teams, with Scrum backlog and board workflows, up to 10 users, and no free-plan user access controls. The article recommends matching a tool to team size and workflow, then trying free plans before upgrading. ### Source excerpt Everyone has a different way of managing projects. Some people like to use their inbox to keep track of tasks. Others prefer to visualize work on a Kanban board or in a calendar view, while some even prefer the old pen and paper system. That's fine on an individual level, but when you collaborate on projects as a team, you need a flexible and capable project management tool that works for everyone. And with so many teams working remotely, there's an even more pressing need for a task management ## Edi Life OS Brings Personal Tracking and Model Context Protocol to Your Homelab DevFeed: [Edi Life OS Brings Personal Tracking and Model Context Protocol to Your Homelab]() Original publisher: [Read original article]() Author: Jeremy Published: 2026-10-23T10:25:30Z Content type: article Language: en Sources: [Noted]() Topics: [Homelab](), [MSP MCP](), [AI Integration Strategies](), [To-Do](), [task management](), [AI Chat]() Tags: [ai](), [dashboard](), [finance](), [goals](), [homelab](), [kanban](), [model-context-protocol](), [optional](), [personal](), [self-hosted](), [self-hosted-personal-dashboards](), [server](), [tracking]() ### AI overview Edi Life OS is a self-hosted PHP and MySQL dashboard that combines ten workspaces, including Kanban, calendar, finance, habits, notes, and goals. Habits can contribute to SMART goals, tasks appear on the calendar, and the dashboard calculates a daily productivity score. Its optional MCP server runs locally with Node.js and uses a token-authenticated API to expose 15 tools for dashboard, habit, finance, and goal actions; tokens operate within individual account workspaces. Version 1.2.0 adds multiple accounts, but all registered users have administrator privileges, including the ability to reset others' passwords. The app requires PHP 8.1 or newer and MySQL 8 or MariaDB, and can run on amd64 or arm64 containers. The excerpt also notes no SSO or granular permissions, and says API rate limiting must be handled by a reverse proxy. ### Source excerpt Edi Life OS unites habit tracking, goals, Kanban, finance, and an optional Model Context Protocol AI server into a self-hosted dashboard. ## Deliberate Practice and Continuous Improvement in Software Teams DevFeed: [Deliberate Practice and Continuous Improvement in Software Teams]() Original publisher: [Read original article]() Author: Dean Hume Published: 2026-10-19T00:00:00Z Content type: article Language: en Sources: [Dean Hume]() Topics: [engineering-leadership](), [Agile](), [Self-organizing Team](), [Kanban]() Tags: [agile](), [engineering](), [improvement](), [kanban](), [scrum](), [teams](), [technical-leadership]() ### AI overview The article applies deliberate practice to software teams, arguing that retrospectives, goals, measurement, and honest feedback support improvement when teams act on what they learn. It cautions that ceremonies and metrics can become ineffective when teams go through the motions or misuse them. ### Source excerpt Doing something for 10,000 hours doesn't make you an expert. This post looks at what deliberate practice really means, and how Scrum and other Agile approaches can help teams keep improving. ## Google Sheets Canvas Builds Mini-Apps From Prompts: How It Works DevFeed: [Google Sheets Canvas Builds Mini-Apps From Prompts: How It Works]() Original publisher: [Read original article]() Author: TechRepublic Staff Published: 2026-10-13T16:57:52Z Content type: tutorial Language: en Sources: [TechRepublic]() Topics: [Canvas](), [generative-ai-tools](), [Tool](), [Google Apps Script]() Tags: [ai-tools](), [artificial-intelligence](), [canvas](), [dashboards](), [gemini](), [google](), [google-sheets](), [google-workspace](), [how-to](), [kanban](), [kanban-boards](), [news](), [sheets-canvas](), [spreadsheet-automation](), [subscription]() ### AI overview Google Sheets Canvas uses Gemini prompts to create interactive mini-apps, including Kanban boards and dashboards. The article describes how it works and notes subscription and availability requirements. ### Source excerpt Google Sheets canvas uses Gemini to create interactive mini-apps from prompts. Here's how to build Kanban boards and dashboards, plus subscription and availability requirements. The post Google Sheets Canvas Builds Mini-Apps From Prompts: How It Works appeared first on TechRepublic. ## The 5 best Kanban tools in 2026 DevFeed: [The 5 best Kanban tools in 2026]() Original publisher: [Read original article]() Author: Katie Paterson Published: 2026-09-28T04:00:00Z Content type: article Language: en Sources: [Zapier]() Topics: [Kanban](), [Tool](), [generative-ai-tools]() Tags: [2026](), [ai](), [ai-automation](), [app-picks](), [kanban](), [project-management](), [tools]() ### AI overview The article's tested picks serve different Kanban needs: Trello is the easiest all-around option, with a robust free plan, flexible cards, Power-Ups and Zapier integration, though reporting is limited. Breeze keeps the interface simple while adding time tracking and several task views, but has no free plan. workstreams.ai connects boards closely to Slack or Teams and uses AI to draft card descriptions and subtasks; setup is less straightforward. Sortd turns Gmail messages into board tasks and supports shared inboxes, but desktop use requires Gmail and Chrome and there is no free plan. Taskworld supports larger, interdependent projects with subtasks, cross-project cards and project chat, at a steeper learning curve and higher starting price. The article describes boards, workflow lists and movable task cards as Kanban's core structure, and says dedicated tools may be unnecessary if an existing project management app already meets the need. ### Source excerpt If you're managing a project that's a bit too complex for a to-do list app but not complex enough that it requires a full-on project management app, you're looking for a Kanban app. I've used Kanban apps a lot over the years to manage totally different kinds of projects: as a blog manager to run a content calendar, as the head of a marketing department to manage projects with my team, and I still use it today as a freelancer to juggle projects and clients. I even recently made a Kanban board for ## How I Set Up AI Agent to Access My Kanban Task Board DevFeed: [How I Set Up AI Agent to Access My Kanban Task Board]() Original publisher: [Read original article]() Author: Yash Kiran Patil Published: 2026-05-29T02:39:54Z Content type: tutorial Language: en Sources: [Linux Handbook]() Topics: [AI Agent](), [Kanban](), [Command-line interface](), [Artificial Intelligence](), [Open Source](), [Large Language Model](), [Messaging](), [personal access token](), [Rust](), [Linux]() Tags: [ai](), [ai-agent](), [blog](), [cli](), [kanban](), [llm](), [messaging](), [open-source](), [personal-access-token]() ### AI overview A hands-on guide to using Fizzy CLI with the ZeroClaw open-source agent runtime to manage a Kanban board from a terminal or messaging app. It covers installation, authentication, and connecting the CLI to an agent using local or hosted language-model providers. ### Source excerpt Life becomes easier when I can ask my AI assistant to create and manage my Kanban task board. Here's the set up I use. ## A wiki from a single Go binary: LeoMoon Wiki-Go DevFeed: [A wiki from a single Go binary: LeoMoon Wiki-Go]() Original publisher: [Read original article]() Author: Jan-Piet Mens Published: 2026-05-04T22:00:00Z Content type: article Language: en Sources: [Jan-Piet Mens]() Topics: [Wiki](), [Go Language](), [Filesystems](), [Markdown](), [Docker](), [REST API](), [Kanban](), [YAML](), [Open Source]() Tags: [docker](), [file-system](), [go](), [jan-piet-mens](), [jpm](), [jpmens](), [kanban](), [markdown](), [open-source](), [rest-api](), [wiki](), [yaml]() ### AI overview This article reviews LeoMoon Wiki-Go, an open-source wiki platform delivered as a single Go binary or Docker image. It stores wiki pages, Kanban boards, and link-management pages as Markdown files in a flat-file directory, with a REST API, web-based settings, user roles, and YAML configuration. ### Source excerpt LeoMoon Wiki-Go calls itself a modern, feature-rich, databaseless, flat-file wiki platform built with Go, and it is all that. Wiki-Go is a single-binary Go program, but there is a docker image for those who want it. I download the binary for my platform and launch it; this creates a data/ directory and its configuration file. If need be I configure a port number for it plus a timezone and the odd other setting and relaunch the binary. The program has all the features I need and more, and what I most appreciate is that I can simply drop Markdown files, images, videos, etc. into a directory to have Wiki-Go serve them. I can also move documents to other pages, so for instance, when I've finished working on the Cascade page, I'll move it into DNS/. The program also boasts an interactive Markdown editor which certainly fulfills all I expect of one, including being able to format text, add links, insert images, etc. In addition to wiki pages, the program supports the creation of Kanban boards and Link management pages, all of which are stored in *.md Markdown files. There is a REST API with examples, which might be interesting to programmatically add comments, say, but if I have access to the server, I copy files into their directories. There's a web-based settings dialog where I can add users and configure roles, but I can also add these to the YAML configuration file manually: users: - username: admin password: $2a$14$V0SkqSKvFPmJMICFqrW6qO9ufQh0befHwHE7uuJZdudK1DcGgPlY. role: admin - username: jp password: $2a$10$KdlXhhVpMiP1QPkggskUQOp4LBZ2JaSADm2ccfyl8JalN10dqmR7W role: viewer groups: - dns - tech This is really a lovely piece of work, and it is open source, and IMO its major features: Markdown in flat files on the file system, which makes it easy for me to synchronize the data directory onto my laptop and use a separate instance of Wiki-Go on that. ## 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 Request](), [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. ## 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). ## GitHub Issues & Projects - May 25th update DevFeed: [GitHub Issues & Projects - May 25th update]() Original publisher: [Read original article]() Author: Kevin Duck Published: 2023-05-25T16:31:48Z Content type: news Language: en Sources: [GitHub Changelog]() Topics: [GitHub](), [GitHub Issues](), [Linear]() Tags: [all](), [beta](), [bug](), [bug-fixes](), [changelog](), [code](), [code-search](), [dialog](), [drag-and-drop](), [either](), [feedback](), [github](), [github-issues](), [highlighting](), [kanban](), [keyboard-shortcuts](), [public](), [tasklists](), [templates](), [update]() ### AI overview GitHub's May 25, 2023 changelog announces organization project templates in public beta, mobile tasklists in private beta, bulk card updates on boards, and other project and interface improvements. ### Source excerpt Today's Changelog brings you project templates, support for tasklists on mobile, and bulk edit support on boards! 🎨 Project templates for organizations Project templates for organizations are now in public... ## A Survey of Applicant Tracking Systems for Bootstrapped Businesses DevFeed: [A Survey of Applicant Tracking Systems for Bootstrapped Businesses]() Original publisher: [Read original article]() Author: Michael Lynch Published: 2022-08-12T00:00:00Z Content type: comparison Language: en Sources: [Mtlynch]() Topics: [App](), [Requirements](), [Kanban](), [User Interfaces]() Tags: [business](), [hiring](), [job](), [kanban](), [reviews]() ### AI overview A bootstrapped founder evaluates applicant tracking systems for small businesses after managing 221 job applications through email. The comparison defines requirements, preferences, pricing limits, and dealbreakers, then reviews how different ATS products fit those needs. ### Source excerpt I'm a bootstrapped founder of a six-person company, and I spent this week testing different tools for hiring candidates. This post summarizes my experience with the applicant tracking systems (ATS) I found and how well they serve small, bootstrapped businesses. Note: This isn't affiliate blogspam where I give fake reviews to push you to sign up for whoever gives me a commission. I have no business relationship with any of these companies except as a customer. The links below are not referral or affiliate links, so I earn nothing if you sign up. Why use an applicant tracking system (ATS)? The last time I hired for a role, I posted the job on WeWorkRemotely and directed candidates to email me. I ended up receiving 221 applications, so managing them in email became messy. I came up with a folder labeling system that worked okay, but this time around, I want a purpose-built tool for tracking applications. ## 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!" ## What I Love about Scrum for Data Science DevFeed: [What I Love about Scrum for Data Science]() Original publisher: [Read original article]() Author: Eugene Yan Published: 2020-06-07T00:00:00Z Content type: opinion Language: en Sources: [Eugene Yan]() Topics: [Data Science](), [Agile](), [Kanban](), [Feature Engineering]() Tags: [agile](), [data-science](), [datascience](), [engineering](), [feature-engineering](), [kanban](), [leadership](), [learning](), [mechanism](), [optimization]() ### AI overview The author explains how an adapted form of Scrum supports data science work through time-boxed iterations, prioritization, demos, and retrospectives. The article argues that bounded deliverables help teams avoid research rabbit holes while still treating learning from experimentation as a valid outcome. ### Source excerpt Initially, I didn't like it. But over time, it grew on me. Here's why. ## 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](), [software-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: [Michael Dubakov]() Topics: [Software Process](), [Agile](), [software-development](), [Self-organizing Team]() Tags: [agile](), [agile-development](), [control](), [engineering](), [kanban](), [process]() ### AI overview The author argues that engineers should control and adapt their development process instead of following a branded methodology by default. They describe "Fake Agile" as organizations adopting visible practices such as stand-ups and sprints while retaining fixed assignments, substantial design documents, and spotty unit testing. The proposed response is process agnosticism: programmers should care about process and seek authority to change it, using systems thinking, evidence, and collaboration. Managers should support teams through education and mentoring. Development tools should be easy to adapt to changing practices; the author says process-specific tools can make switching approaches costly, citing Leankit for Kanban and AgileCraft for SAFe, and criticizes VersionOne as ineffective for any process. The text advocates flexible tooling, including support for Waterfall where a team considers it suitable. ### Source excerpt with Rick and Morty! ## Project board automation and template updates DevFeed: [Project board automation and template updates]() Original publisher: [Read original article]() Author: Rachel Nehmer Published: 2018-06-06T07:00:00Z Content type: release Language: en Sources: [GitHub Blog]() Topics: [GitHub](), [Automation]() Tags: [kanban](), [news-insights](), [pull-request-automation](), [the-library](), [workflow]() ### AI overview GitHub updated project board automation so issues and pull requests can use different actions as they are added or moved across columns. It introduced a Bug triage template and updated Automated kanban to place new pull requests in In progress while new issues remain in To do. ### Source excerpt Automate settings in your project boards for more workflow control with issues and pull requests. ## Creating new projects with board templates and project copying DevFeed: [Creating new projects with board templates and project copying]() Original publisher: [Read original article]() Author: Liz Abinante Published: 2018-05-01T07:00:00Z Content type: release Language: en Sources: [GitHub Blog]() Topics: [GitHub](), [Linear]() Tags: [automation](), [github-projects](), [kanban](), [news-insights](), [product]() ### AI overview GitHub Projects adds project copying and board templates so teams can reuse board columns, automation settings, and other configuration when starting new work. Users can copy boards into organizations or repositories where they have write access, while cards are not copied. ### Source excerpt Getting started with GitHub Projects using board templates and project copying. ## Now Open: GitHub Issues for Gradle DevFeed: [Now Open: GitHub Issues for Gradle]() Original publisher: [Read original article]() Author: Eric Wendelin Published: 2016-10-19T04:00:00Z Content type: release Language: en Sources: [Gradle]() Topics: [GitHub Issues](), [Pull Request](), [Open Source](), [GitHub](), [Gradle]() Tags: [bugs](), [community](), [extension](), [feature](), [github](), [github-issues](), [gradle](), [issue-tracker](), [kanban](), [open-source-collaboration](), [pull-request](), [reviews]() ### AI overview Gradle opened GitHub Issues for bug reports and feature requests, with an issue template to guide submissions. Reports missing required details will be marked not actionable, and closed after a week without a response. Actionable issues will be prioritized alongside other improvements; users can add πŸ‘ reactions to indicate support. Gradle will track priorities and workflow with ZenHub, which is optional and provides epics and a kanban board. Pull requests will be acknowledged within a week and reviewed using GitHub's built-in tools. As a medium-term transition, existing JIRA issues will move to GitHub, and new issues will stop going into JIRA after Gradle 3.2; the excerpt cuts off during a further roadmap commitment. ### Source excerpt Gradle has been an open-source project since its inception, but as a team we haven't always lived up to the spirit of modern open-source collaboration. For example, we haven't made it easy for folks to stay abreast of what we're working on, and we haven't had a clear and simple process for users to submit feature requests or bugs against a proper issue tracker. We're very happy to announce that all of that is changing today. We've opened up GitHub Issues on the Gradle repository, and what follows are the immediate, medium-, and long-term changes we're making to put--and keep!--the needs of the Gradle community front and center. Effective Immediately βœ”οΈŽ You can now submit feature requests and bugs through GitHub Issues. We've put together a simple set of guidelines in the form of an issue template so you'll be presented with them each time you submit a new issue. We'll label issues that don't follow these guidelines as not-actionable and we'll add a comment asking for what's missing. To keep things clean, we'll close these issues after a week of inactivity. βœ”οΈŽ Actionable issues you submit will be prioritized alongside other Gradle improvements. Low-cost changes that benefit a large number of users are the easiest to justify, so please add a πŸ‘ reaction to issues that matter to you. Like many other GitHub projects, we'll use these reactions as a simple kind of voting system. βœ”οΈŽ We'll manage issue priority and workflow using ZenHub. If you're not already familiar, ZenHub adds a number of features to GitHub Issues through its clever browser extension. It allows us to group related issues into epics and to visualize everything via a kanban board. Installing and using ZenHub is by no means a requirement, but do check it out if you'd like to get an additional level of insight about what we're working on. βœ”οΈŽ Pull requests will be acknowledged within a week and reviews of them will be done through GitHub's built-in pull request reviews. Please continue to follow the contributio ## Outage Resolution Through Automation DevFeed: [Outage Resolution Through Automation]() Original publisher: [Read original article]() Author: Target Brands, Inc Published: 2014-12-29T06:00:00Z Content type: news Language: en Sources: [Target]() Topics: [Monitoring](), [infrastructure monitoring](), [Monitoring & Alerting](), [dashboards](), [DevOps](), [Jenkins]() Tags: [2014](), [agile](), [alerts](), [automation](), [chef](), [code](), [dashboard](), [dashboards](), [data](), [devops](), [feature](), [flashbuilds](), [github](), [health](), [jenkins](), [kanban](), [kanban-boards](), [key](), [kitchen](), [managed](), [metric](), [monitoring](), [outage]() ### AI overview Project Argus used a monitoring-as-code setup to automate KPI collection and dashboards. Each Chef cookbook represented a business function's KPIs, connected to data sources, created processing scripts, and scheduled them through crontab. Processing ran on separate on-site servers, while dashboards were decoupled and cookbook definitions were dashboard agnostic, allowing presentation changes or a dashboard switch. Dashboards also detected missing data and sent chat alerts. When the monitoring servers went down on 2014-12-06, the dashboards went blank and the health monitors alerted within minutes. The excerpt ends before describing how the outage was resolved. ### Source excerpt Recently we launched Project Argus, a 30-day "monitoring challenge" to improve visibility of key performance indicators (KPIs) across our technology stack prior to our peak retail season (in Greek Mythology, Argus is a 100-eyed giant). This effort was structured as a mix between a FlashBuild and agile. We used two day sprints, twice a day stand-ups, and feature tracking through Kanban boards. Quickly in this effort we decided to build our product as monitoring-as-code. Through the use of tools such as GitHub, Chef, Kitchen, Jenkins, and Ruby, we were able to quickly build several monitoring and dashboard solutions for use within our Technology Operations Center. These dashboards and the iterative process we use to continue delivering more content have been embraced by our support teams who now heavily rely on them to proactively detect and resolve issues. One deliverable from Argus includes a cookbook per core business function that represents the KPIs identified by each business product owner. When run, the cookbooks establish connections to our data sources, build the scripts that process our data, and create crontab entries to automatically run the scripts at our predefined intervals. All of these resources and actions are defined in code. We designed our solution so that the dashboards are decoupled from our centralized processing and metric creation. Additionally, our cookbooks are written to be dashboard agnostic and independent so that anyone can make changes to the appearance and we can switch dashboard solutions easily. The processing of our metrics is centralized and managed on-site with each cookbook receiving its own server. Finally, our dashboard solution detects lapses in data and generates alerts that post into our persistent chat client. This allows us to close the loop on the health of the monitoring system, which can be a painful endeavor! ##The Problem Unfortunately, on 2014-12-06 at around 1:30pm the servers we use to process the monitoring data ## How to Manage Development Projects with a Trello Kanban Workflow DevFeed: [How to Manage Development Projects with a Trello Kanban Workflow]() Original publisher: [Read original article]() Author: Harry Roberts Published: 2014-05-02T21:34:30Z Content type: tutorial Language: en Sources: [CSS Wizardry]() Topics: [Kanban](), [software-development](), [Agile](), [DevOps](), [Software Testing]() Tags: [acceptance](), [agile](), [backlog](), [board](), [development](), [devops](), [implementation](), [kanban](), [project](), [project-management](), [projects](), [sprint](), [testing](), [workflow]() ### AI overview A practical guide to using Trello as a Kanban board for managing software development projects, including distributed-team work, project columns, backlogs, implementation, and acceptance testing. ### Source excerpt How I manage development projects using Trello ## Agile is Poisonous DevFeed: [Agile is Poisonous]() Original publisher: [Read original article]() Published: 2013-04-01T15:41:57Z Content type: opinion Language: en Sources: [Michael Dubakov]() Topics: [Agile](), [Kanban](), [Standup Meeting](), [pair\_programming](), [Test automation](), [Software Testing]() Tags: [acceptance-tests](), [agile](), [agile-development](), [iteration](), [kanban](), [meetings](), [productivity](), [qa](), [requirements](), [scrum](), [technical-debt](), [testing]() ### AI overview The author reports that their company abandoned several agile practices after finding them unproductive: daily standups were replaced by weekly email status reports, while one- and two-week iterations brought meeting overhead, rushed work, technical debt, and testing difficulties. Kanban's 23-state board and later state limits did not prevent deadline pressure, work-in-progress overload, or reported 100-hour weeks. The account also describes punitive productivity displays and enforced pair programming, which led to conflict and, in one incident, a broken nose; pair programming was then banned. These are the author's company-specific experiences, not evidence that the practices fail universally. ### 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