Skip to main content

Table 8 Main results of the cycle 2 Evaluating phase

From: ScrumOntoBDD: Agile software development based on scrum, ontologies and behaviour-driven development

Product Owner (PO) Software Engineer (SE)
Focus on the application development Focus on the development methodology
Advantages Disadvantages Advantages Disadvantages
Phase for defining a common language between user and developer Does not use screen prototypes
Probably the usual POs will have understanding difficulties
Use of formal methodology to complement Scrum Longer development process
Use of “records” that give visibility to the development phases and enable the PO collaboration on those phases Need for an additional actor, the Ontology Engineer, and likely an increase of the system cost Use of “records” that facilitate the communication with the user Does not use screen prototypes
Probably the usual POs will have understanding difficulties
Possibility of better result with less code repair Likely increase in system development time Better communication with the developer, and consequent increase in productivity  
   Likely reduction of code repair  
   Probably better cost/benefit ratio