Mgmt 404 Project

MGMT 404 job Campus bookstore self-checking Register December 12, 2011 Professor Chuang Table of Contents backcloth statement3-4 earn breakdown organize.. 5 mesh diagram. 6 Risk management be after7-8 Resource management plan8 Communication management plan9-10 Scope Statement Project Overview Statement Executive sum-up ________________________________________ Project come upon Self-checking registers section bookstallLast Updated November 11, 2011 Project Manager(s) chant Johnson, Nancy Drew, David Winner Project Department Owner Student Body Community ____________________________________________________________ ____________ Project Overview Installation of a self-checking registers in Campus bookstore. Project should non exceed $23,000. Deliverables 1. Gather Requirements a. Discuss current system with Bookstore Representatives b. Understand the requirements c. Understand the budget l cobblers lastable d. Research any permits that are required 2. Self-checkout system d evelopment a.Outsource the development to external spot b. Install the self-checkout system at the exit of the Bookstore c. Discuss with IT department the deal of inputting barcode information d. arrive contractor about installation requirements 3. Communication with Stakeholders a. Inform students about the new process b. Inform Bookstore staff/ warranter about the new process c. Inform staff/security about their responsibilities 4. go for the process a. Set a launch date Milestones 1. Systems ratifiedNovember 25, 2011 2. Permits approvedNovember 21, 2011 3. Electrical outlets installedDecember 9, 2011 . social structure completedDecember 22, 2011 5. IT installs software and training completedJanuary 13, 2011 6. Completion dateJanuary 20, 2011 Technical Requirements 1. Confirm present area for self-checkout counter 2. Obtain permits 3. Approval of building codes Limits and Exclusions 1. Contractors reserves the right to contract outside serve 2. Contractors trustworthy for any subcontracted work 3. Site hours set for Monday through Friday, 800 a. m. to 600 p. m. ____________________________________________________________ __________________ Prepared by Carol JohnsonProject ManagerNancy Drew David Winner Work Breakdown Structure Task Name School Register 1 Requirements Gathering 1. 1 Discuss the current system with Book bloodline Representatives 1. 2 Understand the requirements with stakeholders 1. 3 Understand the budget available for developing the new system 2 butt Design 2. 1 Design high level process map 2. 2 pick up feedback from stakeholders 2. 3 Design detailed level process map 2. 4 Identify the roles of different stakeholders in the Process 3 Self-checkout system development 3. 1Outsource the development to an external means 3. Install the self-checkout system at the exit of the Bookstore 3. 3 Collect the details of all stakeholders using Bookstore from the Admin Office 3. 4 Design and Development of access tease 3. 5 Collect the acce ss cards from external agency 3. 6 Distribute access cards to all the stakeholders 4 Communication to stakeholders 4. 1 Communicate to Students 4. 1. 1 Inform students about the new process 4. 1. 2 Inform students about their roles & expectations 4. 1. 3 request students to cast their access cards 4. 2 Communicate to Faculty/T apieceers 4. 2. Inform faculty about the new process 4. 2. 2 Inform faculty/teachers about their roles 4. 2. 3 Request Faculty/Teachers to verify their access cards 4. 3 Communicate to Book Store Staff / Security 4. 3. 1 Inform the staff/security about the new process 4. 3. 2 Inform the staff/security about their roles and responsibilities 4. 3. 3 Request Staff/Security to verify their access cards Implement the Process 5. 1 Develop a common message about the date of launch 5. 2 Encourage participation and adherence from the stakeholders Network Diagram Risk precaution PlanRisk Event Response Contingency Plan spark Person Responsible Completion before new semester Accept Work approximately Time rear off Carol corporeal out of spec rationalize Contact Manufactory Programming not working IT department & Nancy Employee training Share Work around Management advisory Management & Carol IT programing equipment (barcodes) Share Work around Not resolved in 24 hours IT department & Nancy Equipment port Mitigate Work around Not resolved in 36 hours IT department & Nancy Wrong equipment Mitigate Order new equipment Not fitting in define shoes IT department & Nancy accessible space in bookstore Transfer Re-arrange bookstore Contractor information Store management & Carol computer hardware malfunction Mitigate Order Equipment falls IT department & Nancy Contractor schedule conflicts Transfer Work around Late showing up David Available work hours (school closing) Transfer Work around Bad prevail/holidays David Risk Management Analysis RISK EVALUATION Risk Probability Cost Schedule Scope Quality Risk Score Completion before new semester 30% 4 2 2 2 3. 0 Material out of spec 20% 1 2 5 1 1. 8 Employee training 20% 3 2 2 1 1. 6 IT programing equipment (barcodes) 15% 2 3 3 2 1. 5 Equipment interface 20% 1 2 2 1 1. 2 Wrong equipment 10% 2 3 1 4 1. 0 Available space in bookstore 20% 1 1 2 1 1. 0 ironware malfunction 10% 2 2 2 1 0. 7 Contractor schedule conflicts 5% 1 4 1 1 0. 4 Available work hours (school closing) 5% 1 3 1 1 0. 3 Defined Conditions for Risk Management Analysis Project Objective congress or Numerical Scales Very Low 1 Low 2 Moderate 3 senior high school 4 Very High 5 Cost unnoticeable embody increase 10% cost increase 10-25% cost increase 25-50% cost increase 50% cost increase Time Insignificant time increase 5% time increase 5-10% time increase 10-25% time increase 25% time increase Scope Scope decrease barely noticeable Minor areas of scope stirred Major areas touch on Reduction unacceptable to sponsor Project end item is effectively unprofitable Quality Quality de gradation barely noticeable Only very demanding application are affected Quality reduction requires sponsor approval Quality reduction unacceptable to sponsor Project end item is effectively useless Resource Management Plan Resource Name Type Material Label Initials aggroup Max. Units Std. Rate Ovt. Rate Cost/Use Accrue At Base calendar Register Price Work RP century% $0. 00/hr $0. 00/hr $0. 0 Prorated cadence Outsource Fees Work OF 100% $0. 00/hr $0. 00/hr $0. 00 Prorated Standard Contractors Work C 100% $25. 00/hr $25. 00/hr $0. 00 Prorated Standard Installers Work I 100% $75. 00/hr $125. 00/hr $0. 00 Prorated Standard Training Work T 100% $25. 00/hr $25. 00/hr $0. 00 Prorated Standard Project Manager Work PM 200% $25. 00/hr $25. 00/hr $0. 00 Prorated Standard IT department Work I 100% $75. 00/hr $125. 00/hr $0. 00 Prorated Standard Communication Management Plan Campus BookstoreSelf Checking Registers Prepared by Carol Johnson Date December 11, 2011 Author ized by Carol Johnson ___________________________________________________________ __________________ A. General Information Installation of one (1) self-checking register. Which is to be installed at the exit of the Campus Bookstore. B. Stakeholder List any Stakeholders are located in the same geographical locations Stakeholder Name/Title Project Role IT harbour Group Customers that volition design the system. They pass on design and program system once it is install. periodic updates will be sent. IT Support Group ManagerAaron Smith give oversee the design and approval. Will depart support the development police squads. Campus DeanSamuel Adams Overall approval for costs.Weekly updates will be received from Project manager Project Team Responsible for providing followups of requirements, technology direction, and reviews. The group will receive weekly attitude reports, access to all documentation for the project, and access to of retires tracking database. Project Te am LeaderCarol Johnson Will manage the entire project from Scope to acceptance and final launch. Carol will be responsible for allocation of all resources and approval of time schedules for the entire project. In charge of overseeing the installation, construction, equipment purchases. Weekly updates will be sent. C. Communication Document Description Audience Expected Action Comm.Class Input Method make Method Frequency Responsible resource Project Status Report All Project team members Individual Status Submitted every Monday needful Status Update Form E-mail each Tuesday Weekly Carol Issue Report All Project team members Individual Status Submitted every Monday Mandatory Status Update Form E-mail each Tuesday Weekly Aaron Outsource report Campus Dean, IT Support Group Manager Individual Status Submitted every Monday Mandatory Status Update Form Email each Tuesday Weekly Carol D. Method for Updating the Communication Plan The communications plan will be updated as needed and reviewed during Status Meetings which will be held weekly. Any changes to the communication will be approved by the Group Team manager. Any changes to the plan will be sent out to the stakeholders in a timely manner. E. Existing SystemsThere will be a weekly organizational liberate skirmish that is held by the Project Team group. The IT Support group will attend the meeting to review changes and major events to the project. The meeting will also address items and other systems that have an impact on us. F. Escalation Process The initial review of the issue or risk will occur during the project status meeting as gathered by the IT Support Group report. The project status will be utilise to escalate any issues or risks not resolved during the weekly meetings. When the issue or risk is identified, we will conduct a review and provide a contingency plan at Status meeting. If the issue or risk is still not resolved, it will be assigned to an executive committee for action.