Development team 178 build erp interface 18 developer

This preview shows page 14 - 17 out of 19 pages.

Development Team1.7.8Build ERP Interface18DeveloperDevelopment Team1.7.9Development46Ryan Neff, Stacy LyleDevelopment Team1.8Testing1.8.1Perform Testing1.8.1.1Perfrom Phase 1 Test12Marc SandersDevelopment Team1.8.1.2Perform Phase 2 Test20Development TeamDevelopment Team1.8.2Perform System Test160Kara Siposki, Todd Eliason, Marc Sanders, Developers, Ryan Neff, Stacy LyleFunction Test Team1.8.3Perform Validation Testing80Kara Siposki, Todd Eliason, Marc Sanders, Developers, Ryan Neff, Stacy LyleFunction Test Team1.9Deployment1.9.1Implement80Kara Siposki, Todd Eliason, Marc Sanders, Developers, Ryan Neff, Stacy LyleFunction Test Team1.9.2Deploy8Kara Siposki, Todd Eliason, Marc Sanders, Developers, Ryan Neff, Stacy LyleFunction Test Team1.9.3Finish Project90Kara Siposki, Todd Eliason, Marc Sanders, Developers, Ryan Neff, Stacy Lyle, Rick BurkeFunction Test TeamB. EvaluationResource Evaluation:There are sufficient resources to complete the project within the given time frame. The project stakeholders are experienced and possess the skills needed to develop the new webpage in the given amount of time. Outsourcing the DEV team will enable A&D High
FINAL PROJECT: PART 115Tech to focus the attentions on the development and requirements desired for the final project.IV.RiskRisk Overview:This risk section will identify potential risks and possible mitigation strategies associated with the project. Those risks will be recorded as well as maintained in the Risk Register. This Risk Register will provide a brief description of each risk and assign it a risk number. Additionally, theregister will score each risk on occurrence possibility. The Project Manager is assigned to maintaining this Risk Register and will review and update on a bi-weekly basis.A. Sources, & StrategiesRISKNO.RISK DESCRIPTION (Event, Causes, Impacts)COMMENT ON RISK(Trends, Background, etc.)CONSEQUENCE(SEVERITY)SCORE (1–5)LIKELIHOOD SCORE(1–5)RISK STRATEGY(Avoid, Reduce, Transfer,Do Nothing) 1Lack of resourcesFilling the roles of developer is dependant on outside agency supplying workers.41Avoid - Assist thirdparty agency by dedicating an HR recruiter toselect candiddates for the developer
FINAL PROJECT: PART 116role2Instability in projectChanging Project Managers after project has begun aswell as poor planning at the onset of project25Reduce - As the project has already changed hands, management needs to ensure that the current PM remians as well as the project plan is closely followed.3Competitors push aheadA less than spectacualr rollout of new e-marketplace has potentialto give competitors a tremendous edge42Avoid - Use retrieved data from competition to determine what worked and failed in their rollouts to avoid mistakes inproject4Budget is inaccurateA lack of data causes budget to be msiidentified44Reduce - Apply additonal funding in initial budget to account forunknowns5Late entering online marketCompetitiorshave alreadybeen selling in an online setting for 15Do Nothing - Put forth the best product

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture