26
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 May 2025
26 points (100.0% liked)
Open Source
37004 readers
109 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
It’s funny (or depressing), because the original concept of agile is very well aligned with an open source/inner source philosophy.
The whole premise of a sprint is supposed to be that you move quickly and with purpose for a short period of time, and then you stop and refactor and work on your tools or whatever other “non value-add” stuff tends to be neglected by conventional deliverable-focused processes.
The term “sprint” is supposed to make it clear that it’s not a sustainable 100%-of-the-time every-single-day pace. It’s one mode of many.
Buuuut that’s not how it turned out, is it?
@kibiz0r @CapriciousDay
> it’s not a sustainable 100%-of-the-time every-single-day pace
The agile manifesto seems to disagree with you:
> Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
And it has some answers for the development of tools and refactoring as well.
The process is supposed to be sustainable. That doesn’t mean you can take one activity and do it to the exclusion of all others and have that be sustainable.
Edit:
Also, regretably, I’m using the now-common framing where “agile” === Scrum.
If we wanna get pure about it, the manifesto doesn’t say anything about sprints. (And also, you don’t do agile… you do a process which is agile. It’s a set of criteria to measure a process against, not a process itself.)
And reasonable people can definitely assert that Scrum does not meet all the criteria in the agile manifesto — at least, as Scrum is usually practiced.
@CapriciousDay yup, that's something that needs to be addressed and it is a more fundamental issue. If employees are not given enough empowerment, than cross-team collaboration and innovation suffers for sure. Nevertheless I think it is possible to have this together with scrum and other agile methodologies, as long as some capacity is reserved for this type of activity that requires empowerment.
And contributions to codebases that have developed with the goal of meeting the team's own needs, and who similarly don't have the time or space to refactor or review as needed to enable effective contributions.
Enabling Innersource will be a priority for management for only two weeks, anyway, before they focus on something else. And if it even makes it into measurable goals, it will probably be gamed so it doesn't ruin bonuses.
Do you also work for $GenericMultinationalCompany, per-chance? Do you also know $BillFromFinance?
@jbloggs777 @CapriciousDay Those problems are real for sure, but on the other hand, we also have open source enthusiasts working on such companies, and having InnerSource as a well defined practice in the industry could give them at least some "ammunition" to bring the open source culture and practices to their organization.