concept

OSPD

Also known as: Open Source Product Development

Facts (17)

Sources

Seven observations and research questions about Open Design ... cambridge.org Cambridge University Press Oct 19, 2021 17 facts

claimOSPD is original because it integrates evolutionary mechanisms, such as branching and derivatives, directly into day-to-day development tools.

claimProduct development in OSSD and OSPD is characterized as an ongoing process of continuous improvement by a community rather than a project with defined inputs, outputs, and timelines.

quoteRaasch & Herstatt (2011) observe that in OSSD and OSPD, 'stable versions […] co-exist with experimental versions'.

claimDemonstrating the feasibility of end-to-end Open Source Product Development (OSPD) requires focusing on downstream processes and experimenting with business-led, open industrialization processes.

claimCurrent Open Source Hardware and Open Source Product Development (OSPD) practices often recreate controlling mechanisms to maintain the applicability of known design methods in the absence of formal hierarchies.

claimStandardization initiatives and referencing databases help codify shared practices and provide access to OSPD project outcomes.

claimOSSD and OSPD projects utilize Distributed Version Control Systems (DVCS) for management and governance, which departs from the traditional Product Data Management (PDM) systems used in engineering.

claimParticipants in OSSD and OSPD projects engage in self-selection and self-identification of tasks, which is incompatible with centralized hierarchies and traditional project or resource planning.

claimIn OSSD and OSPD, the determination of which repository copy or branch acts as the reference is decided by agreement among developers and can be revised.

claimOSSD and OSPD projects prioritize encouraging divergence over controlling convergence, a behavior explained by their specific governance models.

quoteLee & Cole (2003) describe the OSSD and OSPD design process as an 'experimental tree […] where innovative variations and experimentations are generated, tested, and selected to become a part of the stable tree where further refinement and improvement are conducted'.

claimOpen Source Hardware and Open Source Product Development (OSPD) initiatives often mimic conventional, centrally structured product development processes to fit into existing prescriptive design methods.

claimOpen Source Hardware (OSHW) is an instantiation of OSPD that possesses a history of practices and sectoral organization.

claimThe community-driven, continuous improvement model of OSSD and OSPD induces challenging turnover among contributors.

claimOpen Design, Open Source Hardware, and OSPD are emerging phenomena attempting to gain maturity and move beyond marginality to offer alternatives to conventional proprietary product creation.

perspectivePractitioners of Open Source Product Development (OSPD) would benefit from practical product design guidelines and operable design principles to help establish active contributor communities.

claimSubteams in OSSD and OSPD can branch out from an original stream to create a derivative product.