Example Reflection – Storytelling 

 Challenge 

 I work for a software development company which has implemented an agile 

 methodology for development . Sometimes I am the product owner and I need to communicate to the scrum team which are the goals and objectives of app or piece of software we have to develop for the customer . Most of the times are apps which have two flavors , the customer and the provider side . On every scrum sprint I need to transmit the big picture to the team , the expected outcomes for the users , the calls to action , expectations . 

 Selection 

 I have found story telling through user stories to be the best way to transmit to the 

 team what the customer wants and how the users will use the app , how they will be feeling about it and which needs/ issues the app will solve for them . Specially important is why they need the app . 

 Application 

 First is to define the project area creating a positioning statement which should include 

 who will use the app and the need the app will help to fulfill and how the app is different from other apps . Then the “ personas”are identified and a detailed persona profile is 

 written . This profile needs to detail the tell story of the individual , who is , what he / she does when facing a situation the app will solve . What he / she thinks , sees , feels , does . 

 Then some scenarios are created with current alternatives and a value proposition the 

 app will give . 

 With this a user story which flows out from the persona is created for the first sprint 

 and storyboards are created . 

 And for following sessions child stories derived form this user story are created to 

 continue the app development . 

 Insight 

 With user stories the scrum team identifies the objectives of the project , and they feel 

 engaged as they understand the needs , and feelings of the persons who will be using the app . It really generates an impact on the team and also the customer . When the customer is invited to the meetings and hear and sees the stories , feel pretty confident the project is in good hands . 

 Approach 

 Right now we are only using storyboards to tell the stories . It will be nice to start testing 

 with some videos where the scrum team will be the actors of the stories . In that way the will internalize in a better way the feelings and needs of the users . 


EMAIL: 
ID_NUM: 
NAME_STUDENT: 
PHONE_NUM: 
STREET_ADDRESS: 
URL_PERSONAL: 
USERNAME: 

### Task: You are a PII (Personal Identity Information) Detection. Given a essays written by students, you have to identify ONLY the following:
NAME_STUDENT - The full or partial name of a student that is not necessarily the author of the essay. This excludes instructors, authors, and other person names.
EMAIL - A student’s email address.
USERNAME - A student's username on any platform.
ID_NUM - A number or sequence of characters that could be used to identify a student, such as a student ID or a social security number.
PHONE_NUM - A phone number associated with a student.
URL_PERSONAL - A URL that might be used to identify a student.
STREET_ADDRESS - A full or partial street address that is associated with the student, such as their home address.
### Input: Example Reflection – Storytelling 

 Challenge 

 I work for a software development company which has implemented an agile 

 methodology for development . Sometimes I am the product owner and I need to communicate to the scrum team which are the goals and objectives of app or piece of software we have to develop for the customer . Most of the times are apps which have two flavors , the customer and the provider side . On every scrum sprint I need to transmit the big picture to the team , the expected outcomes for the users , the calls to action , expectations . 

 Selection 

 I have found story telling through user stories to be the best way to transmit to the 

 team what the customer wants and how the users will use the app , how they will be feeling about it and which needs/ issues the app will solve for them . Specially important is why they need the app . 

 Application 

 First is to define the project area creating a positioning statement which should include 

 who will use the app and the need the app will help to fulfill and how the app is different from other apps . Then the “ personas”are identified and a detailed persona profile is 

 written . This profile needs to detail the tell story of the individual , who is , what he / she does when facing a situation the app will solve . What he / she thinks , sees , feels , does . 

 Then some scenarios are created with current alternatives and a value proposition the 

 app will give . 

 With this a user story which flows out from the persona is created for the first sprint 

 and storyboards are created . 

 And for following sessions child stories derived form this user story are created to 

 continue the app development . 

 Insight 

 With user stories the scrum team identifies the objectives of the project , and they feel 

 engaged as they understand the needs , and feelings of the persons who will be using the app . It really generates an impact on the team and also the customer . When the customer is invited to the meetings and hear and sees the stories , feel pretty confident the project is in good hands . 

 Approach 

 Right now we are only using storyboards to tell the stories . It will be nice to start testing 

 with some videos where the scrum team will be the actors of the stories . In that way the will internalize in a better way the feelings and needs of the users .
### Output: 