Stream Management Project 

 CHALLENGE : 

 I 'm a member of my organisation quality control département and our Challenge is to improve the   workflow with the best asset quality control ( quality and process projects ) within the département   in ordre to increase the quality of product , consumer protection and marketing survey ; and to spend   à budget on the right copains , learning and costumes journées . The project scope includes the   régional représentation of central département , the département itself and IT département with   whom we work closely . The project is limited to internal resources ( i.e , budget and employee time ) . 

 The project , should not , exceed 60 business dans and should include an even distribution of working 

 Hors amongst the team members . 

 We will fous on trying to uncover our team members as well as the head of the département and the   IT département senior office , called or consider to be ineffective or problematic with regard to the   workflow dependently to quality of product and service throughout the customer Journey . 

 SELECTION : 

 1 to 2 member of our team have already gone through one or several design thinking activités and/or   tools , so we are ready to try the learning lunch tool ( because   two members are trying it ) . 

 Globaly speaking , this tool is experimented as tool meant fait and cheap to test an idéal and   prototype . 

 APPLICATION : 

 For our first learning launch , we focus on the structure / exécution for our control quality product , our   protection of consumer and our market survey Journey . 

 By this learning launch , we wanted to structure our tasks , projects and processes . 

 To adapt the stream project management ( application created by IT Department ) . 

 For our work ( e.g time to délivrance of assessment conformité certificate , quantity and value of non- conform product , classification of controlled product , spécific meeting , list of controlled product ,   etc … . ) . 

 To a new way more scalable and more agile : agile@scale . 

 This tested our assumption that the structure and exécution were the main cause , of our workflow   with quality Challenge . 

 Our team went through a seven - day training with stream project management coach wich include   control process , end to end customer Journey ( for consumer protection to market Survey process in   one hand , in the other hand how to manage data of this processes . 

 Next , we move to 3 workshops to structure our tasks and processes in agile@scale wich include : 

 -   How to do control in the field due to the new application ( stream Management project ) . 

 -   How to do networking with other intra - inter organisations and exchanging the informations   and Data . 

 The timeframe of those workshops must be 4 weeks ; and in the end we expected a clear   statement of the new agile@scale processes / workflow .     In the second phase , we have to prioritize ; that 's why we have to have a learning launch   about prioritization in relation with tasks . This tested our assumption that our prioritization   of tasks was the main cause of our workflow Challenge .     Insight   By applying the learning launch tool , our team identified our assumptions and designed   launches to test these assumptions .   Additionally , we thought through anticipated résultats , expertise to find agile@scale   approche that would improve our workflow . Our team would be fairly open to the new   prioritization of tasks and process , and incorporation it into future launch designs before the   full rollout in the design thinking timeline .     Approach     Future launch designs should reflect insight gained , progress made , and come closer to   compelling solution ready for full rollout . 


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: Stream Management Project 

 CHALLENGE : 

 I 'm a member of my organisation quality control département and our Challenge is to improve the   workflow with the best asset quality control ( quality and process projects ) within the département   in ordre to increase the quality of product , consumer protection and marketing survey ; and to spend   à budget on the right copains , learning and costumes journées . The project scope includes the   régional représentation of central département , the département itself and IT département with   whom we work closely . The project is limited to internal resources ( i.e , budget and employee time ) . 

 The project , should not , exceed 60 business dans and should include an even distribution of working 

 Hors amongst the team members . 

 We will fous on trying to uncover our team members as well as the head of the département and the   IT département senior office , called or consider to be ineffective or problematic with regard to the   workflow dependently to quality of product and service throughout the customer Journey . 

 SELECTION : 

 1 to 2 member of our team have already gone through one or several design thinking activités and/or   tools , so we are ready to try the learning lunch tool ( because   two members are trying it ) . 

 Globaly speaking , this tool is experimented as tool meant fait and cheap to test an idéal and   prototype . 

 APPLICATION : 

 For our first learning launch , we focus on the structure / exécution for our control quality product , our   protection of consumer and our market survey Journey . 

 By this learning launch , we wanted to structure our tasks , projects and processes . 

 To adapt the stream project management ( application created by IT Department ) . 

 For our work ( e.g time to délivrance of assessment conformité certificate , quantity and value of non- conform product , classification of controlled product , spécific meeting , list of controlled product ,   etc … . ) . 

 To a new way more scalable and more agile : agile@scale . 

 This tested our assumption that the structure and exécution were the main cause , of our workflow   with quality Challenge . 

 Our team went through a seven - day training with stream project management coach wich include   control process , end to end customer Journey ( for consumer protection to market Survey process in   one hand , in the other hand how to manage data of this processes . 

 Next , we move to 3 workshops to structure our tasks and processes in agile@scale wich include : 

 -   How to do control in the field due to the new application ( stream Management project ) . 

 -   How to do networking with other intra - inter organisations and exchanging the informations   and Data . 

 The timeframe of those workshops must be 4 weeks ; and in the end we expected a clear   statement of the new agile@scale processes / workflow .     In the second phase , we have to prioritize ; that 's why we have to have a learning launch   about prioritization in relation with tasks . This tested our assumption that our prioritization   of tasks was the main cause of our workflow Challenge .     Insight   By applying the learning launch tool , our team identified our assumptions and designed   launches to test these assumptions .   Additionally , we thought through anticipated résultats , expertise to find agile@scale   approche that would improve our workflow . Our team would be fairly open to the new   prioritization of tasks and process , and incorporation it into future launch designs before the   full rollout in the design thinking timeline .     Approach     Future launch designs should reflect insight gained , progress made , and come closer to   compelling solution ready for full rollout .
### Output: 