To better align software projects with the organizations in the OSDUTM Forum and develop clear working agreements and expectations
Who is involved
Three primary technical subcommittees (Enterprise Architecture [EA], Data Definitions [DD], and Information Security [IS]) are generally tasked with ensuring that all platform behavior is aligned with the consensus of the members.
The Business Model subcommittee (BM) is tasked with... (communicating, prioritization?)
Project Management Committee (PMC)
The PMC is generally tasked with ensuring the stable development of the platform, championing meritocracy among the contributors, and ensuring a 'working whole' as implemented in open source software.
Overlapping accountabilities between technical subcommittees and PMC
There is not always a clear accountability on roles and responsibilities for projects in relationship to governance by the technical subcommittees and the project management committee (PMC). This is further complicated in the fact that forum members (individuals) are often both members of the technical subcommittees (i.e. they have a subcommittee role) and also members of various PMC projects (i.e. they have a software project role).
Multiple projects required to achieve a capability
Related "projects" get started in separate areas to address the same capability (outcome). Each "project" may only focus narrowly on the scope of the specific area it has been started within (e.g. Data Definitions) and interactions with related projects required to deliver a working capability (useful outcome) are inconsistent. This also creates confusion for members on where they might join in the dialog as a single capability gets worked in multiple subcommittee meetings.
There have been some attempts to address this by assigning various subcommittee liaisons to specific projects. This may be an opportunity to clearly document those roles and bring clarity.
Related conversation happening in different subcommittee meetings
The same topics are discussed in difference subcommittee-specific meetings without a significant overlap in people attending. This is leading to siloed conversation which can result in misalignment and confusion about path forward.