MKTwain - CMGTCB-555 - Final Relection 05.23.23

docx

School

University of Phoenix *

*We aren’t endorsed by this school

Course

555

Subject

Management

Date

Feb 20, 2024

Type

docx

Pages

1

Uploaded by PrivateOtterPerson4789

Report
Mark Twain CMGTCB/555 – Final Reflection The use of either SDLC, Agile or Waterfall, will depend on what project an organization is looking to tackle. If it’s a project with a defined output, such as a production item that is always to be expected to be the same, let’s say a rugged case for the latest smart phone, then a waterfall approach may be simpler to implement. However, if the desired product is going to be an improvement on this design, then an Agile approach would be taken to develop it with improvements, and this would require collaboration from various parties to determine the new product and its capabilities or features. Various phases of the chosen SDLC are specific to the approach taken. Waterfall will have less phases, but with more defined documentation on what to do next in the phases. Under Waterfall, it will be difficult to go back and change the outputs in a phase once it has commenced. Any deviations from these phases may result in having to start over or retool the process, resulting in a different timeline and higher cost. In Agile phases, there is more room for change, and it is part of the process in order to make sure the customer’s desired outcome is on track. These phases are more with incremental applications that can be changed with low impact on the process in that milestone. Change management in my work environment can be applied to several processes, one most recent process with multi-factor authentication on our devices for both our Microsoft and Google platforms. Had we planned to implement multi-factor authentication on our own terms earlier on, we could’ve developed a process to deploy this and train users on how to properly set-up their authentication controls. What happened was we were reactive to the multi-factor authentication implementation on the Google side of our platform, we were forced to assist instructional staff on how to set this up to their devices. Many didn’t want to use their personal devices to authenticate a log in for their school-issued Chromebook or Chromebox. Some staff members used an authentic app that itself required MFA and ended up locking out their accounts. A few weeks later, when the MFA for Microsoft was going to be turned on, we had a bit more time to communicate this to instructional staff and prepare them for it, with weblinks to our knowledgebase and PDF instructions on how to troubleshoot after, if needed. This impact was noticeable in the attitude of our staff members who were appreciative of the fact that we tried to lessen the blow of a new process this time around. Throughout this whole course, many parts of the competencies helped me understand the needs for these types of systems analysis in my environment. I have handled several large-scale projects in my current organization, however, we have never done so with a detailed and well-defined project plan. Most of the projects have been reactive due to an issue that came up that we only found out was an issue when the problem surfaced and took down a key system in our network. Going forward when planning for future projects, in a proactive approach, utilizing the tools I’ve learned in this course, specifically coming up with a plan utilizing an Agile methodology. Have a well- defined approach and the collaboration from all of those affected will go far in the planning, implementation, and acceptance of a project.
Discover more documents: Sign up today!
Unlock a world of knowledge! Explore tailored content for a richer learning experience. Here's what you'll get:
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help