Tuesday, October 8, 2019

MGT 430 MIS Lesson 2 Case Study Example | Topics and Well Written Essays - 750 words

MGT 430 MIS Lesson 2 - Case Study Example One of the primary issues with the failing modernization program prior to review was a constant widening of project scope (aka creeping) that ultimately resulting in years of work and billions of dollars lost. By placing responsibility on many business units instead of the singular existing ITS department, these potential overruns would be avoided due to the increased and multi-focused scrutiny on project development. Another issue identified by the Oversight Board was the lack of trust between departments involved in the implementation and monitoring of this program. Again, involving many sections of the business will necessarily result in the need to establish an effective web of information, rather than the quarantined nature of the previous development committee. As mentioned above, placing responsibility for scope changes on business units would be desired due to the ability of each unit to focus on development as it impacts their specific unit. The variety of perspectives will necessitate the interaction of many sections, and should result not only in reduced overruns but also in trust growth within the company as they come to be better acquainted with the perspectives of each. Assigning these responsibilities to either the existing ITS, BSM, or Prime would result in the segregation of development from profit operations, and would reduce the likelihood of cooperation. Creating an environment of trust in any organization is an important but difficult task. In the college situation, the most effective approach would be similar to assign ownership and development responsibilities to as many sections of end-users as is possible (maximize without making it unmanageable). Including business units (departments), student committee(s), vendors, and the existing IT department instead of an isolated BSM type committee would necessitate interactions and exchanges of perspective throughout the system

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.