Building open-source Kanban frameworks inside the Celean research lab

The Celean team operates at the intersection of academic research and practical engineering, developing open Kanban tools that organisations can adapt without paying licence fees. Housed at Chalmers University of Technology in Gothenburg, the group brings together researchers, graduate students and industry engineers who share a common interest in visual planning, lean workflows and enterprise systems. Their work has been watched closely by software teams in Sydney, Melbourne and Brisbane, where demand for transparent project management tools has grown alongside the country's expanding technology sector.

In Australia, the appetite for open-source workflow software has been shaped by a long history of resource-based industries adapting lean principles to remote and hazardous environments. Mining operators in Western Australia, for instance, have used visual planning to coordinate shift handovers across fly-in fly-out sites. Manufacturers in Melbourne's outer suburbs have applied similar methods to automotive supply chains. Celean's frameworks fit neatly into this context because they allow companies to host their own planning infrastructure rather than relying on overseas cloud platforms subject to foreign data laws.

The team's projects are not built in isolation. Volvo, one of the founding industry partners, has provided testbeds inside its production facilities, and several smaller European manufacturers have contributed requirements. Celean's researchers also publish their findings through academic journals, conference papers and the Project Visit website, making the technical documentation and code freely available to practitioners. This blend of rigour and openness has positioned the group as a quiet but influential contributor to the global Kanban community.

For readers who manage software, engineering or research teams, the Celean story offers more than a case study in academic collaboration. It shows how an open framework can mature when researchers respect the constraints of real workplaces, including Australian ones governed by the model Work Health and Safety laws that apply across most states and territories.

Roots at Chalmers and the academic foundation

The Chalmers Electronic Lean Research Team was established to study how digital tools can support lean thinking without undermining the human judgement at the heart of the system. Early work focused on simple electronic boards that mirrored physical Kanban cards, and the team soon realised that the most interesting research questions sat at the boundaries between software engineering, operations management and human factors. Funding from Swedish research councils and a handful of industry partners allowed the group to recruit doctoral students, several of whom now lead sub-projects on workflow analytics, board design and policy automation.

This academic anchoring matters because it gives the Celean frameworks a different flavour from commercial offerings. Vendors typically optimise for revenue and market share, which can lead to feature bloat. Celean's code instead reflects what researchers can justify with evidence, and the documentation frequently cites peer-reviewed studies. When Australian practitioners evaluate the frameworks, they often find the rationale for each design choice explained more thoroughly than in proprietary alternatives, an important consideration for teams that must justify tool selections to procurement officers.

The Chalmers environment also provides access to manufacturing engineering students who use the Kanban systems as living laboratories. A student assignment might involve redesigning a signal mechanism, measuring cycle times or building a small extension that integrates with an enterprise resource planning suite. The resulting contributions flow back into the open repository, where they are reviewed and, if accepted, become part of the next release. The cycle keeps the software honest and the curriculum current.

Working with industry partners

From the beginning, Celean has treated industry partners as co-researchers rather than customers. Volvo's plant engineers contributed the initial requirements for visualising work-in-progress limits, and they continue to validate new features against real assembly lines. Similar arrangements exist with regional manufacturers in Sweden and with software firms interested in lean service operations. The partnership model means that every release of the framework is shaped by someone who must operate it under production pressure.

In Australia, this approach resonates with manufacturers in Melbourne and Adelaide who have struggled to find Kanban tools that respect local shop-floor practices. The South Australian defence sector, for example, operates under the Commonwealth's Defence Industry Security Program, which imposes constraints on where sensitive project data can be stored. Open-source frameworks that can be self-hosted on Australian servers have an obvious advantage over cloud services routed through foreign jurisdictions. Several Australian integrators have already approached Celean to explore localised deployments, though formal partnerships are still in early discussions.

Celean's researchers travel regularly to meet partners, observe workflows and run workshops. These visits are not only about gathering requirements; they also help the team understand how cultural factors shape the use of visual management. A pull system that works in a Scandinavian plant may need adjustment in a multicultural Australian factory where shift workers speak several languages and rotate across sites. The willingness to absorb these nuances has earned the team a reputation for thoughtful, rather than off-the-shelf, collaboration.

The choice of open source

The decision to publish Celean's frameworks under a permissive licence was deliberate. Researchers want their work to be read, used and tested, and restrictive licences create friction that few independent teams will tolerate. By releasing code publicly, the group invites scrutiny and contribution, both of which raise quality over time. The licence also aligns with the expectations of public-sector bodies in Australia that increasingly prefer open solutions to avoid vendor lock-in.

Open source does carry responsibilities. The Celean team must maintain documentation, respond to bug reports and review community patches. They have invested in contributor guidelines, code-style rules and a public roadmap so that newcomers can find their footing. The repository is structured to make it easy for an Australian software house to fork the code, add a local feature and, if useful, send the change back upstream. This kind of reciprocity is the lifeblood of healthy open projects, and Celean treats it as seriously as the research itself.

Critics sometimes worry that open Kanban tools will be abandoned when funding runs out. The Chalmers group has addressed this concern by building a broad contributor base and by ensuring that the code does not depend on exotic libraries. The frameworks are written in languages familiar to most Australian developers, which lowers the cost of long-term maintenance for organisations that adopt them.

