Skip to main content
. 2021 Sep 20;21(18):6298. doi: 10.3390/s21186298

Table A4.

Detailed integration method proposed by each selected primary study.

Study Agile Process Activity Way of Integration Integration Level Integration Steps
[27] XP Requirements Analysis
Planification and Design		 Extreme Personas Detailed

  1. Start as the classic persona model.

  2. When the knowledge is updated, refactor the persona, or even create new ones if necessary.
[31] XP Requirements Analysis
Planification and Design		 Mobile-D (Extreme Personas) Detailed

  1. Exploration phase: research and modeling.

  2. Design: Requirements and framework definition.

  3. Development and testing: requirements refinement and prototyping.
[32] XP Requirements Analysis Extreme Personas Detailed

  1. Contextual research.

  2. Consolidation in Personas.

  3. Interview with users to evaluate satisfaction with the prototype.
[33] XP Requirements Analysis
Planification and Design		 Alan Cooper on XP + contextual design Detailed

  1. Ethnographic research.

  2. Asynchronous research to gather info on specific characteristics without affecting the speed of the project.

  3. Validating personas with end-users.

  4. Monitoring of developers to confirm that they use personas.
[39] Scrum Requirements Analysis Minimal personas, persona stories Detailed

  1. Short description and motivation for each persona.

  2. One page per persona: one side for utilities and preferences and one side for likes and personality.

  3. Persona stories: how a particular persona (not the specific users) does the task.
[40] XP Requirements Analysis Lightweight Personas Detailed

  1. Contextual research.

  2. Creates personas based on initial studies.

  3. Refactor when the study suggests changes in requirements.
[48] DSDM Requirements Analysis Sketch and user interview Generic
[49] DSDM Requirements Analysis User-centered creative thinking, priority specification during prototyping Detailed

  1. Design-thinking session for user story analysis.

  2. Requirement specification activity.

  3. Interview with users for validation.
[50] DSDM Requirements Analysis
Planification and Design		 Architecturally Significant Persona Detailed

  1. Analyze user stories.

  2. Create personas and assign them user stories.

  3. Elaborate solution design and validate with users.
[51] Scrum Planification and Design Creative session between requisite analysis and planification Detailed

  1. Brainstorming session for the creation of user stories.

  2. Grouping similar ideas in one persona.
[52] Scrum Requirements Analysis
Planification and Design		 AgileRE Tool Detailed

  1. Template to create persona with auto-complete sentences.

  2. Create epics and user stories.

  3. When the user is satisfied, mark the story as solved.
[53] Scrum Requirements Analysis Creative session with students Generic
[54] Scrum Requirements Analysis Nielsen heuristics Detailed

  1. Select artifacts and hypotheses of relevant personas.

  2. Associate tasks to each persona.
[55] Scrum Requirements Analysis Mental maps to connect Personas Generic
[56] Scrum Requirements Analysis 4 steps to create personas with physical or mental limitations Detailed

  1. Introduction of user requirements iteratively.

  2. Contextualization of the persona, design of the target group.

  3. Concretization.

  4. Development based on user stories.

  5. Feedback: evaluation, improvement, testing.
[57] Scrum Requirements Analysis User XStories Generic
[58] Scrum Project Definition Study based on personas along the project definition Generic
[59] Scrum Requirements Analysis User objectives on incremental iterations Detailed

  1. Specification of requirements at the interface and navigation level.

  2. Presentation of the user objectives from one or several functional and non-functional requirements each, to obtain high fidelity prototypes.

  3. Validation of the functionality of the user objectives with the Personas technique.
[60] FDD Requirements Analysis
Planification and Design		 Combination of Personas and use cases Detailed

  1. Combine use case actors with subjects in personas.

  2. Use information from personas in S-BPM interaction diagrams: sub-stories of subjects for behavioral models.

  3. Refine user stories by abstracting patterns and assigning these small sub-stories to concrete subjects.
[61] FSS Requirements Analysis Light personas—MEX boards Generic
[62] FDD Requirements Analysis
Planification and Design		 Questionnaire to patientsInterviews with emotional analysis experts Generic
[63] Lean Problem Definition Questionnaire during the problem definition Detailed

  1. Questionnaire to determine the user groups.
[64] Lean Requirements Analysis Proto-Persona method Detailed

  1. Development of the persona.

  2. Knowing the users.

  3. Refining the persona.
[65] Lean Requirements Analysis
Planification and Design		 User clusterization according to behaviors and preferences Detailed

  1. Contextual research with interviews.

  2. Grouping the results into clusters of Personas based on preferences and behaviors.

  3. Design for the patterns found in each cluster.
[66] XP Requirements Analysis
Planification and Design		 Design Thinking Detailed

  1. Integrate user stories with persona-based design: empathize with the user and define an action to the problem based on it.

  2. Multidisciplinary team for collaboration and creativity.

  3. Prototype development.

  4. UCD and user acceptance.

  5. Usability testing during agile development by the user.
[67] XP Requirements Analysis Persona story context metamodel Detailed

  1. Create the context of each persona.

  2. Describe the interaction between several personas in order to reduce the processing time of each use case.

  3. Represent the interaction between personas in a class diagram.
[68] XP Requirements Analysis
Refinement phase (changes among iterations)		 Extreme Personas Detailed

  1. Personas are modeled based on the preliminary user groups.

  2. Personas are refactored each time new information appears suggesting changes.

  3. Creation of new personas if the current ones do not meet the new needs.
[69] XP Requirements Analysis Human story as a combination of User Story and Persona Story Detailed

  1. Give the persona a name.

  2. Mind map design to connect what the persona wants and how they want it. Use colors to highlight what is important.

  3. Understand the user before developing for them. Importance of story writing.

  4. Evaluate the result with agile requirements quality checklists.