Cooperation Process
Notes
Mastering the complexity of software development depends highly on Cooperation.
In context of cooperation, Open Source Projects have great benefits against Closed Source Projects.
In practice, Open Source Projects lack cooperation.
2 major reasons can be identified quickly:
- Personal Goals of the Project Lead (or the whole core Team)
- Non Awareness about cooperation possibilities.
Subsystem Level
- Clarify Overall System Structure (Subsystem Overview)
- Review Subsystem Overviews of similar Projects (even competitive)
- Isolate Common Subsystems
- Arrange cooperation (e.g. create seperated Subprojects)
Analyst Level
- Prices for Analyst Services can be very high
- Identify Open Source Projects / Companies
- either with similar problems (e.g. same domain)
- or which create a solution when combined (persistency, template-system, GUI)
- Share costs for analyst services
Clarifications
If the results of an analysis are publically available, why should a project pay for them?
- To be able to direct the analysis.
- To get results which are based on the own system.
- To simplify the rework of the own system.