Skip to main content

Table 7 Main results of the cycle 1 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
Agility due to weekly meetings Lack of more systematic "records" that could give more visibility to the different development phases Using agile software development methodologies like Scrum Scrum distributes roles and activities to team members, but does not explain how to implement these activities
Lack of a formal methodology that facilitates the communication with the user and with the developer
Using screen prototypes Lack of development team experience Using screen prototypes Division into non-testable sub-tasks throughout the process
Need for more frequent meetings during the requirements gathering phase
Software that “handles the Medicine Programme needs” Lack of openness for more effective collaboration, not taking advantage of PO meaningful prior experience   Not testable with a real data set
  Discontinuity and very delayed testing   Lack of development team experience
    Lack of openness for more effective collaboration, not taking advantage of SE meaningful prior experience
    Discontinuity and very delayed testing