Pattern idea: Integrate InnerSource with DevOps by exposing roadmaps/backlogs along with the code

[NewMexicoKid]

• Inter-team collaboration can work by exposing code, documentation, roadmaps,
  backlogs, and sprint plans. The data is made openly available to drive the
  discussions between the teams.
• Keep your agile-project management tools open and findable.
• Contributing developers would need to fit in with the owning team's sprints
  when a dev is submitting one-off merge requests, etc.
• When teams work together over many sprints to deliver larger services works a
  bit differently.
• Note: It helps to NOT colocate teams (so async written communication can create lazy documentation)
• CI/CD can make it easier to validate contributions.
• Question: how do you protect the CI/CD pipelines of products that are using the IS component?
• Question: Should there be a simple process for contributing automated tests to a shared set (to prevent breakage downstream)?
• Question: What happens when something downstream detects a problem? Who debugs these issues?
• Question: Do contributors join development sprints of the owning organization?

References

• Notes from a discussion in the ISC

[spier]

@NewMexicoKid @ErinMB sorry if you are tired of my GitHub spam already :)

I don't think there is a PR associated with this pattern idea already, or did I miss it?

I was wondering if either of you wants to work on this pattern, or if we can archive this issue?

[spier]

Original title:

Pattern idea: Integrate InnerSource with DevOps by exposing Agile team roadmaps, backlogs and sprint plans along with the code