check file
Stakeholder Analysis Rubric ABCDFPoints Assigned Demonstration of conceptual understanding● All impacted stakeholders are correctly identified ● All impacted stakeholders have been assigned the correct stakeholder category and corresponding P/I Designation ● 90-100% RACI assignments are correctly identified ● All stakeholder categories are listed in communication plan ● All required information, frequency, and medium of communication plan aligns appropriately to the corresponding stakeholder category ● All information from previous project documents are accurately transposed to the Stakeholder Analysis Matrix ● All key stakeholder requirements for each stakeholder in the stakeholder analysis matrix supports the project objectives and are appropropriately aligned to the relevant stakeholder ● Score: 64-80 points● Most impacted stakeholders are correctly identified ● Most impacted stakeholders have been assigned the correct stakeholder category and corresponding P/I Designation ● 80-89%RACI assignments are correctly identified ● Most stakeholder categories are listed in communication plan ● Most required information, frequency, and medium of communication plan aligns appropriately to the corresponding stakeholder category ● Most information from previous project documents are accurately transposed to the Stakeholder Analysis Matrix ● Most stakeholder requirements for each stakeholder in the stakeholder analysis matrix supports the project objectives and are appropropriately aligned to the relevant stakeholder ● Score: 56-63 points● Some impacted stakeholders are correctly identified ● Some impacted stakeholders have been assigned the correct stakeholder category and corresponding P/I Designation ● 70-79% of RACI assignments are correctly identified ● Some stakeholder categories are listed in communication plan ● Some required information, frequency, and medium of communication plan aligns appropriately to the corresponding stakeholder category ● Some information from previous project documents are accurately transposed to the Stakeholder Analysis Matrix ● Some stakeholder requirements for each stakeholder in the stakeholder analysis matrix supports the project objectives and are appropropriately aligned to the relevant stakeholder ●Score: 48-55 points● Most impacted stakeholders are NOT correctly identified ● Most impacted stakeholders have NOT been assigned the correct stakeholder category and corresponding P/I Designation ● 50-69% of RACI assignments are correctly identified ● Most stakeholder categories are NOT listed in communication plan ● Most required information, frequency, and medium of communication plan does NOT align appropriately to the corresponding stakeholder category ● Most information from previous project documents are NOT accurately transposed to the Stakeholder Analysis Matrix ● Most stakeholder requirements for each stakeholder in the stakeholder analysis matrix does NOT support the project objectives and are NOT appropropriately aligned to the relevant stakeholder ● Score: 40-47 points● Few or no impacted stakeholders are correctly identified ● Few or no impacted stakeholders have been assigned the correct stakeholder category and corresponding P/I Designation ● Less than half of the RACI assignments are correctly identified ● Few or no stakeholder categories are listed in communication plan ● Few or none of the required information, frequency, and medium of communication plan aligns appropriately to the corresponding stakeholder category ● Few or no information from previous project documents are accurately transposed to the Stakeholder Analysis Matrix ● Few or no stakeholder requirements for each stakeholder in the stakeholder analysis matrix supports the project objectives and are appropropriately aligned to the relevant stakeholder ●Score: <40 points/80 quality of work● writing is concise and clear. written in business appropriate language. minor to no errors in grammar and spelling ●score: 16-20 points● writing is clear and mostly concise. mostly written in business appropriate language. few grammar and spelling errors ●score: 13-15 points● writing is somewhat unclear and/or not concise. mostly written in non-business appropriate language. several grammar and spelling errors ●score: 12-14 points● writing is mostly unclear and/or not concise. mostly written in colloquial language. many grammar and spelling errors ●score: 10-11 points● writing is incomprehensible or non-existant. most of the writing has grammatical and spelling errors ●score: 0-10 points/20 total stakeholder analysis assignment – worth 20% of final grade new concrete products containing recycled glass with adl process inc. (https://www.georgebrown.ca/about/office-of-research-innovation/research-facilities/green-projects) note: detail of project progress has been modified here for educational purpose and the names of the individuals are fictional to maintain confidentiality. company and project background adl process, an electronics recycling company in toronto, has been collaborating with george brown college to identify the opportunities and feasibility in recycling cathode ray tubes (crts) into a construction product (e.g. concrete). the project objective was to research concrete formulation, how it would be impacted by the addition of recycled glass and analyze the performance of different concrete formulations containing recycled glass. the research stage will be followed by the limited volume pilot production of modified concrete in adl process’s productions lines to be used for initial certification and marketing purpose of new product in canadian market. after twelve months of applied research and materials engineering characterization, adl process’s r&d team announced that the project was a big success and new developed concrete has all the technical requirements to meet the canadian standard for cementitious materials for use in concrete. considering the current importance of applied research in green construction and sustainable building practices in the canadian construction, this project could become a high-profile project for the ministry of environment and city of toronto. scenario: pilot production of modified concrete adl process’s current lines include certified product destruction and electronics recycling and has a total workforce of 200 staff spread across five departments (refer to appendix a for organization chart). lisa hurley, the adl process’s ceo, convened a meeting with the five department directors to present the plan for the pilot production of modified concrete. this phase of the project is to modify one of the adl’s current productions (recycling) lines to produce required volume of modified concrete. however, in order to keep up with their regular electronics recycling business, adl will need to finish the production within four months and requires the participation and coordination of all five departments. all five department directors pledged their support for this plan and will serve as members of an executive steering committee along with lisa herself. this committee is tasked with identifying and assigning resources to support the project. the adl’s director of financial services has volunteered to champion the project. adl has contracted you as a project manager to plan, manage, and execute this plan. at this stage, the target market includes mid-size concrete producer companies in the greater toronto area. mark stock, environmental manager from gbc will serve as the client. points to consider · adl will need to finish pilot production of modified concrete in four months. this will involve significant staff hires and training · engineering has indicated that it can modify its current production line to produce the proposed products, but requires a different type of machine than it currently uses · health & safety has indicated that the improved health and safety measures are required for employees who are supposed to work in new production line · concrete producers are not typical customers for adl. sales & marketing will need to establish new customer contacts and secure purchase orders stakeholder analysis assignment this assignment is comprised of four parts aimed at evaluating your application of the stakeholder analysis concepts covered in the lectures. utilize the details from the case study, including the organization chart, combined with your own assumptions to complete each of the four parts. this assignment is worth 20% of your final grade. part 1 – stakeholder identification · identify the following 17 stakeholders involved and/or impacted by this project: · client (already provided as an example) · executive steering committee (6 members, indicate all their names and positions) · project sponsor · project manager (you!) · project team (5 staff, indicate all their names and positions) · subject matter expert · external authority · end user · for each stakeholder indicate their name and title (if identified in the case study), the organization they work for, their corresponding stakeholder category (which may be selected from the dropdown list) and p/i designation (e.g. a – high power/high interest) · below is a sample of the expected output: important notes: · adl has hired a consulting firm, smart construction consulting (scc) to assist in choosing the correct machinery required for pilot production of modified concrete. edgar rubio, a senior consultant working with scc, will be assigned to this project · ensure that the project team members have most appropriate skills to help deliver the project but are not committed to management responsibilities on a day-to-day basis. it is expected that the project team members will work 100% of their available time on this project until it is completed. part 2 – responsibility matrix · complete the responsibility matrix for the stakeholders shown. · for each intersecting stakeholder and activity indicate which of the four-letter responsibility designations (r - responsible, a – accountable, c – consulted, i – informed) · pay close attention to the notes in red font in the responsibility matrix tab of the excel document. part 3 – communication plan · enter information for columns b-d for each of the stakeholder groups identified in the ‘communications plan’ tab (column a is already completed) · for the ‘what information they need’ column, indicate what project information each stakeholder needs to be provided in order to successfully undertake their assigned tasks · for the ‘frequency’ column, indicate how often the information needs to be communicated to them (e.g. weekly, daily, etc.) · for the ‘medium’ column, indicate how the information will be conveyed to the stakeholder (e.g. weekly status report, bi-weekly meeting, etc.) · below is a sample of the expected output: part 4 – stakeholder analysis matrix · the stakeholder analysis matrix lists all identified stakeholders for the project · where appropriate copy information from the stakeholder identification and communication plan tables. · refer to the slides for class 4 to complete column e (key stakeholder requirements) – list most important two requirements for each stakeholder · below is a sample of the expected output: submission guidelines 1. capture all work in the stakeholder matrix analysis.xlsx file; do not save as a different file format. 2. complete the cover page with your gbc number, name, and due date. 3. save the file using the following format gbc#_first name_last name_stakeholder analysis matrix analysis (e.g. 1234567_james_smith_stakeholder analysis matrix). 4. upload your completed assignment to blackboard (in the assignments section) by 11:59pm (toronto time) jan 26th, 2023. 5. complete this assignment as if you were providing it to a business client. use professional language. do not use slang or colloquialisms. appendix a: adl process organization chart page 2 of 2 appendix b: power / interest grid power/interest grid b high power/low interest monitor closely a high power/high interest: manage key relationship d low power/low interest low priority c low power/high interest keep informed power interest power/interestgrid b highpower/lowinterest monitorclosely a highpower/highinterest: managekeyrelationship d lowpower/lowinterest lowpriority c lowpower/highinterest keepinformed power interest cover page stakeholder analysis matrix assignment name gbc # 1. stakeholder identification #stakeholder name & titlestakeholder organizationstakeholder categoryp/i designation 1mark stock, environmental manager gbcclienta 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 * note that you may need to scroll within the stakeholder category (column c) drop down list to view and choose all possible entries client senior management/executive steering committee project sponsor project manager project team member employees funder subject matter experts end user external authority wider community 2. responsibility matrix stakeholder category activityclientproject sponsorproject managerproject team member(s)operations / manufacturing staff (adl)human resources staff (adl)sales and marketing staff (adl)information technology staff (adl)end usersubject matter expertexternal authority approve funding for the project secures adl process's resources for the project prepare project plan (includes schedule and budget) hire staff to produce modified concrete upgrade it infrastructure (required for project) retool/install manufacturing equipment purchase raw materials and machinary manufacture modified concrete identify target market (purchasors of the modified concrete) obtain sales contracts with end users prepare and distribute project status reports a - accountable: stakeholder who approves the completion of the task r - responsible: is the person/persons primarily responsible for working on and completing the task c - must be consulted during the delivery of the task i - must be informed about the status of the task note 1: all stakeholders do not necessarily receive an a, r, c or i designation for all tasks (only those with which they are involved) note 2: must be at least one 'r' and one 'a' for each activity note 3: refer closely to the organizational chart in the assignment document for information on where specific functions reside in the organization 3. communication plan stakeholderwhat information they needfrequency (show multiple frequencies if applicable)medium project sponsor- high level cost, schedule, quality performance (project status information) - problems and proposed actions from pm- weekly- written status report - weekly meeting - ad hoc meetings as necessary client executive steering committee (same information for all e.s.c. members) project team members (same information for all project team members subject matter experts external authority end user 4. stakeholder analysis matrix #stakeholder (name, position)organizationstakeholder categoryp/i designationkey stakeholder requirements (list 2)strategies for communicating with/managing stakeholders (list 2) 1aman rakkaradlteam memberc- specification of required materils - delivery schedule- weekly meetings - provide project status reports 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 points="" 80="" quality="" of="" work="" ●="" writing="" is="" concise="" and="" clear.="" written="" in="" business="" appropriate="" language.="" minor="" to="" no="" errors="" in="" grammar="" and="" spelling="" ●score:="" 16-20="" points="" ●="" writing="" is="" clear="" and="" mostly="" concise.="" mostly="" written="" in="" business="" appropriate="" language.="" few="" grammar="" and="" spelling="" errors="" ●score:="" 13-15="" points="" ●="" writing="" is="" somewhat="" unclear="" and/or="" not="" concise.="" mostly="" written="" in="" non-business="" appropriate="" language.="" several="" grammar="" and="" spelling="" errors="" ●score:="" 12-14="" points="" ●="" writing="" is="" mostly="" unclear="" and/or="" not="" concise.="" mostly="" written="" in="" colloquial="" language.="" many="" grammar="" and="" spelling="" errors="" ●score:="" 10-11="" points="" ●="" writing="" is="" incomprehensible="" or="" non-existant.="" most="" of="" the="" writing="" has="" grammatical="" and="" spelling="" errors="" ●score:="" 0-10="" points="" 20="" total="" stakeholder="" analysis="" assignment="" –="" worth="" 20%="" of="" final="" grade="" new="" concrete="" products="" containing="" recycled="" glass="" with="" adl="" process="" inc.="" (https://www.georgebrown.ca/about/office-of-research-innovation/research-facilities/green-projects)="" note:="" detail="" of="" project="" progress="" has="" been="" modified="" here="" for="" educational="" purpose="" and="" the="" names="" of="" the="" individuals="" are="" fictional="" to="" maintain="" confidentiality.="" company="" and="" project="" background="" adl="" process,="" an="" electronics="" recycling="" company="" in="" toronto,="" has="" been="" collaborating="" with="" george="" brown="" college="" to="" identify="" the="" opportunities="" and="" feasibility="" in="" recycling="" cathode="" ray="" tubes="" (crts)="" into="" a="" construction="" product="" (e.g.="" concrete).="" the="" project="" objective="" was="" to="" research="" concrete="" formulation,="" how="" it="" would="" be="" impacted="" by="" the="" addition="" of="" recycled="" glass="" and="" analyze="" the="" performance="" of="" different="" concrete="" formulations="" containing="" recycled="" glass.="" the="" research="" stage="" will="" be="" followed="" by="" the="" limited="" volume="" pilot="" production="" of="" modified="" concrete="" in="" adl="" process’s="" productions="" lines="" to="" be="" used="" for="" initial="" certification="" and="" marketing="" purpose="" of="" new="" product="" in="" canadian="" market.="" after="" twelve="" months="" of="" applied="" research="" and="" materials="" engineering="" characterization,="" adl="" process’s="" r&d="" team="" announced="" that="" the="" project="" was="" a="" big="" success="" and="" new="" developed="" concrete="" has="" all="" the="" technical="" requirements="" to="" meet="" the="" canadian="" standard="" for="" cementitious="" materials="" for="" use="" in="" concrete.="" considering="" the="" current="" importance="" of="" applied="" research="" in="" green="" construction="" and="" sustainable="" building="" practices="" in="" the="" canadian="" construction,="" this="" project="" could="" become="" a="" high-profile="" project="" for="" the="" ministry="" of="" environment="" and="" city="" of="" toronto.="" scenario:="" pilot="" production="" of="" modified="" concrete="" adl="" process’s="" current="" lines="" include="" certified="" product="" destruction="" and="" electronics="" recycling="" and="" has="" a="" total="" workforce="" of="" 200="" staff="" spread="" across="" five="" departments="" (refer="" to="" appendix="" a="" for="" organization="" chart).="" lisa="" hurley,="" the="" adl="" process’s="" ceo,="" convened="" a="" meeting="" with="" the="" five="" department="" directors="" to="" present="" the="" plan="" for="" the="" pilot="" production="" of="" modified="" concrete.="" this="" phase="" of="" the="" project="" is="" to="" modify="" one="" of="" the="" adl’s="" current="" productions="" (recycling)="" lines="" to="" produce="" required="" volume="" of="" modified="" concrete.="" however,="" in="" order="" to="" keep="" up="" with="" their="" regular="" electronics="" recycling="" business,="" adl="" will="" need="" to="" finish="" the="" production="" within="" four="" months="" and="" requires="" the="" participation="" and="" coordination="" of="" all="" five="" departments.="" all="" five="" department="" directors="" pledged="" their="" support="" for="" this="" plan="" and="" will="" serve="" as="" members="" of="" an="" executive="" steering="" committee="" along="" with="" lisa="" herself.="" this="" committee="" is="" tasked="" with="" identifying="" and="" assigning="" resources="" to="" support="" the="" project.="" the="" adl’s="" director="" of="" financial="" services="" has="" volunteered="" to="" champion="" the="" project.="" adl="" has="" contracted="" you="" as="" a="" project="" manager="" to="" plan,="" manage,="" and="" execute="" this="" plan.="" at="" this="" stage,="" the="" target="" market="" includes="" mid-size="" concrete="" producer="" companies="" in="" the="" greater="" toronto="" area.="" mark="" stock,="" environmental="" manager="" from="" gbc="" will="" serve="" as="" the="" client.="" points="" to="" consider="" ·="" adl="" will="" need="" to="" finish="" pilot="" production="" of="" modified="" concrete="" in="" four="" months.="" this="" will="" involve="" significant="" staff="" hires="" and="" training="" ·="" engineering="" has="" indicated="" that="" it="" can="" modify="" its="" current="" production="" line="" to="" produce="" the="" proposed="" products,="" but="" requires="" a="" different="" type="" of="" machine="" than="" it="" currently="" uses="" ·="" health="" &="" safety="" has="" indicated="" that="" the="" improved="" health="" and="" safety="" measures="" are="" required="" for="" employees="" who="" are="" supposed="" to="" work="" in="" new="" production="" line="" ·="" concrete="" producers="" are="" not="" typical="" customers="" for="" adl.="" sales="" &="" marketing="" will="" need="" to="" establish="" new="" customer="" contacts="" and="" secure="" purchase="" orders="" stakeholder="" analysis="" assignment="" this="" assignment="" is="" comprised="" of="" four="" parts="" aimed="" at="" evaluating="" your="" application="" of="" the="" stakeholder="" analysis="" concepts="" covered="" in="" the="" lectures.="" utilize="" the="" details="" from="" the="" case="" study,="" including="" the="" organization="" chart,="" combined="" with="" your="" own="" assumptions="" to="" complete="" each="" of="" the="" four="" parts.="" this="" assignment="" is="" worth="" 20%="" of="" your="" final="" grade.="" part="" 1="" –="" stakeholder="" identification="" ·="" identify="" the="" following="" 17="" stakeholders="" involved="" and/or="" impacted="" by="" this="" project:="" ·="" client="" (already="" provided="" as="" an="" example)="" ·="" executive="" steering="" committee="" (6="" members,="" indicate="" all="" their="" names="" and="" positions)="" ·="" project="" sponsor="" ·="" project="" manager="" (you!)="" ·="" project="" team="" (5="" staff,="" indicate="" all="" their="" names="" and="" positions)="" ·="" subject="" matter="" expert="" ·="" external="" authority="" ·="" end="" user="" ·="" for="" each="" stakeholder="" indicate="" their="" name="" and="" title="" (if="" identified="" in="" the="" case="" study),="" the="" organization="" they="" work="" for,="" their="" corresponding="" stakeholder="" category="" (which="" may="" be="" selected="" from="" the="" dropdown="" list)="" and="" p/i="" designation="" (e.g.="" a="" –="" high="" power/high="" interest)="" ·="" below="" is="" a="" sample="" of="" the="" expected="" output:="" important="" notes:="" ·="" adl="" has="" hired="" a="" consulting="" firm,="" smart="" construction="" consulting="" (scc)="" to="" assist="" in="" choosing="" the="" correct="" machinery="" required="" for="" pilot="" production="" of="" modified="" concrete.="" edgar="" rubio,="" a="" senior="" consultant="" working="" with="" scc,="" will="" be="" assigned="" to="" this="" project="" ·="" ensure="" that="" the="" project="" team="" members="" have="" most="" appropriate="" skills="" to="" help="" deliver="" the="" project="" but="" are="" not="" committed="" to="" management="" responsibilities="" on="" a="" day-to-day="" basis.="" it="" is="" expected="" that="" the="" project="" team="" members="" will="" work="" 100%="" of="" their="" available="" time="" on="" this="" project="" until="" it="" is="" completed.="" part="" 2="" –="" responsibility="" matrix="" ·="" complete="" the="" responsibility="" matrix="" for="" the="" stakeholders="" shown.="" ·="" for="" each="" intersecting="" stakeholder="" and="" activity="" indicate="" which="" of="" the="" four-letter="" responsibility="" designations="" (r="" -="" responsible,="" a="" –="" accountable,="" c="" –="" consulted,="" i="" –="" informed)="" ·="" pay="" close="" attention="" to="" the="" notes="" in="" red="" font="" in="" the="" responsibility="" matrix="" tab="" of="" the="" excel="" document.="" part="" 3="" –="" communication="" plan="" ·="" enter="" information="" for="" columns="" b-d="" for="" each="" of="" the="" stakeholder="" groups="" identified="" in="" the="" ‘communications="" plan’="" tab="" (column="" a="" is="" already="" completed)="" ·="" for="" the="" ‘what="" information="" they="" need’="" column,="" indicate="" what="" project="" information="" each="" stakeholder="" needs="" to="" be="" provided="" in="" order="" to="" successfully="" undertake="" their="" assigned="" tasks="" ·="" for="" the="" ‘frequency’="" column,="" indicate="" how="" often="" the="" information="" needs="" to="" be="" communicated="" to="" them="" (e.g.="" weekly,="" daily,="" etc.)="" ·="" for="" the="" ‘medium’="" column,="" indicate="" how="" the="" information="" will="" be="" conveyed="" to="" the="" stakeholder="" (e.g.="" weekly="" status="" report,="" bi-weekly="" meeting,="" etc.)="" ·="" below="" is="" a="" sample="" of="" the="" expected="" output:="" part="" 4="" –="" stakeholder="" analysis="" matrix="" ·="" the="" stakeholder="" analysis="" matrix="" lists="" all="" identified="" stakeholders="" for="" the="" project="" ·="" where="" appropriate="" copy="" information="" from="" the="" stakeholder="" identification="" and="" communication="" plan="" tables.="" ·="" refer="" to="" the="" slides="" for="" class="" 4="" to="" complete="" column="" e="" (key="" stakeholder="" requirements)="" –="" list="" most="" important="" two="" requirements="" for="" each="" stakeholder="" ·="" below="" is="" a="" sample="" of="" the="" expected="" output:="" submission="" guidelines="" 1.="" capture="" all="" work="" in="" the="" stakeholder="" matrix="" analysis.xlsx="" file;="" do="" not="" save="" as="" a="" different="" file="" format.="" 2.="" complete="" the="" cover="" page="" with="" your="" gbc="" number,="" name,="" and="" due="" date.="" 3.="" save="" the="" file="" using="" the="" following="" format="" gbc#_first="" name_last="" name_stakeholder="" analysis="" matrix="" analysis="" (e.g.="" 1234567_james_smith_stakeholder="" analysis="" matrix).="" 4.="" upload="" your="" completed="" assignment="" to="" blackboard="" (in="" the="" assignments="" section)="" by="" 11:59pm="" (toronto="" time)="" jan="" 26th,="" 2023.="" 5.="" complete="" this="" assignment="" as="" if="" you="" were="" providing="" it="" to="" a="" business="" client.="" use="" professional="" language.="" do="" not="" use="" slang="" or="" colloquialisms.="" appendix="" a:="" adl="" process="" organization="" chart="" page="" 2="" of="" 2="" appendix="" b:="" power="" interest="" grid="" power/interest="" grid="" ="" ="" ="" ="" b="" ="" ="" high="" power/low="" interest="" ="" ="" monitor="" closely="" ="" ="" a="" ="" ="" high="" power/high="" interest:="" ="" ="" manage="" key="" relationship="" ="" ="" d="" ="" ="" low="" power/low="" interest="" ="" ="" low="" priority="" ="" ="" c="" ="" ="" low="" power/high="" interest="" ="" ="" keep="" informed="" ="" power="" ="" ="" interest="" ="" power/interest="" grid="" b="" high="" power/low="" interest="" monitor="" closely="" a="" high="" power/high="" interest:="" manage="" key="" relationship="" d="" low="" power/low="" interest="" low="" priority="" c="" low="" power/high="" interest="" keep="" informed="" power="" interest="" cover="" page="" stakeholder="" analysis="" matrix="" assignment="" name="" gbc="" #="" 1.="" stakeholder="" identification="" #="" stakeholder="" name="" &="" title="" stakeholder="" organization="" stakeholder="" category="" p/i="" designation="" 1="" mark="" stock,="" environmental="" manager="" gbc="" client="" a="" 2="" 3="" 4="" 5="" 6="" 7="" 8="" 9="" 10="" 11="" 12="" 13="" 14="" 15="" 16="" 17="" *="" note="" that="" you="" may="" need="" to="" scroll="" within="" the="" stakeholder="" category="" (column="" c)="" drop="" down="" list="" to="" view="" and="" choose="" all="" possible="" entries="" client="" senior="" management/executive="" steering="" committee="" project="" sponsor="" project="" manager="" project="" team="" member="" employees="" funder="" subject="" matter="" experts="" end="" user="" external="" authority="" wider="" community="" 2.="" responsibility="" matrix="" stakeholder="" category="" activity="" client="" project="" sponsor="" project="" manager="" project="" team="" member(s)="" operations="" manufacturing="" staff="" (adl)="" human="" resources="" staff="" (adl)="" sales="" and="" marketing="" staff="" (adl)="" information="" technology="" staff="" (adl)="" end="" user="" subject="" matter="" expert="" external="" authority="" approve="" funding="" for="" the="" project="" secures="" adl="" process's="" resources="" for="" the="" project="" prepare="" project="" plan="" (includes="" schedule="" and="" budget)="" hire="" staff="" to="" produce="" modified="" concrete="" upgrade="" it="" infrastructure="" (required="" for="" project)="" retool/install="" manufacturing="" equipment="" purchase="" raw="" materials="" and="" machinary="" manufacture="" modified="" concrete="" identify="" target="" market="" (purchasors="" of="" the="" modified="" concrete)="" obtain="" sales="" contracts="" with="" end="" users="" prepare="" and="" distribute="" project="" status="" reports="" a="" -="" accountable:="" stakeholder="" who="" approves="" the="" completion="" of="" the="" task="" r="" -="" responsible:="" is="" the="" person/persons="" primarily="" responsible="" for="" working="" on="" and="" completing="" the="" task="" c="" -="" must="" be="" consulted="" during="" the="" delivery="" of="" the="" task="" i="" -="" must="" be="" informed="" about="" the="" status="" of="" the="" task="" note="" 1:="" all="" stakeholders="" do="" not="" necessarily="" receive="" an="" a,="" r,="" c="" or="" i="" designation="" for="" all="" tasks="" (only="" those="" with="" which="" they="" are="" involved)="" note="" 2:="" must="" be="" at="" least="" one="" 'r'="" and="" one="" 'a'="" for="" each="" activity="" note="" 3:="" refer="" closely="" to="" the="" organizational="" chart="" in="" the="" assignment="" document="" for="" information="" on="" where="" specific="" functions="" reside="" in="" the="" organization="" 3.="" communication="" plan="" stakeholder="" what="" information="" they="" need="" frequency="" (show="" multiple="" frequencies="" if="" applicable)="" medium="" project="" sponsor="" -="" high="" level="" cost,="" schedule,="" quality="" performance="" (project="" status="" information)="" -="" problems="" and="" proposed="" actions="" from="" pm="" -="" weekly="" -="" written="" status="" report="" -="" weekly="" meeting="" -="" ad="" hoc="" meetings="" as="" necessary="" client="" executive="" steering="" committee="" (same="" information="" for="" all="" e.s.c.="" members)="" project="" team="" members="" (same="" information="" for="" all="" project="" team="" members="" subject="" matter="" experts="" external="" authority="" end="" user="" 4.="" stakeholder="" analysis="" matrix="" #="" stakeholder="" (name,="" position)="" organization="" stakeholder="" category="" p/i="" designation="" key="" stakeholder="" requirements="" (list="" 2)="" strategies="" for="" communicating="" with/managing="" stakeholders="" (list="" 2)="" 1="" aman="" rakkar="" adl="" team="" member="" c="" -="" specification="" of="" required="" materils="" -="" delivery="" schedule="" -="" weekly="" meetings="" -="" provide="" project="" status="" reports="" 2="" 3="" 4="" 5="" 6="" 7="" 8="" 9="" 10="" 11="" 12="" 13="" 14="" 15="" 16="">