Homework answers / question archive / The full details, requirements and grading criteria are provided in the in the attached file below

The full details, requirements and grading criteria are provided in the in the attached file below

Business

Share With

The full details, requirements and grading criteria are provided in the in the attached file below.

You are required to use the format in the Risk-Register Example. Please provide at least two references.

The purpose of this Individual project is to develop a risk analysis and a risk register spreadsheet for the ITP project. This is an assessment of the potential risks that your project may run into in the future, and a plan for how to either prevent them or handle them if they do occur. By addressing project risks in advance, we can reduce risks, reduce the chance that risks will mature into problems, and reduce costs, and increase chances of project success.ITP-5 - Project Risk Assessment (Individual project) (PMBOK 11) Addresses Course Outcomes #4c and 6e Please be sure to read the Team Contribution Assessment and Grading of Team Assignments and the Project Documentation Requirements sections of this ITP Master Document. Assignment for the ITP-5 Project Deliverable This assignment is an INDIVIDUAL assignment. Review your previous deliverable assignments and the assignments that other teams have posted in the Shared Learning Environment Discussions. This assignment has two parts. Risk Register in Excel – Part 1 Using your team's ITP WBS, develop and submit a project risk register in MS Excel: ? A project risk register, from the textbook, from the classroom material, from www.pmi.org, or from other valid research, that meets the following requirements. ? In MS Excel, the risk register should be populated with the risks for at least 3 tasks of different types and categories at EACH level of the decomposition in the WBS (no fewer than 12 tasks must have risks identified -- 3 major tasks, 3 sub-tasks, 3 lowest level leaf node tasks or sub-sub tasks, and also at least 3 risks at the overall project level (Level 0)). (Note that this is minimum required, along with the other things below, to earn a satisfactory score. To earn a better score, you would want to include more risks at each level, and some of the additional things mentioned below.) ? Risks may include, for example, technical IT risks, external risks that impact the project but which are outside the PM's control, project management risks, risks of project changes, and so forth. ? Please note that a task could have more than one risk! The risk register must include MITIGATION strategies to avoid/eliminate or minimize the risk and contingency plans (what you will do if the risk happens). If the format you are using does not include these columns, please add them, then be clear on the difference between mitigation and contingency. Address what aspect of the project will be affected by each mitigation action - cost, schedule, or scope. Provide a recommendation for whether or not the mitigation action should be implemented, remembering that EACH mitigation will impact the project's scope, cost or schedule. The risk register should also include: ? Title or description of item or TASK at risk. (This is the WBS task in which the risk occurs, not the risk itself.) ? Also include the WBS ID and a designation of which WBS level the task is at. Each risk in the Risk Register should show the WBS level of the task that it refers to. I urge you to let the computer do this for you, since doing it by hand seems error prone for some reason. Either import the field from MS Project or use an Excel formula to calculate the level for you. ? ? ? ? ? ? ? ? ? ? Description of the RISK (What is the risk? What is at risk of happening?) (This identifies the nature of the risk itself, not the task.) Risk category or type (e.g., technical risks, quality risks, financial risks, external risks, organization risks, project risks, quality risks, other risks, etc.) Consequences, impact, or cost at risk (adjectival or numeric) Likelihood or probability (adjectival or numeric) Initial risk score (or "risk product", consequence times likelihood) Risk handling category (avoidance, mitigation, transfer, acceptance, etc.) The mitigation action that, if taken, would avoid the risk or the impact of the risk. Cost and time required for the mitigation action. Contingency plan - what the team will do if the risk actually happens Designation of risk "owner" or risk manager (best designated by title or role rather than by individual's name) For additional points, you may include such things as: ? ? ? ? ? ? ? ? ? ? ? Additional risks Risks for additional tasks Results of handling each risk after controls are implemented: Consequences or cost at risk Likelihood or probability Final risk score or product (consequence times likelihood) Quantitative numerical consequences, probabilities, and risk scores (rather than subjective, qualitative, or adjectival assessments) Additional narrative discussion of each risk, handling method, etc. Total of all the risk scores (risk products) for the entire project after risk controls are implemented, in dollars. Also include some risks associated with the general ability to complete the project successfully. (You might consider these risks at Level 0, the root level, of the WBS, affecting the entire project.) Finally, if you quantitatively calculated the risk product in those terms, then what is the total of all the initial risk scores (risk products) for the entire project, in dollars. Text Document – Part 2 Please include the Executive Summary with appropriate changes Questions: In an accompanying Word doc or text submission, answer the following questions: 1. Which risks (and associated tasks) would be the most threatening to the success of the project and why? This discussion should be very specific to tasks and their associated risks. 2. Which top THREE mitigations (and associated tasks) and risk handling plans should be implemented, and why? Remember that mitigation actions will affect cost, schedule and/or scope – so discuss what can you AFFORD to do based on the likelihood and impact of the risk? 3. What are the TOTAL impacts on cost, schedule and scope for the project if the recommended risk controls and mitigation actions are taken? If you use costs, how did you calculate the cost? Will the risk handling improve things or make them worse? That is, will the project cost more and/or be less successful because of risk handling, or will it cost less and/or be more successful because of risk handling? How so? Explain. 4. How did you determine those costs and impacts? Please describe. What is the benefit of mitigating risks that are identified for mitigation? 5. If your project could only afford $20,000 for mitigation actions, which risks (identify associated tasks) would be implemented? 6. If your project could only tolerate a 5 day delay related to mitigation actions, which risks and mitigations (identify associated tasks) would be implemented? 7. What would be the most expensive (time and or schedule) contingency action/plan? Identify the associated task and explain why this contingency would be the most expensive in terms of time or schedule. 8. How did you determine those costs and impacts? Please describe. Submit the Excel and the Word document(s) to the Assignment Area. Approximate breakdown by areas include: o o o General: Structure, Format, Mechanics, Style (~5%) Risk register (~84%) Questions (~10%) Rubrics and Grading for the ITP-5 Project Deliverable To earn 90-100% of the points available for this assignment – The risk register meets the basic requirements. Identify at least 10 risks at each level of the WBS, including risks that affect the general ability to complete the project successfully, major tasks of different types and categories, sub-tasks of different types and categories, risks of several different risk types and categories, including external risks, financial risks, organization risks, PM risks, quality risks, technical risks, and other risk categories. In addition, include such things as: • • • • • • • • Multiple risks for single tasks Quantitative numerical consequences, probabilities, and risk scores (rather than subjective, qualitative, or adjectival assessments) Show risk assessment (probability, impact, and score) numerically (e.g., percentages, dollars, etc.) rather than qualitatively. Additional narrative discussion of each risk, handling method, etc. Designation of risk "owner" or risk manager and why that person or functional position is the “owner” Total of all the risk scores (risk products) for the entire project after risk controls are implemented, in dollars. Also include some risks associated with the general ability to complete the project successfully. (You might consider these risks at Level 0, the root level, of the WBS, affecting the entire project.) Answer all the initial risk scores (risk products) for the entire project, in dollars. Include the following risk info for ea. risk: Title or description of item or TASK at risk; Description of the RISK; Risk category or type; Initial assessment of Consequences, impact, or cost at risk; initial likelihood or probability; Initial risk score (consequence x likelihood); Risk handling CATEGORY; Risk handling / control / mitigation / action PLAN; Designation of risk "owner"; Risk results with/after controls / handling plans implemented (Consequences or cost with controls; Likelihood or probability with controls; Final risk score (consequence x likelihood)). Answer all questions, and include reference sources are used in the text and included in a Reference page. Show risk assessment (probability, impact, and score) numerically (e.g., percentages, dollars, etc.) rather than qualitatively. To earn 80-89% of the points available for this assignment – Identify at least 6 risks at each level, including risks such as: the general ability to complete the project successfully; major tasks of different types and categories; sub-tasks of different types and categories; lowest level leaf node tasks or sub-sub tasks of different types and categories. Include risks of several different risk types and categories, including risks such as: external risks, financial risks, organization risks, PM risks, quality risks, technical risks, and other risk categories. Include several different risk handling categories (avoidance, mitigation, transfer, acceptance). Include most of the following risk info for ea. risk: Title or description of item or TASK at risk; Description of the RISK; Risk category or type; Initial assessment of Consequences, impact, or cost at risk; initial likelihood or probability; Initial risk score (consequence x likelihood); Risk handling CATEGORY; Risk handling / control / mitigation / action PLAN; Designation of risk "owner. Answer all questions. To earn 70-79% of the points available for this assignment – Identify at least 3 risks at each level, including risks such as: the general ability to complete the project successfully; major tasks of different types and categories; sub-tasks of different types and categories; lowest level leaf node tasks or sub-sub tasks of different types and categories. Include risks of several different risk types and categories, including risks such as: external risks, financial risks, organization risks, PM risks, quality risks, technical risks, and other risk categories. Include different risk handling categories (avoidance, mitigation, transfer, and acceptance). Include most of the following risk info for ea. risk: Title or description of item or TASK at risk; Description of the RISK; Risk category or type; Initial assessment of Consequences, impact, or cost at risk; initial likelihood or probability; Initial risk score (consequence x likelihood); Risk handling CATEGORY; Risk handling / control / mitigation / action PLAN; Designation of risk "owner. Answer the majority of the questions. To earn 60-69% of the points available for this assignment – Identify at least 6 risks, including risks such as: the general ability to complete the project successfully; major tasks of different types and categories; sub-tasks of different types and categories; lowest level leaf node tasks or sub-sub tasks of different types and categories. Include risks such as: external risks, financial risks, organization risks, PM risks, quality risks, technical risks, and other risk categories. Includes only one of the risk handling categories (avoidance, mitigation, transfer, acceptance). Include much of the following risk info for ea. risk: Title or description of item or TASK at risk; Description of the RISK; Risk category or type; Initial assessment of Consequences, impact, or cost at risk; initial likelihood or probability; Initial risk score (consequence x likelihood); Risk handling CATEGORY; Designation of risk "owner. Answer the majority of the questions. Less than 60% Risk Registers that do not meet the requirements will earn a zero. WBSs that are not original work will earn a zero. WBS Task Name Outline Level 0 Team Delivery-IPT-3 0 0 Team Delivery-IPT-3 0 0 Team Delivery-IPT-3 0 1 1 Project Management 1.1 Project kickoff 2 1.3 Sign Off for Time and Materials Meeting 2 2 2.1 Design IT System Gather Requirements 1 2 2.1.1 Meet with Mama and staff/Get buy-In 3 2.1.2 Audit work processes 3 2.1.3 Optimize work processes 3 2.1.4 Review work processes 3 4 4.1.4 Ordering and Receiving Resources Install network equipment 1 3 4.1.4.1 Mount Network Rack 4 4.1.4.2 Rack firewall 4 4 4 4.1.4.3 Rack Switch 4 4 4.1.4.4 Mount APs 4 4 4.1.4.5 Cable Network Equipment 4 4 5 5.1 5.2 Software Domain Order Licensing for Azure Hosting Build Azure AD Domain 1 2 2 5.3 Configure Cloud DNS 5.4 Setup Laptop to Integrate to Domain 2 2 2 2 2 Risk Risk Risk Category Full Funding Unavailable from Client Financial, External $ 10,000.00 Client Inaccessible During Project External $ 10,000.00 Construction Delayed Project, External $ 10,000.00 Inability to define project objective, or scope Project $ 1,500.00 Client delays signing the Purchase Order Financial, External $ 1,500.00 Resistance from customer on project to provide details External, Organizational $ 1,000.00 Inability to articulate current business processes External, Organizational, Quality $ 1,500.00 Missing, or lack of clarity, on workflows External, Organizational, Quality $ 1,000.00 Disagreement of proposed workflows External, Project $ 1,500.00 Contractor unable to mount rack to wall External $ 250.00 Rack not ready Technical $ 250.00 Equipment not available External $ 150.00 No hardware to mount equipment Technical $ 250.00 Rack not ready Technical $ 250.00 Equipment not available External $ 150.00 No hardware to mount equipment Contractor unable to mount APs Technical External $ $ 150.00 250.00 Cables not available Technical $ 200.00 In wall cabling non-functional Technical $ 500.00 Pricing changes Technical resource unavailable to configure Financial, External Project $ $ 500.00 200.00 Consequences Unforseen technical challenges Technical resource unavailable to configure Unforseen technical challenges Technical resource unavailable to configure Wrong operating system to integrate with domain. Technical Project Technical Project Technical $ $ $ $ $ 100.00 200.00 100.00 200.00 100.00 $ 41,700.00 Risk Probability Risk Handling Initial Risk Score Category 10.00% $ 1,000.00 Accept 50.00% $ 5,000.00 Mitigate 20.00% $ 2,000.00 Transfer 25.00% $ 375.00 Accept 15.00% $ 225.00 Transfer $ - 10.00% $ 100.00 Accept 40.00% $ 600.00 Mitigate 30.00% $ 300.00 Transfer 50.00% $ 750.00 Accept 50.00% $ 125.00 Transfer 50.00% $ 125.00 Accept 30.00% $ 45.00 Mitigate 50.00% $ 125.00 Accept 50.00% $ 125.00 Accept 30.00% $ 45.00 Mitigate 20.00% 50.00% $ $ 30.00 125.00 Accept Mitigate 20.00% $ 40.00 Mitigate 10.00% $ 50.00 Transfer 15.00% 25.00% $ $ 75.00 50.00 Transfer Mitigate 50.00% 25.00% 50.00% 25.00% 20.00% $ $ $ $ $ 50.00 50.00 50.00 50.00 20.00 $ 11,510.00 27.60% Mitigate Mitigate Mitigate Mitigate Mitigate Mitigation Action Cancel Project Obtain multiple avenues to contact client, and be persistent. Inform client of dependency, and develop accelerate implementation/acceptance schedule. Extend discussion with client to understand the buiness. Explain to client impact of delay on project timeline. Ensure to listen to all concers, and address each. Schedule each person to be shadowed instead of verbal explaination. Articulate to customer workflows optimized only ones explained, or shadowed. During meetings have customer articulate need, and outcome from each workflow. Transfer work to a later date. Setup equipment w/o rack. Work with vendors to ensure availability, and shipping prior to ordering. Setup equipment w/o rack. Setup equipment w/o rack. Work with vendors to ensure availability, and shipping prior to ordering. Setup equipment w/o rack. Confirm availability of contractor prior to date of installation Have backup local source of cables available. Have test, and acceptance, 2 weeks prior to installation. Obtain BOM from vendor to lock in pricing. Have backup resource identified to perform work. Ensure support from vendor is purchased. Have backup resource identified to perform work. Ensure support from vendor is purchased. Have backup resource identified to perform work. Have project admin confirm desired PC specs before ordering. Contingency Plan Risk Owner Cancel the project and go find more work. Be persistent to contact the client, and reiterate the importance of communication. Explain to the client the risk it out of Team Delivery's hands, and project extensions are possible. PM Continue talking with the client to obtain clarity about the specifics for the project. Articulate the timing of the project will change if the contract is not signed promptly. The PM will have to perform a deep dive on each area of concern to determine if the concern will affect the project. PM PM PM PM PM Each individual who audits each area will have to listen, and ask probing PM, Project Admin, questions to ensure workflow accuracy. Business Analyst Discuss with customer that if information was withheld, or forgotten, it would impact analysis. PM, Project Admin, Business Analyst Talk through each workflow verbally, and graphically. Have customer signoff on each workflow. PM Contractor can mount at a later date. PM Obtain downtime after open to install equipment. Network Engineer Use temporary equipment from Team Delivery to setup the business, and PM, Network install ordered equipment at a later date. Engineer Obtain downtime after open to install equipment. Network Engineer Obtain downtime after open to install equipment. Network Engineer Use temporary equipment from Team Delivery to setup the business, and install ordered equipment at a later date. Obtain downtime after open to install equipment. Have a list of contractors from prior jobs avaible. PM, Network Engineer PM PM Order cables from local vendor which can be obtained same day. Project Admin Use temporary run cables in ceiling until cabling can be fixed. Network Engineer Hold vendor accountable for pricing change. Have a list of contract IT resources that can be used. PM PM Call vendor support for technical issues. Have a list of contract IT resources that can be used. Call vendor support for technical issues. Have a list of contract IT resources that can be used. Work with equipment vendor to obtain correct OS. System Admin PM System Admin PM System Admin Est. Cost of Remaining Remaining Mitigation Action Probability Consequences $ 1,500.00 Final Risk Score 10.00% $ 500.00 $ 50.00 25.00% $ 1,500.00 $ 375.00 10.00% $ 1,000.00 $ 100.00 $ - $ 200.00 10.00% $ 150.00 $ 15.00 $ 125.00 5.00% $ 100.00 $ 5.00 $ 375.00 5.00% $ 500.00 $ 25.00 $ 1,200.00 15.00% $ 750.00 $ 112.50 $ 1,500.00 20.00% $ 500.00 $ 100.00 $ 1,250.00 25.00% $ 750.00 $ 187.50 $ 750.00 20.00% $ 25.00 $ 5.00 $ 750.00 20.00% $ 25.00 $ 5.00 $ 1,200.00 15.00% $ 100.00 $ 15.00 $ 50.00 15.00% $ 250.00 $ 37.50 $ 500.00 20.00% $ 250.00 $ 50.00 $ 1,000.00 15.00% $ 100.00 $ 15.00 $ $ 35.00 1,000.00 10.00% 20.00% $ $ 100.00 100.00 $ $ 10.00 20.00 $ 17.50 5.00% $ 200.00 $ 10.00 $ 25.00 5.00% $ 500.00 $ 25.00 $ $ 50.00 50.00 5.00% 10.00% $ $ 500.00 200.00 $ $ 25.00 20.00 $ $ $ $ $ 70.00 50.00 70.00 50.00 50.00 $ 11,867.50 28.46% 20.00% 10.00% 20.00% 10.00% 15.00% $ $ $ $ $ 100.00 200.00 100.00 200.00 100.00 $ $ $ $ $ 20.00 20.00 20.00 20.00 15.00 $ 8,800.00 $ 21.10% 1,302.50 3.12% Mamma Mia’s Bakery Project Team Charter Group A: Team ATLAS TTP – 2 Project Charter IFSM – 438 Information Systems Project Management University of Maryland Global Campus March 31, 2021 Team Members: Robert Hill Gregory Nitch Victorien Singhe Sandra Carey Marise Arroyo Milton Tanjong Team Atlas Project Charter Executive Summary The Mamma Mia’s bakery project charter will be conducted by team Atlas. Team Atlas is self-managing and cross-functional team that delivers high quality working software to clients incrementally. This project covers the installation of a new IT system that will support the expansion of Mamma’s Bakery and Sandwich Shoppe. The main customer is Mamma Mia who the owner of the business and one of the stakeholders. The primary objective of this project is to install an IT system that will help facilitate the growth of Mamma’s Bakery and Sandwich Shoppe. As the business attempts to scale, the existing hard copy system of record keeping will become more and more difficult to manage and that is where this IT system comes in. It will add value by creating a better way of recording and managing information that is needed for operating the business. The scope of the project is to provide Mamma Mia’s Bakery and Sandwich Shoppe with Information Technology (IT) capabilities which include point-of-sale, inventory, and for bookkeeping purposes. Additionally, employees at the bakery will use the system to connect to Mamma Mia’s suppliers, the health department for food services, and other business relationships. Furthermore, the system will have a website which connects to an Internet presence and so Mamma Mia’s customers can make advance orders for pick-up. Additionally, the system will have the capability to process debit and credit cards. Furthermore, in considering all the requirements and task of this project, the estimate is $105,000.00 dollars. The schedule of this project will depend on the reconstruction and new reconfiguration of the bakery. The estimate of the project would be six months for total completion. The project charter also gives a preliminary delineation of roles and responsibilities of the team members. The Project management Leads in the planning and development of the project; manages the project to scope. Responsibilities include develop the project plan; identify project deliverables; identify risks and develop risk management plan. Page 2 of 10 Team Atlas Project Charter A. General Information Project Title: Brief Project Description: Prepared By: Date: Mamma’s Bakery and Sandwich Shoppe IT System Development This project covers the installation of a new IT system that will support the expansion of Mamma’s Bakery and Sandwiche Shoppe. Gregory Nitch, Marise Arroyo, Milton Tanjong, Robert Hill, Sandra Carey, Victorien Singhe 1.3 Version: March 30, 2021 Customer and Stakeholders: Identify the customer/user/client. Who are the internal and external stakeholders and their influences or interest in this project? The customer for this project is Mamma Mia, the owner of the business. Mamma Mia is also an internal stakeholder along with all her current and new employees. External stakeholders include everyone being contracted to develop and implement the new IT system. As far as interest and influence goes, Mamma Mia has the greatest interest in seeing that the project is a success since it directly impacts her ability to execute on business objectives, and therefore, she will influence how the IT system will support those business objectives. The team developing and implementing the IT system also has a strong interest in seeing the project be successful as it reflects on their business, and the team influences the technical details of how the system will operate in order to ultimately support the business. B. Project Objective: The primary objective of this project is to install an IT system that will help facilitate the growth of Mamma’s Bakery and Sandwich Shoppe. As the business attempts to scale, the existing hard copy system of record keeping will become more and more difficult to manage and that is where this IT system comes in. It will add value by creating a better way of recording and managing information that is needed for operating the business. On top of that, the IT system will support the current business priorities of expanding the staff to include four additional employees and expanding the product offerings to include additional sandwiches and bakery items. The deliverables for this project will include the software and hardware necessary for the function of components such as the desired point-of-sale, inventory, and bookkeeping systems. Benefits from these deliverables will be realized when the existing processes are migrated to the new IT system and the resulting time savings and improved ability to ingest and manage larger amounts of information are seen. Page 3 of 10 Team Atlas Project Charter C. Assumptions List and describe the assumptions made in the decision to charter this project. Please note that all assumptions must be validated to ensure that the project stays on schedule and on budget. It is assumed that Mamma Mia wishes to have all business faculties connected via software, this includes human resources, financing, supply management, customer servicing, and inventory management. By tying these systems together with digital integration, the increased efficiency being sought after can be obtained (Amy Cook, 2017). In addition, it is also assumed that all hardware to fulfill the project’s objectives will be procured and installed as part of the project. This is because without the proper hardware to operate the new IT system then it will be rendered useless to the customer. This system will need to be secure to prevent privacy concerns for both customers and employees. This constraint is significant for both customer and employee relationships and legal concerns. It is also assumed that information such as inventory and business information will need to be migrated from the old hard copy system. This will ensure continuity of operations during and after change over to the new IT system. Furthermore, it is assumed that personnel will need to be properly trained on the use of the system. Without proper skills to manipulate the new IT system continuity of business operations will be affected. Another assumption is that an information back up will need to be included in the project. With an information backup system, the store will be able to react to and or recover from natural disasters or other contingencies (IBM Services, 2020). Finally, it is assumed that an internet service provider will need to be obtained to support the new IT system and website. Without internet the system will not be able to operate as desired. Page 4 of 10 Team Atlas Project Charter D. Project Scope Describe the scope of the project. The project scope establishes the boundaries of the project. It identifies the limits of the project and defines the deliverables. • Obtain Internet Service Provider (ISP) and install a Local Area Network (LAN). • Install an IT system that focuses on point-of-sale, inventory, and bookkeeping systems. • Install new point-of-sale systems, computers, a wireless capable router, and run fiber-optic cabling. • Obtain a Software as a Solution (SaaS) provider to provide a business software. • Connect Mamma with suppliers, health department, and other business relationships using the SaaS. • Point-of-sale will include credit/debit card processing. • Train employees on new system and software. Create and Implement new website for online ordering. List any requirements that are specifically excluded from the scope. • • Hiring of additional employees. ISP running network to Mamma’s building. E. Project Milestones . Milestones Initiation of Project Approval – Submission and approval of Project Plan to begin work. Funding – Verify funding for labor, hardware, resources and contingency allotment. Installation – Installation of LAN, Wi-Fi, Point of Sale System (POS), Hardware, & Software/Applications. Testing – Verify uptime of network, transactions for POS and installed applications Stand up website for online transactions. Quality Assurance (QA) Plan Deliverables Project Charter Signed Project Charter & Project Plan Date 3/29/2021 4/05/2021 Provide cost estimates on resources and materials. Submit a proposed budget for approval Install all network and hardware related equipment. Setup software applications and define configuration management plan. Testing of network connectivity, uptime, review logs & network security posture. Design and publish Mamma Mia’s online website with online transaction capability. Verify testing has been completed, website is reachable, usable, and 4/19/2021 5/17/2021 5/24/2021 5/31/2021 6/7/2021 Page 5 of 10 Team Atlas Project Charter User Acceptance and Usability Deployment Project Close Out validate testing results. Implement any changes/feedback to the system needed prior to production. QA review is completed. Ensure staff is trained on the applications, bookkeeping, point of sale system, and website. Establish support plan for any IT related issues or troubleshooting. IT solution goes live and into production for Mamma Mia’s bakery and solution is monitored for success. Verify project meets the needs and requirements of the stakeholder. Close out is approved. 6/14/2021 6/21/2021 6/28/2021 F. Impact Statement List the impact this project may have on existing systems or units. . Potential Impact Systems / Units Impacted Extra work related to data migration Training required to operate new systems Online orders disrupting normal orders New system incompatibility with suppliers Supply, Inventory, Finances Supply, Inventory, Finances, Services Services Supply, Inventory Page 6 of 10 Team Atlas Project Charter G. Roles and Responsibilities Describe the roles and responsibilities of project team members followed by the names and contact information for those filling the roles. Sponsor: Provides overall direction on the project. Responsibilities include approve the project charter and plan; secure resources for the project; confirm the project’s goals and objectives; keep abreast of major project activities; make decisions on escalated issues; and assist in the resolution of roadblocks. Email / Phone Name rhill95@student.umgc.edu Robert Hill Project Manager: Leads in the planning and development of the project; manages the project to scope. Responsibilities include: develop the project plan; identify project deliverables; identify risks and develop risk management plan; direct the project resources (team members); scope control and change management; oversee quality assurance of the project management process; maintain all documentation including the project plan; report and forecast project status; resolve conflicts within the project or between cross-functional teams; ensure that the project’s product meets the business objectives; and communicate project status to stakeholders. Email / Phone Name gnitch@student.umgc.edu Gregory Nitch Victorien Singhe vsinghetakougoum@student.umgc.edu Team Member: Works toward the deliverables of the project. Responsibilities include: understand the work to be completed; complete research, data gathering, analysis, and documentation as outlined in the project plan; inform the project manager of issues, scope changes, and risk and quality concerns; proactively communicate status; and manage expectations. Email / Phone Name scarey13@student.umgc.edu Sandra Carey Milton Tanjong mtanjong@student.umgc.edu Customer: The person or department requesting the deliverable. Responsibilities include: partner with the sponsor or project manager to create the Project Charter; partner with the project manager to manage the project including the timeline, work plan, testing, resources, training, and documentation of procedures; work with the project team to identify the technical approach to be used and the deliverables to be furnished at the completion of the project; provide a clear definition of the business objective; sign-off on project deliverables; take ownership of the developed process and software. Email / Phone Name stephany.head@faculty.umgc.edu Stephany Head Subject Matter Expert: Provides expertise on a specific subject. Responsibilities include: maintain up-to-date experience and knowledge on the subject matter; and providing advice on what is critical to the performance of a project task and what is nice-to-know. Email / Phone Name marroyo5@student.umgc.edu Marise Arroyo Page 7 of 10 Team Atlas Project Charter H. Resources Identify the initial funding, personnel, and other resources committed to this project by the project sponsor. Resource Project Budget Project Team Constraints $105.000 6 personnel I. Project Risks Identify the high-level project risks and the strategies to mitigate or avoid them. Risk Cost/Budget Timeline/Schedule Connectivity Loss of Resources Scope Creep Mitigation Strategy Advance planning of budget to include labor costs, supplies, equipment, & contingency allotment. Require project manager to monitor timelines and bottom line throughout the project lifecycle. Establish weekly status call to ensure all components of the project are on target for the outlined due dates and all deliverables are on schedule. Verify through testing that the uptime for the network connection is acceptable at the bakery and ensure there is a failover in place in case of an internet outage. Ensure critical documents and project plans are accessible to the entire team in case of any unforeseen turnover or key personnel leaving the project. Establish a communication plan and reoccurring touch points throughout the duration of the project. Establish clear benchmarks, tasks, dates and milestones. Allow adequate communication with the stakeholder to confirm the project is in scope and within the requirements of the project plan/sow/charter. J. Success Measurements What are the high-level benefits of this project? Identify metric and target you are trying to achieve as a result of this project. For example, overall cost savings of $50K or reduce processing time by 25 percent. There are 3 high level benefits expected to be produced by project completion. These high-level benefits are as follows, increased efficiency, increased customer base, and Page 8 of 10 Team Atlas Project Charter business continuity. “Integrating a company’s ERP and CRM, for example, allows important data to flow, and gives your business the insight to meet customer demands more efficiently” (Anna Kinnear, 2018). Since all business processes at the store are done by hand it is estimated that there will be an efficiency increase of at least 20%. Furthermore, a website will contribute to additional revenue for the business, in fact Kasey Kaplan argues that most customers will visit a business’s website prior to making a purchase (2020). It is estimated that the new store website will contribute to at least 10% more in sales within the first 6 months. Finally, a data backup will protect business information in the event of a contingency. This is important because more than half of businesses are subject to attacks or disasters, with 20% losing up to 20% of their customers because of it (Arconis, n.d.). By establishing a data backup, business operations will be able to resume almost immediately after an event. Page 9 of 10 Team Atlas Project Charter K. Signatures The signatures of the people below document agreement and approval of the formal Project Charter. The project manager is empowered by this charter to proceed with the project as outlined in the charter. This charter will be: Customer: Name Signature MMIA Mama Mia Date 5/5/2021 Project Sponsors: Name Signature Robert Hill Robert Hill Date 5/5/2021 Project Manager: Name Signature Date Gregory Nitch Gregory Nitch 5/5/2021 Victorien Singhe Victorien Singhe 5/5/2021 L. References Arconis. (n.d.). Why data backup is important for your business. Retrieved from https://www.acronis.com/en-us/articles/data-backup-for-business/ Cook, A. O. (2017, October 31). 6 ways to make your business more efficient. Retrieved from https://www.entrepreneur.com/article/292833 IBM Services. (2020, November 25). What is a business continuity plan? Retrieved from https://www.ibm.com/services/business-continuity/plan Kaplan, K. (2020, February 3). Why every business needs a website. Retrieved from https://www.forbes.com/sites/theyec/2020/02/03/why-every-business-needs-awebsite/?sh=2912e27b6e75 Kinnear, A. (2018, November 28). Four ways your business can benefit from digital integration. Retrieved from https://www.commercient.com/four-ways-yourbusiness-can-benefit-from-digital-integration/ Page 10 of 10 ID WBS 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Task Mode 1 1.1 1.1.1 1.1.1.1 1.1.1.2 1.1.1.3 1.1.1.3.1 1.1.1.3.2 1.1.1.3.3 1.1.1.3.3.1 1.1.1.3.3.2 1.1.2 1.1.2.1 1.1.3 1.1.3.1 1.1.3.2 1.1.3.3 1.1.4 1.1.4.1 1.1.4.2 1.1.4.2.1 1.1.4.2.2 1.1.4.2.3 Project: TTP3 Date: Wed 5/5/21 Task Name Apr 25, '21 S M T W T F S May 2, '21 S M Mama Mia’s Bakery Project Initiation of Project Meet with stakeholders Review requirements Confirm deliverables Establish meeting schedule Weekly status report Discuss project status Establish bi-weekly meeting Meet on Mondays and Fridays Meet for 1 hour duration Establish budget Provide cost estimate Approval Submission of project plan Approval of project plan Approval of budget allocation Funding Verify funding for labor Verify funding for hardware Conduct market research for fixed price Obtain cost estimates Order hardware 4/27 Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 1 T W T F S S ID WBS 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 Task Mode 1.1.4.3 1.1.4.3.1 1.1.4.3.2 1.1.4.4 1.1.4.4.1 1.1.4.4.2 1.1.5 1.1.5.1 1.1.5.2 1.1.5.2.1 1.1.5.2.2 1.1.5.2.3 1.1.5.2.4 1.1.5.2.5 1.1.5.2.5.1 1.1.5.2.6 1.1.5.3 1.1.5.4 1.1.5.5 1.1.5.5.1 1.1.5.5.2 1.1.5.6 1.1.5.7 Project: TTP3 Date: Wed 5/5/21 Task Name Apr 25, '21 S M Verify funding for resources Conduct market research for fixed price Obtain cost estimates Verify funding LAN/Wifi Internet Connection Conduct market research for fixed price Select vendor Installation Receive HW/Networking Equipment Install LAN connection Prepare contract with vendor Schedule onsite installation Design network configuration Run fiber optic cabling Setup wireless routers Configure Wireless Network Setup modem Setup Hardware Printers Mobile Devices Smartphone (three iPhones) Tablets (four iPads) Laptop PC Select SaaS Product T W T F S May 2, '21 S M 4/27 4/27 Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 2 T W T F S S ID WBS 47 48 49 50 51 55 56 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 Task Mode 1.1.5.7.1 1.1.5.7.1.1 1.1.5.7.1.2 1.1.5.7.1.3 1.1.5.7.1.4 1.1.5.7.1.5 1.1.5.8 1.1.5.9 1.1.5.10 1.1.6 1.1.6.1 1.1.6.2 1.1.6.2.1 1.1.7 1.1.7.1 1.1.7.2 1.1.7.3 1.1.8 1.1.8.1 1.1.8.2 1.1.8.3 1.1.8.3.1 1.1.9 Project: TTP3 Date: Wed 5/5/21 Task Name Apr 25, '21 S M T W T F S May 2, '21 S M Define requirements of SaaS Point of Sale System Database capability Inventory System Payroll Ordering System Conduct market research Select top SaaS contender Stakeholder Approval of SaaS Install SaaS on Hardware Sign contract Establish IT support Establish 24 hour helpdesk support Testing Verify Uptime of Network Test transactions on POS Test Installed Software Stand up website Design Website Build Webiste Setup online transaction capability Update Inventory Daily Quality Assurance (QA) Plan Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 3 T W T F S S ID WBS 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 Task Mode Task Name Apr 25, '21 S M 1.1.9.1 1.1.9.1.1 1.1.9.2 1.1.9.2.1 1.1.9.3 Verify all testing is complete Implement any changes necessary Verify Website is reachable Implement any changes necessary Verify Orders can be placed on website 1.1.9.3.1 1.1.10 1.1.10.1 1.1.10.2 1.1.10.3 1.1.10.4 1.1.11 1.1.11.1 1.1.11.2 1.1.11.3 1.1.12 1.1.12.1 1.1.12.1.1 1.1.12.1.2 1.1.13 Implement any changes necessary User Acceptance and Usability Train Staff on Software Applications Train Staff on Payroll and Inventory system Train staff on POS system Train staff on Website Deployment LAN is running for full access to all IT assets Making sure SaaS is up and running Checking if Website is Live Project Close Out Stakeholder Meeting Verify Needs have been Met Final approval for project close out Grand Re-Opening Project: TTP3 Date: Wed 5/5/21 T W T F S May 2, '21 S M Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 4 T W T F S S May 9, '21 S M T Project: TTP3 Date: Wed 5/5/21 W T F S May 16, '21 S M T W T F S May 23, '21 S M T W T F S May 30, '21 S M Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 5 T W T F S May 9, '21 S M T Project: TTP3 Date: Wed 5/5/21 W T F S May 16, '21 S M T W T F S May 23, '21 S M T W T F S May 30, '21 S M Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 6 T W T F S May 9, '21 S M T Project: TTP3 Date: Wed 5/5/21 W T F S May 16, '21 S M T W T F S May 23, '21 S M T W T F S May 30, '21 S M Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 7 T W T F S May 9, '21 S M T Project: TTP3 Date: Wed 5/5/21 W T F S May 16, '21 S M T W T F S May 23, '21 S M T W T F S May 30, '21 S M Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 8 T W T F S