Management Mgt 4100 Management Information Systems Mis Busin

Management Mgt 4100management Information Systems Misbusiness Case

Management (MGT) 4100 Management Information Systems (MIS) Business Case Instructions The business case study will include four submissions. The first submission will be selecting a topic based on an IT-based challenge that you have personally experienced at home, work or school. The topic submission will include on paragraph (minimum of five sentences) detailing the problem and will be due on the last day of Module 1 at 11:59pm. The second submission will be an essay (minimum of two pages) including a refinement of the topic problem as well as three possible solutions to resolve the problem. The essay will be due on the last day of Module 2 at 11:59pm and will include a minimum of three properly formatted APA references with in-text citations, one supporting each of the possible solutions. The third submission will be a full draft (according to the Final Project Template ) of the final business case study. The draft submission will incorporate instructor feedback from the previous essay and will be due on the last day of Module 3 at 11:59pm. The fourth and final submission will be the final product incorporating instructor feedback from the previous draft, have a minimum of 10 pages and 10 references with in-text citations (APA formatting), and will be due on the last day of Module 4 at 11:59pm. The value of submissions: topic submission is worth 5 points, essay is worth 20 points, draft of business case study is worth 25 points, and the final business case study is worth 100 points. The Business Case Study is worth 150 points overall.

Paper For Above instruction

The assignment for this course involves developing a comprehensive business case study centered around an IT-based challenge experienced by the student. This multi-phased project aims to guide students through identifying a real-world issue, analyzing potential solutions, and refining their approach to present a well-structured final report. The process begins with selecting a relevant IT challenge from personal experience, fostering engagement and contextual understanding. The initial topic submission requires a concise paragraph, outlining the core problem with clarity and relevance. This step sets the foundation for subsequent analyses.

Next, students will expand upon their initial problem statement by composing a two-page essay that refines the problem's scope and introduces three feasible solutions. Each solution must be supported by at least one credible APA-formatted reference with in-text citations, ensuring academic rigor and evidence-based reasoning. This stage encourages critical thinking and comparative analysis of different approaches to address the identified issue. Feedback from the instructor on this essay will inform revisions for the subsequent draft, which must be aligned with a specific project template. The draft serves as an intermediate step, integrating instructor suggestions to enhance clarity, depth, and coherence.

The culmination of this process is a final business case study, which must be at least ten pages in length and include a minimum of ten scholarly or credible references formatted according to APA standards. This comprehensive report should synthesize all previous work, demonstrating thorough analysis, well-justified solutions, and academic credibility. Throughout the project, students will demonstrate their ability to connect theoretical concepts from management information systems with practical application, culminating in a persuasive, well-organized business case.

Effective project management strategies, including accurate estimation of project times and costs, play a crucial role in the successful execution of the final report. Understanding the factors influencing estimate accuracy, applying top-down and bottom-up methods, and refining estimates based on project scope and complexity are essential skills. Addressing the challenges of large-scale projects, such as mega projects, requires additional considerations like risk assessment and reference class forecasting, ensuring realistic planning and resource allocation.

References

  • Meredith, J. R., & Mantel, S. J. (2017). Project Management: A Managerial Approach (9th ed.). Wiley.
  • Kerzner, H. (2013). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (11th ed.). Wiley.
  • PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute.
  • Fleming, Q. W., & Koppelman, J. M. (2016). Earned Value Project Management (4th ed.). Taylor & Francis.
  • Ahlemeyer-Stubbe, A., & Baum, S. (2016). Managing Mega Projects. Journal of Business and Technology, 35(4), 201-213.
  • Flyvbjerg, B. (2014). What You Should Know About Megaprojects and Why: An Overview. Project Management Journal, 45(2), 6-19.
  • Lyons, T., & Low, S. (2020). Cost Estimation Techniques in Project Management. International Journal of Project Management, 38(3), 231-245.
  • Standish Group. (2015). CHAOS Report: Causes of Project Success and Failure. Standish Group Report.
  • Winston, W. L. (2014). Microsoft Excel Data Analysis and Business Modeling. Pearson.
  • Hwang, B., & Ng, T. (2016). Project Management Knowledge and Skills for Sustainable Construction. Journal of Cleaner Production, 135, 1-20.

Related Assignments