XM SEBD Assessment Procedure: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
Once any SEBD is documented, it should be assessed for possibility to break the technology down into further components. The goal is to break down a technology into the smallest size possible to allow for simultaneous development by a large, distributed team. The large team can work independently once the interface between the components has been identified clearly.
Once any SEBD is documented, it should be assessed for possibility to break the technology down into further components. The goal is to break down a technology into the smallest size possible to allow for simultaneous development by a large, distributed team. The large team can work independently once the interface between the components has been identified clearly. If significant breakdown occurs, this allows for large gains in development velocity via parallel development.
 
The Product Owner should perform the assessment. Crowdsourced assessments are welcome under these conditions:
 
*Contributor lists their qualifications which allow the contributor to make a grounded assessment of the work product
*Contributor acknowledges adherence of the assessment to [[OSE Specifications]]


[[Category:XM]]
[[Category:XM]]

Latest revision as of 05:04, 27 March 2012

Once any SEBD is documented, it should be assessed for possibility to break the technology down into further components. The goal is to break down a technology into the smallest size possible to allow for simultaneous development by a large, distributed team. The large team can work independently once the interface between the components has been identified clearly. If significant breakdown occurs, this allows for large gains in development velocity via parallel development.