MKTwain - CMGTCB-555 - Competency 1 Reflection

.docx

School

University of Phoenix *

*We aren’t endorsed by this school

Course

555

Subject

Management

Date

Feb 20, 2024

Type

docx

Pages

Uploaded by PrivateOtterPerson4789

Mark Twain CMGTCB/555 – Competency 1 Reflection System Development Life Cycles (SDLC) have been used in all types of business and organizations, as well as for personal projects or plans. SDLCs were certainly used for projects before SDLCs were a concept, as these are planning and implementation stages of mostly anything that needs to be produced, created or implemented. When methodologies were finally a concept to aid in the implementation or production of something, they were first used in the production or construction industries. The first methodology to be a concept was the Waterfall, which has specific steps that must be taken in order to reach a result. This methodology works well if the result is always expected to be the same, such as in the mass production of appliances, furniture, cars, toys, etc. or in the construction of something like sheds, garages, manufactured homes and model homes. An organization whose primary business is in manufacturing products for mass retail purposes would favor the Waterfall SLDC because it is a defined process to develop those products. A more recent methodology to enter the SDLC arena is the Agile, this newer concept came about when looking to achieve different processes to meet a result, but with more input from various lines of thoughts, not just a cookie-cutter development process. Agile allows for a more free-thinking approach to reaching a result because not all end results are desired to be the same, Agile is more flexible and involves a collaborative effort. The Agile SLDC will be favored by an organization that looks to empower their employees to bring various experiences and backgrounds to develop ideas. Both of these methodologies may be used by the same organization; however, they will possibly be used in different business units. For example, Agile may be used in a business unit of an organization that operates a think tank to develop the new mobile device to blow the current industry out of the water. Once the final idea prototype has been designed, developed and ready for implementation, it will follow production steps designated in a Waterfall methodology. Thinking back to a recent project at my current organization, we upgraded to an interactive classroom by updating teacher workstations to those that have the capability to use touchback from the new interactive flat panel screens that replaced chalkboards. During the research and planning stage of what interactive flat panel we would choose, as well as what workstation would support our plan, we sat around and used ideas from everyone on what route to take. We first began with the idea of a mobile device, such as a touchscreen laptop to use with the panels, but we had to change this due to cost and availability of 500+ touchscreen laptops during an electronics shortage caused by COVID and getting the classrooms ready by the new school year. The decision to go with laptops was made in December of 2019, quotes were being requested, budgeting was being allocated, then three months later COVID threw a wrench in that engine. Worldwide electronics shortages would mean we would have classrooms without a workstation that would work with our interactive flat panels if we went with a touchscreen laptop solution. We ordered desktop computers that would respond to the touch input from the flat panels we ordered to mount in the classroom. Had we not used the Agile method, we would have had to start all over with the planning of the new interactive classroom.

Although the planning, acquisition, and implementation of the devices we selected had room for change without drastically affecting the result, the installation of the devices and the preparation of the classrooms followed a well-defined plan. The installation plan was more along the line of the Waterfall method because there was little to no room for changes or one-offs. The well-written requirements gave instructions on each step of the installation project, beginning with wall preparation, from the removal of the old chalk and dry erase boards, to repairing the walls and painting them. Followed by the precise installation of electrical receptacles on the walls at specified heights and offset 8” from the center of the wall to accommodate the panel brackets that would be bolted on the walls. Once the panels were mounted, they would be joined to our network and the firmware updates pushed out along with the applications necessary for our classroom environment. Two key attributes to the well written requirements for this project were the clarity of what work needed to be done, and the instructions on precise measurements needed for the installation of electrical receptacles and panel mounts. These attributes impacted the quality of requirements because with any contractor that read the project plan and result, they would see that there was little to no room to deviate from the defined placement of electrical receptacles or conduits, otherwise the panel mounts would not be able to be placed on the wall by the installation contractor. Assessing the system requirements based on these attributes, I’d say that the Waterfall SDLC was the best decision for the installation portion of the project as it specifically outlined what needed to happen to make sure all panels were mounted in the same manner in time for updates and implementation with the classroom workstations.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version