Architecture of the Celean frameworks

At a technical level, the Celean frameworks are modular. A core engine handles board state, signal rules and audit logs, while plug-ins add visualisations, integrations and notifications. This separation allows teams to start small, perhaps with a single team board, and expand to programme-level planning without rewriting the foundation. It also makes the code easier to test, an important property for systems that may eventually support regulated industries.

The frameworks expose a documented application programming interface that enterprise systems can call. In practice, this means a Brisbane-based software company can connect a Celean board to its existing customer relationship management platform, or a Perth mining contractor can link planning signals to its maintenance management system. The integration story is deliberately pragmatic: rather than dictate a single source of truth, the team encourages its tools to sit alongside established enterprise software and exchange data through well-defined contracts.

Security and data sovereignty have become central concerns for Australian adopters, particularly those subject to the Privacy Act 1988 and the notifiable data breaches scheme. Celean's self-hosted design gives organisations full control over where board data lives, whether on premises in Adelaide or in a Sydney-based data centre. The team has also published guidance on configuring authentication, logging and backup procedures that align with the Australian Cyber Security Centre's recommendations.

Field testing in real workplaces

Before any new feature lands in a stable release, it passes through a small pilot phase. Industry partners operate the candidate build alongside their existing tools and report back on usability, performance and unexpected edge cases. A new signal policy, for instance, might be tested on a Volvo assembly line for several weeks before being promoted. This discipline is unusual in open-source projects, but Celean argues that it is essential when the software influences the pace of physical work.

Australian workplaces have occasionally contributed to these pilots, even if informally. A software team in Sydney's Surry Hills used an early version of the framework to coordinate releases across three product squads, and a civil engineering firm in Perth adapted the signal mechanism to manage permitting workflows. The lessons from these off-the-books experiments feed back into the design discussions at Chalmers, often via blog posts or conference talks.

Safety is another dimension where field testing matters. Visual planning tools that shape the rhythm of work can affect fatigue, error rates and incident response. Celean's researchers have begun cross-referencing Kanban data with safety records, and families who want to understand how drills translate into household preparedness can read more through resources that explain household safety drills and the structured practice that visual management encourages in workplaces.

Bridging physical and digital Kanban

Despite the rise of digital tools, many teams still value the tangible presence of a physical board. A well-placed whiteboard in a team area provides a constant reminder of work in progress, and it invites informal conversations that purely screen-based systems often miss. Celean has studied this duality closely, and its frameworks are designed to coexist with physical boards rather than replace them.

In a hybrid setup, the digital framework records the authoritative state of work while a physical board offers at-a-glance visibility. Workers update the wall during stand-up meetings, and a designated custodian transcribes the agreed changes into the system. This pattern suits Australian teams in industries such as construction and resources, where site conditions can make screen use inconvenient. It also aligns with the practical argument laid out in a Project Visit review on physical Kanban boards in modern digital workplaces.

The Celean team has explored camera-based and sensor-based methods to automate the synchronisation between physical and digital boards, although none of these has graduated to a production release. For now, the human bridge remains the most reliable mechanism, and the documentation offers advice on making that handoff as smooth as possible.

Building a contributor community

An open-source project is only as healthy as the people who care about it. Celean invests in its community through regular video calls, a public chat channel and an annual gathering held alongside a lean software conference. Contributors are credited in release notes, and students who contribute substantial work can sometimes extend their involvement into master's or doctoral projects. This pipeline has produced a small but loyal group of maintainers spread across Europe, with growing interest from North America and the Asia-Pacific region.

Australian developers are beginning to appear in the contributor logs. A volunteer in Brisbane has been improving the time-zone handling in the notification system, and a team in Canberra has translated portions of the documentation into English variants more familiar to local readers. These contributions may seem minor, but they signal that the framework is becoming genuinely global rather than a purely European endeavour.

Celean also welcomes researchers who want to use the frameworks as testbeds for their own studies. Anyone interested in workflow analytics, human factors or lean service operations can request access to anonymised data sets or deploy the software in a controlled experiment. This openness ensures that the project continues to generate fresh questions, which in turn keeps the research agenda lively and the code evolving.

Practical guidance for teams considering the frameworks

• Start with a single team and a clearly scoped pilot before scaling across the organisation.
• Involve frontline workers in board design so that visual signals match the actual rhythm of work.
• Plan for hybrid use, where physical boards and digital state coexist, to capture the benefits of both.
• Document local configuration choices, especially authentication and data residency settings, to satisfy Australian regulatory expectations.
• Allocate time for code review and contribution, even if your team only consumes the software today.
• Engage with the upstream community through bug reports, documentation edits or feature discussions.

The Celean approach demonstrates that open-source Kanban frameworks can be both academically credible and operationally useful, provided the team behind them respects the realities of the workplaces that adopt the software. For Australian organisations navigating lean transformations under local safety and privacy laws, the project's combination of self-hosting, transparent design and active community offers a workable path away from vendor lock-in. The most practical step any interested team can take is to install the framework on a small internal server, run a one-team pilot for a quarter and document the lessons before committing to a broader rollout.