Introduction- 

 I worked as lead position in software development , and I need to create stories and different scenarios   for application development ( using Agile methodology ) , so that the business understanding and   development will be easy for developer . For that purpose we used JIRA for project handling , which   support us to tell the business how we are going to implement our client business cases . 

 A key component of agile software development is putting people first , and user - stories put actual end   users at the center of the conversation . Stories use non - technical language to provide context for the   development team and their efforts . After reading a user story , the team knows why they are building   what they 're building and what value it creates . 

 User stories are one of the core components of an agile program . They help provide a user - focused   framework for daily work — which drives collaboration , creativity , and a better product overall . A user   story is the smallest unit of work in an agile framework . It ’s an end goal , not a feature , expressed from   the software user ’s perspective . I preferred JIRA because it 's not only support me to create user stories   even I can manage task and process execution and how much progress in done on daily basis . 

 We can add members in project and assign task to them with time line , and on daily basis we can get   update . 

 For Example- I have a use case to login in application . For that I can easily write user stories after   discussing with client and write down all defend kind of scenarios of login like success , failure , network   or any other issues during login . 

 User stories describe the why and the behind the day - to - day work of development team members ,   often expressed as persona , need , purpose . Understanding their role as the source of truth for what   your team is delivering , but also why , is key to a smooth process . 

 Start by evaluating the next , or most pressing , large project ( e.g. an epic ) . Break it down into smaller   user stories , and work with the development team for refinement . Once your stories are out in the wild   where the whole team can see them , you ’re ready to get to work . Overall Jira support and fulfill all my   requirement to handle project smoothly . 


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: Introduction- 

 I worked as lead position in software development , and I need to create stories and different scenarios   for application development ( using Agile methodology ) , so that the business understanding and   development will be easy for developer . For that purpose we used JIRA for project handling , which   support us to tell the business how we are going to implement our client business cases . 

 A key component of agile software development is putting people first , and user - stories put actual end   users at the center of the conversation . Stories use non - technical language to provide context for the   development team and their efforts . After reading a user story , the team knows why they are building   what they 're building and what value it creates . 

 User stories are one of the core components of an agile program . They help provide a user - focused   framework for daily work — which drives collaboration , creativity , and a better product overall . A user   story is the smallest unit of work in an agile framework . It ’s an end goal , not a feature , expressed from   the software user ’s perspective . I preferred JIRA because it 's not only support me to create user stories   even I can manage task and process execution and how much progress in done on daily basis . 

 We can add members in project and assign task to them with time line , and on daily basis we can get   update . 

 For Example- I have a use case to login in application . For that I can easily write user stories after   discussing with client and write down all defend kind of scenarios of login like success , failure , network   or any other issues during login . 

 User stories describe the why and the behind the day - to - day work of development team members ,   often expressed as persona , need , purpose . Understanding their role as the source of truth for what   your team is delivering , but also why , is key to a smooth process . 

 Start by evaluating the next , or most pressing , large project ( e.g. an epic ) . Break it down into smaller   user stories , and work with the development team for refinement . Once your stories are out in the wild   where the whole team can see them , you ’re ready to get to work . Overall Jira support and fulfill all my   requirement to handle project smoothly .
### Output: 