InnerSource - A way to spread the Open Source way / culture in organizations?
Hey @opensource, I’d like to share a bit about #InnerSource, it is the practice of adopting the open source practices and cultures for in-house software development and software-like projects.
If you are interested, there is a ton of material gathered by the community at https://innersourcecommons.org/
I’m currently working with this topic and I could not see a lot about in in the #Fediverse yet.
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.