Easyblood System – Learning Launch 

 Challenge 

 I am a college student and I use to observe various problems surrounding me . Once upon a   time , I noticed that there are so many people around us who need blood on daily basis as well   as in emergencies . Patients of thalassemia need blood on daily basis , people whose kidneys   are not working properly they need blood in dialysis . Moreover , in accidents there are heavy   blood loss sometime , in that critical moment blood is required on specific time period . As I   am Computer Science student , I want to develop a technical solution which can be useful and   also help me in building my technical skills . So I told this problem to my friends and they all   agreed . Hence , I was able to create a team of my own age filled with enthusiasm . Hence , we   decided to create Mobile and Web application for EasyBlood .       Selection     Our team has already gone through several design thinking activities / tools , so we are ready   to try the learning launch tool . Broadly speaking , the learning launch is an experiment meant   to quickly test an idea and prototype .       Application      For our first learning launch , we focused on the structure / execution of our online Blood bank   management system . In particular , we wanted to build a platform where all the users can get   the details about the blood available in blood banks near to them and find nearest blood bank   and donor for specific blood group . The desired application will be mobile application through   which users can get details about blood they require .     This tested our assumption that the structure and execution were the main causes of our   workflow challenge . We went through various blood bank management system to collect   information about how to arrange data . Next , we went through five workshops to structure   our tasks and processes in a more agile way . These two sessions occurred within in a three- week timeframe . We expected to produce a document with a clear description of our new ,   more agile processes / workflow . For our second learning launch , we focused on gaining clarity   about our tasks and priorities . This tested our assumption that our prioritization of tasks was   the main cause of our workflow challenge . We also did survey on blood bank staff and normal   people . The surveys included questions about whether they would like to share the details   about their blood and blood available in blood banks . 

 Insight      By applying the learning launch tool , we identified our assumptions and designed launches to   test these assumptions . Additionally , we thought through anticipated results , expecting to   find that a more agile approach would improve our workflow and open to the new   prioritization of tasks or process . But everything came out as we expected .   We were only   concerned about that if user find it safe and easy to use the application and it helps in getting   blood easily and quickly . We did survey about this , it turned out with excellent response .       Approach      Given that our team has already gone through several design thinking activities / tools and are   at this stage in the timeline , the learning launch is the appropriate tool . As previously   mentioned , our team needs to review the insight gained from our first two launches and   incorporate this insight into future launch designs . Future launch designs should reflect   insight gained , progress made , and come closer to a compelling solution ready for full rollout .   Our college is also happy with our efforts and mobile application . 


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: Easyblood System – Learning Launch 

 Challenge 

 I am a college student and I use to observe various problems surrounding me . Once upon a   time , I noticed that there are so many people around us who need blood on daily basis as well   as in emergencies . Patients of thalassemia need blood on daily basis , people whose kidneys   are not working properly they need blood in dialysis . Moreover , in accidents there are heavy   blood loss sometime , in that critical moment blood is required on specific time period . As I   am Computer Science student , I want to develop a technical solution which can be useful and   also help me in building my technical skills . So I told this problem to my friends and they all   agreed . Hence , I was able to create a team of my own age filled with enthusiasm . Hence , we   decided to create Mobile and Web application for EasyBlood .       Selection     Our team has already gone through several design thinking activities / tools , so we are ready   to try the learning launch tool . Broadly speaking , the learning launch is an experiment meant   to quickly test an idea and prototype .       Application      For our first learning launch , we focused on the structure / execution of our online Blood bank   management system . In particular , we wanted to build a platform where all the users can get   the details about the blood available in blood banks near to them and find nearest blood bank   and donor for specific blood group . The desired application will be mobile application through   which users can get details about blood they require .     This tested our assumption that the structure and execution were the main causes of our   workflow challenge . We went through various blood bank management system to collect   information about how to arrange data . Next , we went through five workshops to structure   our tasks and processes in a more agile way . These two sessions occurred within in a three- week timeframe . We expected to produce a document with a clear description of our new ,   more agile processes / workflow . For our second learning launch , we focused on gaining clarity   about our tasks and priorities . This tested our assumption that our prioritization of tasks was   the main cause of our workflow challenge . We also did survey on blood bank staff and normal   people . The surveys included questions about whether they would like to share the details   about their blood and blood available in blood banks . 

 Insight      By applying the learning launch tool , we identified our assumptions and designed launches to   test these assumptions . Additionally , we thought through anticipated results , expecting to   find that a more agile approach would improve our workflow and open to the new   prioritization of tasks or process . But everything came out as we expected .   We were only   concerned about that if user find it safe and easy to use the application and it helps in getting   blood easily and quickly . We did survey about this , it turned out with excellent response .       Approach      Given that our team has already gone through several design thinking activities / tools and are   at this stage in the timeline , the learning launch is the appropriate tool . As previously   mentioned , our team needs to review the insight gained from our first two launches and   incorporate this insight into future launch designs . Future launch designs should reflect   insight gained , progress made , and come closer to a compelling solution ready for full rollout .   Our college is also happy with our efforts and mobile application .
### Output: 