Mgmt 404 Project

MGMT 404 Project Campus Bookstore self-checking Register December 12, 2011 Professor Chuang Table of Contents Scope statement†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦3-4 Work breakdown structure†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦.. 5 Network diagram†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. 6 Risk management plan†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â ‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦7-8 Resource management plan†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦8 Communication management plan†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦9-10 Scope Statement Project Overview Statement Executive Summary ________________________________________ Project Name: Self-checking registers Department: Bookstore Last Updated: November 11, 2011 Project Manager(s): Carol Johnson, Nancy Drew, David Winner Project Department Owner: Student Body Community ____________________________________________________________ ____________ Project Overview Installation of a self-checking registers in Campus bookstore. Project should not exceed $23,000. Deliverables 1. Gather Requirements a. Discuss current system with Bookstore Representatives b. Understand the requirements c. Understand the budget available d. Research any permits that are required 2. Self-checkout system development a. Outsource the development to external agency b. Install the self-checkout system at the exit of the Bookstore c. Discuss with IT department the process of inputting barcode information d. Contract contractor about installation requirements 3. Communication with Stakeholders a. Inform students about the new process b. Inform Bookstore staff/security about the new process c. Inform staff/security about their responsibilities 4. Implement the process a. Set a launch date Milestones 1. Systems approved—November 25, 2011 2. Permits approved—November 21, 2011 3. Electrical outlets installed—December 9, 2011 . Construction completed—December 22, 2011 5. IT installs software and training completed—January 13, 2011 6. Completion date—January 20, 2011 Technical Requirements 1. Confirm staging area for self-checkout counter 2. Obtain permits 3. Approval of building codes Limits and Exclusions 1. Contractors reserves the right to contract outside service s 2. Contractors responsible for any subcontracted work 3. Site hours set for Monday through Friday, 8:00 a. m. to 6:00 p. m. ____________________________________________________________ __________________ Prepared by: Carol Johnson—Project Manager Nancy Drew David Winner Work Breakdown Structure Task Name| School Register| 1 Requirements Gathering | 1. 1 Discuss the current system with Book Store Representatives| 1. 2 Understand the requirements with stakeholders| 1. 3 Understand the budget available for developing the new system| 2 Process Design| 2. 1 Design high level process map| 2. 2 Request 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 agency| 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 cards| 3. 5 Collect the access 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 verify their access cards| 4. 2 Communicate to Faculty/Teachers| 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 Management Plan Risk Event| Response| Contingency Plan| Trigger | Person Responsible| Completion before new semester| Accept| Work around| Time frame off| Carol | Material out of spec| Mitigate| 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 interface| Mitigate| Work around| Not resolved in 36 hours| IT department & Nancy| Wrong equipment | Mitigate| Order new equipment| Not fitting in define space| IT department & Nancy| Available space in bookstore| Transfer| Re-arrange bookstore| Contractor information| Store management & Carol | 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 weather/holidays| David| Risk Man agement 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| Hardware 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| Relative or Numerical Scales| Very Low – 1| Low – 2| Moderate – 3| High – 4| Very High – 5| Cost| Insignificant cost 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| 1 0-25% time increase| > 25% time increase| Scope| Scope decrease barely noticeable| Minor areas of scope affected| Major areas affected| Reduction unacceptable to sponsor| Project end item is effectively useless| Quality| Quality degradation 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| Group| Max. Units| Std. Rate| Ovt. Rate| Cost/Use| Accrue At| Base Calendar| Register Price| Work|   | RP|   | 100%| $0. 00/hr| $0. 00/hr| $0. 0 | Prorated| Standard| 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 Bookstore—Self Checking Registers Prepared by: Carol Johnson Date: December 11, 2011 Authorized 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 All Stakeholders are located in the same geographical locations Stakeholder Name/Title| Project Role| IT Support Group | Customers that will design the system. They will design and program system once it is install. Weekly updates will be sent. | IT Support Group Manager—Aaron Smith| Will oversee the design and approval. Will provide support the deve lopment teams. | Campus Dean—Samuel Adams| Overall approval for costs. Weekly updates will be received from Project manager| Project Team | Responsible for providing reviews of requirements, technology direction, and reviews. The group will receive weekly status reports, access to all documentation for the project, and access to of issues tracking database. | Project Team Leader—Carol 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| Output Method| Frequency| Responsible resource| Project Status Report| All Project team members| Individual Status Submitted every Monday| Mandatory| 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 Systems There will be a weekly organizational release meeting 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 used 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.