Learning Launch 

 Challenge     I am a member of my organization ’s on line advertising and marketing branch and my / our   project is to enhance the workflow ( sports and projects ) in the branch so that it will boom income   withinside the on line channel and to spend advertising and marketing budgets at the proper   campaigns . The venture scope consists of the web advertising and marketing branch composed   of ten employees , in addition to the bigger advertising and marketing branch and IT branch , with   whom we paintings closely . The venture is constrained to inner resources ( i.e. , finances and   worker time ) . The venture need to now no longer exceed 30 enterprise days and the answer need   to encompass a good distribution of running hours among the group members . We will   awareness on looking to find what our group members , in addition to key stakeholders in the   large advertising and marketing branch and IT branch , do not forget to be useless or difficult   with reference to the workflow .     Selection     Our group has already long past via numerous layout wondering sports / equipment , so we ’re   geared up to strive the gaining knowledge of release tool . Broadly speaking , the gaining   knowledge of release is an test intended to fast check an concept and prototype .     Application     For our first gaining knowledge of release , we centered at the shape / execution of our on line   advertising and marketing obligations . In particular , we desired to peer if we may want to shape   our obligations , projects , and tactics to evolve the strategies of Scrum venture control for our   paintings ( e.g. , time boxed , daily , unique meetings , reviews , etc . ) for you to come to be greater   agile . This examined our assumption that the shape and execution had been the principle reasons   of our workflow project . Our group went via a -day education with a Scrum venture control   coach . Next , we went via 5 workshops to shape our obligations and tactics in a greater agile way .   These periods befell inside in a three - week timeframe . We anticipated to provide a file with a   clean description of our new , greater agile tactics / workflow .   For our 2nd gaining knowledge of release , we centered on gaining readability approximately our   obligations and priorities . This examined our assumption that our prioritization of obligations   changed into the principle motive of our workflow project . Our group finished an nameless   survey . Additionally , 5 key stakeholders from the bigger advertising and marketing branch and   IT branch additionally finished an nameless survey . The surveys covered questions on our new ,   proposed manner , know - how the manner and the prioritization of obligations , and emotions   approximately the change , and had been carried out inside a one - week timeframe . 

 Insight     By making use of the gaining knowledge of release tool , our group diagnosed our assumptions   and designed launches to check those assumptions . Additionally , we idea via predicted   consequences , waiting for to discover that a greater agile technique might enhance our workflow ,   and that each our group and the important thing stakeholders might be pretty open to the brand   new prioritization of obligations and manner . Our real consequences had been barely exceptional   from what we predicted : even as our group changed into open to the prioritization of obligations   and manner , the important thing stakeholders withinside the large advertising and marketing   branch and IT branch expressed a few concerns . Moving forward , our group will evaluate this   perception and include it into destiny release designs . The ongoing incorporation of perception is   specifically critical at this degree , as launches come earlier than a complete rollout withinside the   layout wondering timeline .     Approach     Given that our group has already long past via numerous layout wondering sports / equipment and   are at this degree withinside the timeline , the gaining knowledge of release is the precise tool . As   formerly mentioned , our group desires to check the perception received from our first launches   and include this perception into destiny release designs . Future release designs need to replicate   perception received , development made , and are available towards a compelling answer geared   up for complete 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: Learning Launch 

 Challenge     I am a member of my organization ’s on line advertising and marketing branch and my / our   project is to enhance the workflow ( sports and projects ) in the branch so that it will boom income   withinside the on line channel and to spend advertising and marketing budgets at the proper   campaigns . The venture scope consists of the web advertising and marketing branch composed   of ten employees , in addition to the bigger advertising and marketing branch and IT branch , with   whom we paintings closely . The venture is constrained to inner resources ( i.e. , finances and   worker time ) . The venture need to now no longer exceed 30 enterprise days and the answer need   to encompass a good distribution of running hours among the group members . We will   awareness on looking to find what our group members , in addition to key stakeholders in the   large advertising and marketing branch and IT branch , do not forget to be useless or difficult   with reference to the workflow .     Selection     Our group has already long past via numerous layout wondering sports / equipment , so we ’re   geared up to strive the gaining knowledge of release tool . Broadly speaking , the gaining   knowledge of release is an test intended to fast check an concept and prototype .     Application     For our first gaining knowledge of release , we centered at the shape / execution of our on line   advertising and marketing obligations . In particular , we desired to peer if we may want to shape   our obligations , projects , and tactics to evolve the strategies of Scrum venture control for our   paintings ( e.g. , time boxed , daily , unique meetings , reviews , etc . ) for you to come to be greater   agile . This examined our assumption that the shape and execution had been the principle reasons   of our workflow project . Our group went via a -day education with a Scrum venture control   coach . Next , we went via 5 workshops to shape our obligations and tactics in a greater agile way .   These periods befell inside in a three - week timeframe . We anticipated to provide a file with a   clean description of our new , greater agile tactics / workflow .   For our 2nd gaining knowledge of release , we centered on gaining readability approximately our   obligations and priorities . This examined our assumption that our prioritization of obligations   changed into the principle motive of our workflow project . Our group finished an nameless   survey . Additionally , 5 key stakeholders from the bigger advertising and marketing branch and   IT branch additionally finished an nameless survey . The surveys covered questions on our new ,   proposed manner , know - how the manner and the prioritization of obligations , and emotions   approximately the change , and had been carried out inside a one - week timeframe . 

 Insight     By making use of the gaining knowledge of release tool , our group diagnosed our assumptions   and designed launches to check those assumptions . Additionally , we idea via predicted   consequences , waiting for to discover that a greater agile technique might enhance our workflow ,   and that each our group and the important thing stakeholders might be pretty open to the brand   new prioritization of obligations and manner . Our real consequences had been barely exceptional   from what we predicted : even as our group changed into open to the prioritization of obligations   and manner , the important thing stakeholders withinside the large advertising and marketing   branch and IT branch expressed a few concerns . Moving forward , our group will evaluate this   perception and include it into destiny release designs . The ongoing incorporation of perception is   specifically critical at this degree , as launches come earlier than a complete rollout withinside the   layout wondering timeline .     Approach     Given that our group has already long past via numerous layout wondering sports / equipment and   are at this degree withinside the timeline , the gaining knowledge of release is the precise tool . As   formerly mentioned , our group desires to check the perception received from our first launches   and include this perception into destiny release designs . Future release designs need to replicate   perception received , development made , and are available towards a compelling answer geared   up for complete rollout .
### Output: 