Assume a company decided to accept a Spanish localization request.. Your project is starting to suffer because you are not meeting the Spanish deliverable deadlines, which have even impacted the European and Japanese language deadlines. During the review process, the Spanish field office has complained that the Spanish version is of poor quality. Your boss has asked you to explain the issues at the next steering committee meeting.In order to prepare for this meeting, you have identified some risks that affect your project. Using the attached template, create a cause and effect diagram (Ishikawa / fishbone diagram) showing the results of a “Poor Spanish Version”. Document the possible root causes from the project data and information you received from the Lullnet stakeholders that is provided in the attached Word Document. Make sure to label all sections of the diagram, explain the causes and write a brief analysis showing the cost of quality for these issues.Note: The assignment is not about cost, it is aimed at finding the causes of failure of the Spanish version that may have impacted on the cost of quality. You donât need to find any cost. You need to find what problems may have resulted in the poor Spanish version.Important Mail/Data from Simulation Regarding Spanish LocalizationProposal for Spanish Localization:We have received the launch dates for the localized versions and the European and Japanese teams areenthusiastic about their sales prospects. I have been contacted by the Lullnet Spain office about thepossibility of a Spanish localization. They believe there is a significant revenue opportunity if a Spanishversion can be produced in the same timeframe. I want to make sure we fully analyze the numbers beforewe make a decision to pursue it or not. I have asked Maria Garbosa from Lullnet Spain to send you thefinancial analysis to assist you in working with Jason to make a decision.Nicholas Prince asked me to forward you our capital budget analysis of the Spanish localization, revenueopportunity. I have worked with the various Spanish channel partners to produce the attached, revenueestimates for a Spanish version of LullSIM. I realize a new version of LullSIM will be out early next year,so I have limited the revenue estimates to six-months. Realistically, this is approximately the saleswindow we are looking at for this version, assuming the typical 90-day turnaround for localized versionsafter the US product launches.Email about Resource Shortage:I am following up on Jason’s request to evaluate the feasibility of adding a Spanish localization to theexisting project. Given other projects we have in process, I do not believe I could assign any resources tothe effort until several weeks after they would be required. Contractors can be hired to help out with QA,but I feel the additional cost would have a negative impact on Lullnet Spain’s original financial estimates.I heard that you are looking into creating a Spanish version of LullSIM. All versions of the software aresupported at headquarters, which includes the localized versions. We currently do not have anyone onstaff that could support a Spanish version and our budget does not have the flexibility to hire a Spanishspeaker until next fiscal year. We could overcome this obstacle if the Spanish office pays for the extraresource.Email about analysis for Spanish Localization Opportunity:I wanted to ensure you have all of the data required to perform an appropriate analysis of thisopportunity. My Spanish team has started to survey the field and we have a fair amount of interest in thisproduct. We are hoping to get this product out with the French, German and Japanese versions. Pleaseget back to me by tomorrow to let me know the results of your evaluation. I would also like to know whatchange control process you have put in place for my groups requests. I want to make sure my requestsare being considered systematically and not based on the Engineering mood to add or change a scoperequest.Email about Project Hurdle Rate:I have been receiving pressure from Lullnet Spain to produce a Spanish version of LullSIM. I am told youhave already received some sales figure estimates from Maria Garbosa. Use those sales figures,combined with the Spanish cost estimate given by the localization vendor, to calculate the net presentvalue. Note that we use a 12 percent hurdle rate when discounting future cash flows, so take that intoconsideration when evaluating this opportunity.More information about Spanish Localization:I was contacted again regarding the Spanish localization by Nicholas Prince himself. He wanted me toassist you in analyzing this opportunity. I think you can handle this on your own given your qualificationsas a project manager. Just remember, Spanish spoken in Spain is not the same as Spanish spoken inLatin America, which by the way each Latin American country has their own variation of Spanish. Its not aone size fits all strategy, just like US English is not the same as the Queen’s English. In any case, I will bereturning back to the company soon enough but probably not before you have finished this project. Becareful dealing with Nicholas, he has a lot of influence in the company.CAUSES OF POOR SPANISH VERSIONSample textSampletextSample textSample textSample textSample textSampletextPoorSpanishVersionSample textSample textSample textSample text
