Okay, that's the one.
Okay, so my name is Glenn Erksson.
I'm going to present a study that we have done.
I started in 2023.
I'm just working for a non-profit research organization.
I focused on applied research in development established in 2011 in Sweden.
And our project, generally focused on open source,
Open Data Research within the transport sector.
In case there are open source ecosystems studies from 2012,
suggest that participation in open source development can reshape
organization practice includes software development methodologies,
knowledge management approach and innovation processes.
And a few studies on how open source participation
contribute to organization transformation,
especially traditional organization,
lacking pre-existing digital transformation capabilities.
So that's if this work.
Okay.
Yeah, so our study centers around digital transformation
in the public organization,
especially in public transportation organization.
And this is a study literature review from 2021,
where digital transformation is seen as a top-down initiative
consisting of two main themes.
It's a maleable organization design to adopt to constant change,
changing environment and embeddedness in the digital business ecosystem,
which characterized by their ever evolving turbulent nature.
I won't go into more details,
but this is another study done on from 2019
on traditional organization in several different sectors.
And they came out to this different capabilities
that organization needs to be digital transformed
and engage in the digital ecosystem.
So transformation challenges.
Public organization,
generally determined by cost focus,
outsourcing, contractual relationship,
function-based procurement and fixed-time frame,
which impedes digital innovation and transformation.
Studies from the mid-2000 established that contractual relationship
impedes innovation and responds to market change.
So this is all news.
But I don't know how many of you work in the public sector
or transportation sector.
Okay.
Is that new to you?
You are totally...
Huh?
It's not really new, but must I have a side again?
Exactly.
I'm going through this quite quick,
so we can go to the core of the presentation,
but I just need to get everybody on board.
And rigid and silo-based organization
can lead to development creates ad hoc IT solution,
called shadow IT,
to fix or solve immediate problems.
This can further fragment the overall IT system environment,
and create overlap and lead to resource waste.
So yeah, let's speed up.
So now we come to the topic for this presentation.
Study on community engagement.
So the idea for the study started in, as a report in 2023,
on how open source was used to digital digital disrupt
the public transportation sector in Norway.
To see if other organizations,
you're only resemblance to one from Norway.
Finding one in session to interview in the community took one year,
and was concluded in October 2025.
So quite recently.
It's quite hard to interact with open source community,
because it's quite opaque,
which people engage in, which organization,
maybe there is only a GitHub account or that's what you see.
It's quite hard to find number of organizations.
But to finally make it, we find 13 of them.
So how much time do I have?
Seven minutes, I'm up there, okay.
So the result of the study, which I will present soon,
is submitted as a full conference paper by me
and Professor Yuho Linman from University of Gothenburg,
to the European Conference on Information System,
which is in Milan, in 2006.
And their announcement for submitted papers
will be in the end of February, I think, so we don't know yet.
So the things I will show you now, it's important to notice
that the model I will present applies to developer communities,
open source communities.
The community, in the study, is quite small,
but the narrow focus have a meritocratic governance model,
dedicated member organization, and have very few hobby programmers.
The relevance for other types of communities,
such as vendors, sponsored, user and phone nation communities,
with other governance model needs to be studied further.
So this doesn't apply to everything, or we hope maybe
some of them or findings will address also other communities.
So let's see, this is, I won't go through everything,
because it's quite, a lot of things in the model,
but I will start with, let's see if I see all the text.
So to start your present, an open source community engagement model,
consist of three main elements, organization, community,
and digital transformation.
I've great up everything here else, so you don't have to focus on that now.
Organizational element represent the internal incentives and activity,
perform to align the organization to the community.
The more involved they get in the community, the more aligned they become,
and the process iterative, and continuous.
That's the back and forth arrow there.
So nine minutes.
Organizational activity sub-aliment consists of evaluating community viability.
This is an activity prior to taking the decision to engage in a community.
This entails assessing the open resources, such as documentation, code base,
repository interactions, frequency, number of maintainers, et cetera.
But the most time-consuming event is activity to determine if the software
design and architecture is sound and viable.
This you need developer competence and next element, maybe the main one.
This is more massive.
This is the community.
The community element represent the mechanisms.
The organization can potentially access when they align themselves to the goal,
culture, and process to the community.
The element is divided into sub-part culture, process, and capabilities.
So the culture, sub-aliment is part of the, is the part that holds the community together.
And it's determined by the number of agreed upon principles.
So, yeah, you can see it here.
Maricrocratic, trust-based governance, and altruistic environment.
Probably not going into that.
So you can ask me later if you want to know more about that.
And the processes, sub-aliment represents a collaborative and distributed development.
And of course, in that occurs in the community.
And there you have a collaborative development.
It illustrates how organization either by taking terms of joint coordinate development
initiative in the community.
So for initiative to occur, one or more members have to take responsibility to push the
change request through the community.
And then we have knowledge creation.
That was another theme we found.
It's a process depicts co-creation and sharing of experience and insights between
members.
The creation of and sharing knowledge can happen in both developer and product
product on the level.
That's what we've seen in this case.
And then you have the software quality insurance and assessment,
which stems from the fact that co-groups the repository is public and open to everyone
and programmer take responsibility professional pride in their work.
So, yeah, that's part of the community engagement.
And let's see if I can see the last one.
And then we have the capability sub element,
which epitomize the technical competence and proficiency in the community,
which you can access.
The talent that the community attracts are related to the personal motivation
and technical problems the community tries to solve.
So this is more, I'm talking about general things here.
So the state of the art technology, the digital technology,
portrays the interest in finding the best possible solution to one
or a set of problems.
And then we have modular and deptable system design.
It's a capability that is too folded.
The first is that open source solutions are made to be more adaptable
and comfortable to suit different use cases.
And the second one is that adaptability comes at an increased
developer cost due to its more flexible design.
And a holistic use case perspective entails a variety of ways
to solve domain business domain problems.
For the members in the community,
this translates to new insights or alternative perspective
on solutions that are both scalable and adoptable.
And then we have the partnership and synergy opportunity,
which portray the possibility to find other members
with similar requirements and form partnership based on trust.
For example, members can form different clusters depending on the region
or continent if it's a global open source community.
And access to global competence pool, which members can utilize here.
And a cumulative competence and experience is access
through documentation, communication channels,
and also prevent members from repeating common mistakes
when they engage in the community.
So that's the model.
So let's see what this implies.
Model implications.
So the model aims to describe the dynamic integration
where organization and community mutually shape each other.
So for organization, adapting their structure,
process, and practice over time to align to the community,
norms, and governance mechanism.
And also the community evolves through a diverse organization interaction
by incorporating different use cases, perspectives,
and expanding its pool of capabilities and resources.
And the engagement opens up for access to state-of-the-art technology
and model design that I showed before,
to fit a wide range of use case scenarios.
And organization that invest sustain resources
and demonstrate loyalty to community objectives,
gain influence, and access to deeper collaboration opportunities.
And let's see, the last exhale, maybe that engagement enables
those access to pool of developer competence,
either within the organization or individual individuals
that can be contracted or funded through community initiatives.
And important here that these talents are probably not easily hired
or recruited nationally, and are not access easily access
if organization is part of the organization.
So this is resources that you can use when you are a member.
So for the next one, let's see, yeah, organization implications.
Yeah, engagement in community can through core involvement,
build the transformative organizational capabilities.
So this pathway requires investment in the developer competence,
allocating sustained resources, and demonstrating commitment
to the community principles.
Let's see, the time, 19 minutes, let's move the evaluation
of the community is a critical preliminary activity,
or organization need to assess not only technical factors,
but also other things such as governance,
maturity, contributor diversity, and alignment
between community objectives and their organization.
And engagement in open source community may manifest as a partial
or department transformation.
This is attractive opportunity for maybe strict structural
rigid organization or traditional organizations.
And yeah, this maybe leads to the road of the digital transformation.
If you're a traditional rigid organization or a pathway to it.
So that we've seen that procuring of the shelf standardized solution.
Does not facilitate knowledge transfer or trigger change in its
to international organizations.
So we see that engagement in the open source community is a
bottom up approach to engage or transform organizations.
Normally a digital transformation is geared from the top,
top down initiative, but we've seen that several organization
that interacts with the community starts to change the
transformation starts in the department and maybe
radiates the other part of the organization.
And let's see, we'll have one more.
Yeah.
So back again, organization need developer competence.
Either they have it in house or they procure it.
You see everything from organization have all the developer teams in
house to other organization, recruiting teams of developers as
call something working either locally or in other locations.
But the minimum was that the organization in this study at least
have project leader or product owner inside in house competence.
And this was seen as important for the industry transfer and
the long-term commitment to the open source community.
And the longer and deeper the better opportunity becomes for
knowledge transfer use case perspective and etc.
And tied to the long-term investment resources is a loyalty
also to the community, which increase influence and access to
deeper collaboration opportunities.
Yeah, and also loyalty culture.
Maybe that doesn't fit all organizations.
Time up.
Okay.
Good.
Okay.
The research project has ended.
So I'm open for questions.
And if somebody has, yeah, if they want to see this study
continues, maybe they can talk to me afterwards.
If they have national funds or European funds because we're
on profit and we're searching for new research projects.
Thank you.