Individual Assignment CMGT 545 Week 3 Flowchart

Individualassignmentcmgt545week3zipcmgt545flowchartpdfindividualassi

The flowchart is representing the process of the migration and the implementation process of the company because the company is focusing to migrate its current applications such as the customer relation service as well as the payroll management application on the cloud based applications. The need to migrate the application was required because the company wants to secure the data and the chief executive of the company knows well that it can effectively save the resources, time as well as monetary resources in the future.

In this section, it is discussed about the flow chart process or the comprehensive summary. The flowchart has the seven phases in which the development team must take some most important actions. The flowchart starts with the scoping and planning of the project, If the team is not performed any kind of scoping or they do not plan for the project, then they should also take start from scoping and planning. In short, they must plan again. When they complete their plan, then they jump into the second phase where they must order/install the equipment.

If they have no equipment, they will order first but if they have the equipment, then they will install them at all. In the third phase, they will install successfully and then test the software. The same scenario is also repeated in this phase. In the next phase, the software will be tested. If the software is not tested, it will go back to the installation phase.

When the software will be tested, then the training on the new software will be started and all the employees will be trained. In this step, the management will be included especially for effective management. Furthermore, the management team will train the employees in the company and the developers will be again focusing on the next phase which is implementation. The process will be rolled out in case of not implementation. After successful implementation, the development team will effectively evaluate the migration of the system and will hand over to the company CEO.

IntuitCloudSystemMigration TeamProjectWeek3.pdf CMGT/545 v1

The C-suite at Intuit, Inc. wants to convert their system to a cloud-based system in a 12-month project with a budget of $1,000,000. As either an IT team member or a c-suite level manager, you have been appointed to the Cloud-Based Applications Project Team. Conduct a project stakeholder meeting to determine the project scope, budget, and timeline for converting the company’s system to a cloud-based system. Include at least 4 milestones in your timeline.

One person from the IT group should facilitate the conversation.

Section 1: Summary

Intuit, Inc has decided to move forward with transitioning to a cloud-based system to better assist our customers. The cloud-based system is technologically forward as it allows our company to respond to our clients immediately with the services needed instead of by a remote server. Intuit attempts to make this 12-month conversion as seamless as possible. Our objective is to determine if a third party should be used or with the help of our IT professionals, determine if we should have our own personal cloud.

With our budget of 1,000,000, we plan to maximize the use of this money without utilizing the entire amount. Both C-Suite and the IT professionals are in agreement with safety measures, so our cybersecurity needs will probably utilize a large portion of our budget. Our IT professionals suggest that a third-party should be used due to security, but that causes a conflict with the desires of C-Suite because they would like the option to lock down the system at their discretion. When purchasing a product from a third party, there are very little modifications that can be done regarding privacy. For the software products wanted by C-suite that can be transformed over the span of 5-10 years, we need to ensure the third party can adjust and add services as needed.

Satisfaction can be determined through various methods, including surveys (internal and external), questionnaires, and welcoming feedback from the IT team. The IT professionals will be in direct support of the product and will interact with customers, thus having more hands-on experience with issues arising during the conversion. The criteria to judge success include profit metrics—such as whether the company is making more money, gaining a larger customer base, receiving referrals, or losing loyal customers. Additional considerations involve researching companies offering a broad product variety, enterprise licenses, and conducting cost analyses for quality, manpower, and security needs.

This project differs from others primarily because of its larger budget and the focus on a conversion process rather than a simple migration. If the company opts for its own cloud, the product should be individualized to fit the specific needs of Intuit, Inc., with comparable control capabilities as major providers like Amazon, Google, or Microsoft—allowing the company to manage access, shut down systems when necessary, and customize functionalities.

Section 2: Phasing

The cloud project comprises eight phases planned over ten weeks, which include:

- Phase I: Vendor Evaluation, Scope Service, Contract, Pricing, Support (Weeks 1-3)

- Phase II: Spin Up Cloud Server, Create Firewall Rules, Sandbox Software (Weeks 2-4)

- Phase III: Implement Testing and Staff Training (Weeks 3-4)

- Phase IV: Roll Out to Production (Weeks 4-5)

- Phase V: Post Implementation (Weeks 3-6)

- Phase VI: Implementation and Rollout (Weeks 5-6)

- Phase VII: Evaluation and Post Implementation (Weeks 7-8)

Three teams will be involved: C-suite, IT, and a combined team for rollout. Phase VII’s duration ensures adequate time for user feedback, testing, and system performance review.

Section 3: Schedule – Milestones

The timeline involves a structured plan to transition from the current in-house data system to a cloud-based system within 12 months, with key milestones such as completing vendor evaluation, initiating server setup, completing staff training, and final deployment. The IT project manager will report directly to the C-suite on any changes.

Section 4: Resources

Resources include:

- Cloud contracts and licenses

- Access to Windows Azure and Palo Alto hardware

- Procurement of engineering computers and network switches

- User training sessions and SOP documentation

- Personnel such as project manager, cloud engineers, cloud manager, and support staff

Constraints encompass hiring and onboarding qualified staff, procurement lead times, hardware upgrades, training resources, and potential delays or budget fluctuations affecting implementation.

Section 5: Organization

Key roles include:

- Project Manager (Wilson): Oversees planning, staffing, and communication

- Project Sponsor (Tiffani): Approves budget, goals, and resource allocation

- Team Members: Contribute operational expertise

- Team Lead: Manages specific activities and communicates with the project manager

- Executive Sponsor: Responsible for high-level approval

- Business Analyst: Ensures requirements are met, verifies deliverables, and conducts testing

Section 6: Change Management

Effective change management involves reviewing requests, updating configurations, and obtaining approval from the Change Management Board. Once approved, technical teams implement the changes, followed by security and compliance checks to ensure system integrity.

Section 7: Risk Management

Risks include data loss with third-party or in-house clouds, employee adaptation issues, budget constraints, communication failures, delays, and storage costs. Each risk is associated with roles responsible for mitigation strategies such as backups, training, clear communication, and budget planning.

References

  1. Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. John Wiley & Sons.
  2. PMI. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th Edition). Project Management Institute.
  3. Schwalbe, K. (2018). Information Technology Project Management. Cengage Learning.
  4. O'Brien, J. A., & Marakas, G. M. (2011). Management Information Systems. McGraw-Hill Education.
  5. Turban, E., Pollard, C., & Wood, G. (2018). Information Technology for Management: Digital Strategies for Insight, Action, and Sustainable Performance. Wiley.
  6. Fitzgerald, B., & Stol, K. (2017). Continuous Software Engineering: A Roadmap and Agenda. Proceedings of the IEEE, 105(11), 2305-2323.
  7. Gartner Research. (2022). Cloud Computing Adoption Framework. Gartner Inc.
  8. IBM. (2023). Cloud Security Best Practices. IBM Security Journal.
  9. McAfee, A. (2019). Enterprise Security: Protecting Your Business from Cyber Threats. Wiley.
  10. Reding, P. (2017). Managing Change in Organizations: A Practice Guide. PMI.

Related Assignments