Reflection – Visualization 

 Challenge & Selection 

 I am working as a program manager in my organization , responsible for managing   data analytics program with multiple sub - projects running under the same . In one of   the major programs , there are multiple teams in different time - zones responsible for   the delivery outcome as release at definite interval of time . The teams use Scrum   framework as execution model and required to integrate after the development   activities . While managing the program , I saw one of the challenges to bring the   holistic picture of the entire release plan with clear accountabilities . I am always   convinced with the power of visualisation in both personal and professional areas . I   thought of applying the powerful technique of visualisation to overcome this   problem and to help my teams delivering with better efficiencies . The entire   information containing the scope , boundaries , relevant timelines , point of   integration , key stakeholders is visible and transparent to everyone in the team   which brought in absolute clarity to tasks , critical path and accountabilities . This used   to captured earlier in old waterfall approach as detailed project plans but missing for   detailed set of requirements in sprints , releases etc . 

 Application 

 I started capturing all the relevant information based on the needs and expectations   of different teams and stakeholders involved . With the help of directions , efforts and   estimates I tried to bring in a clear and concise view with all relevant information ,   with focus on not having over information . As a inspect and adapt mechanism , I   shared a draft view with all stakeholders to gather their inputs and make it valuable   with the right information for each set of stakeholders . I prepared a specific   questionnaire to gather the right kind of information with custom questions : 

 1 . What key information(s ) is missing in the plan ?   2 . Is this plan able to meet all the requirements that you are looking for ?   3 . Is this plan providing you a clear and concise view ? Etc .. 

 Once the inputs are gathered , I revised and enhanced it before applying it . During   one of the discussion forums , I briefed the stakeholders with the purpose of the plan   and how to use it . I later on applied the same technique to approach different   problems during the retrospection . A brief summary for a different set of   stakeholders was added to make the information more meaningful . I worked   through different versions to make it more intuitive to reflect the risks areas ,   important milestones etc . 

 Insight & Approach 

 Well , I got a very positive feedback on the visualisation of all the different phases and details   captured in the plan . The queries on the basic information reduced and most importantly   every details is visible and transparent to anyone both internal – Development Teams ,   Product , Sales , Marketing , in the organisation and external - the Customer . The technique   has given the diverse group of stakeholders a focal point for discussion that allows them to   share their perspectives and develop insights into potential root causes of their problem –   not having a consolidated / clear view .   This course has been an eyeopener to me to focus on   the purpose and how systematically I can proceed with engagement and collaboration to   address the concern . 


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: Reflection – Visualization 

 Challenge & Selection 

 I am working as a program manager in my organization , responsible for managing   data analytics program with multiple sub - projects running under the same . In one of   the major programs , there are multiple teams in different time - zones responsible for   the delivery outcome as release at definite interval of time . The teams use Scrum   framework as execution model and required to integrate after the development   activities . While managing the program , I saw one of the challenges to bring the   holistic picture of the entire release plan with clear accountabilities . I am always   convinced with the power of visualisation in both personal and professional areas . I   thought of applying the powerful technique of visualisation to overcome this   problem and to help my teams delivering with better efficiencies . The entire   information containing the scope , boundaries , relevant timelines , point of   integration , key stakeholders is visible and transparent to everyone in the team   which brought in absolute clarity to tasks , critical path and accountabilities . This used   to captured earlier in old waterfall approach as detailed project plans but missing for   detailed set of requirements in sprints , releases etc . 

 Application 

 I started capturing all the relevant information based on the needs and expectations   of different teams and stakeholders involved . With the help of directions , efforts and   estimates I tried to bring in a clear and concise view with all relevant information ,   with focus on not having over information . As a inspect and adapt mechanism , I   shared a draft view with all stakeholders to gather their inputs and make it valuable   with the right information for each set of stakeholders . I prepared a specific   questionnaire to gather the right kind of information with custom questions : 

 1 . What key information(s ) is missing in the plan ?   2 . Is this plan able to meet all the requirements that you are looking for ?   3 . Is this plan providing you a clear and concise view ? Etc .. 

 Once the inputs are gathered , I revised and enhanced it before applying it . During   one of the discussion forums , I briefed the stakeholders with the purpose of the plan   and how to use it . I later on applied the same technique to approach different   problems during the retrospection . A brief summary for a different set of   stakeholders was added to make the information more meaningful . I worked   through different versions to make it more intuitive to reflect the risks areas ,   important milestones etc . 

 Insight & Approach 

 Well , I got a very positive feedback on the visualisation of all the different phases and details   captured in the plan . The queries on the basic information reduced and most importantly   every details is visible and transparent to anyone both internal – Development Teams ,   Product , Sales , Marketing , in the organisation and external - the Customer . The technique   has given the diverse group of stakeholders a focal point for discussion that allows them to   share their perspectives and develop insights into potential root causes of their problem –   not having a consolidated / clear view .   This course has been an eyeopener to me to focus on   the purpose and how systematically I can proceed with engagement and collaboration to   address the concern .
### Output: 