Delivering User Stories for Implementing Logical Software Architectures by Multiple Scrum Teams

Abstract

Abstract. In software projects, agile methodologies are based in small development cycles and in continuous communication with customers with low needs on modeling formalism for requirements elicitation and documentation. However, there are projects whose context requires formal modeling and documentation of requirements in order to raise and manage critical issues from the very beginning of the project, like architectural diagrams. This work presents an approach for deriving a list of User Stories using a logical architectural diagram as input. Derived User Stories are then delivered to multiple Scrum teams.

Risk management analysis in Scrum software projects

“…Some authors mention the importance of a formal documentation in Scrum projects. According to Costa et al (), formal documentation is important to initiate the development phase, especially when the developed software is large and is being implemented in parallel by several teams. Read and Briggs () mention that the lack of formal documentation of Scrum projects makes it harder for knowledge transfer from the project to big teams.…”

Review of approaches to manage architectural knowledge in Agile Global Software Development

“…In [50,62,[67][68][69]79], a phase called sprint zero (also called pre-development phase [68] or domain engineering [50]) has been introduced to develop a common understanding of requirements and to propose a first architecture proposal. A similar approach is presented in [67], where a phase of analysis and design is executed based on the V + V process [80] (the first execution of the V-model relates to analysis, while the second relates to design). After executing the V + V process, a logical architecture is obtained, which could be segmented into modules, and each module is assigned to a Scrum team.…”

Ambiguity in user stories: A systematic literature review

“…Inconsistency is a problem that occurs within a set of related user stories if interpretations conflict, hence it is a problem of ambiguity. The reviewed studies showed that inconsistency may result in requirements being incomplete [41,43,46,47,49,53,73,74,76] and systems being non-compliant [24,43,45,46,49,55,57,[69][70][71][72][73][74][75][76].…”

“…In terms of semantic ambiguity, imprecise scope determination [41,45,53,72], inaccurate goals decomposition [43,55,57,73,74], and misinterpretations [69][70][71]75] have been investigated as consistency obstacles. For imprecise scope determination, inconsistency problems show up as discrepancies or missing user stories when user stories are derived from goal models [53,72] or as incompatible specifications of systems [41,45] caused by minimal visual documentation [41,45,53,72].…”