Open Source Has Arrived – And it Needs to be Managed
OpenSource needs to be managed
Everyone knows it. Tasks pile up, something constantly comes up and it becomes confusing to distribute all projects or tasks amongst employees.
Decision Kanban or Scrum Board?
Kanban method
Do you work on projects with different priorities and tasks? Are new tasks constantly being added? Then Kanban (very flexible) should be the most suitable.
Professional software: Atlassian Jira (large projects, complex workflows, but expensive), Alternatives Trello, Stackfield
Since Mattermost was already being used for internal communication, I looked at the board solution also offered here.
And the test of this board began...
Since our example is about app customisation and redevelopment, we choose the roadmap template provided by Mattermost.
![]() |
A board for sprints and a board for the normal status were automatically created. In addition, there is a calendar view, a list for errors and one for tasks. |
Here we add another group for testing

Now we have all the groups we need

Under "not Started" we now create the new projects

Here, too, many different adjustments can be made
|
|
Subsequently, the tasks can be distributed to individual employees. By changing the status, the task moves through the workflow

The individual tasks or bugs are summarised in the respective lists
![]() |
![]() |
OpenSource needs to be managed
Compliance, risk management, banking compliance
Cloud migration, Accxia Cloud