3 questions
4 days ago
60
inssweek8.docx
InsssummaryChapter14.docx
- insssummaryChapter13.docx
inssweek8.docx
Must be authentic answer each question at 400 words per questions with citations.
The questions below are based on the following three case studies of systems/services development initiatives. Apply the content of Chapters 13 and 14 (Laudon, Laudon, and Traver. Management Information Systems: Managing the Digital Firm, 18th Edition, Pearson, ©2026. ISBN-13: 9780138344245.), plus your own independent research into the concepts, notions, and theories in these two chapters to address these questions.
· Building digital ecosystems from within: A case from life insurance ( http://proxy-ub.researchport.umd.edu/login?url=https://www.proquest.com/abiglobal/scholarly-journals/building-digital-ecosystems-within-case-life/docview/3283145119/sem-2?accountid=28969 )
· Unraveling the generative mechanisms of smart technology and service design ( http://proxy-ub.researchport.umd.edu/login?url=https://www.proquest.com/abiglobal/scholarly-journals/what-lies-beneath-unraveling-generative/docview/2500442502/sem-2?accountid=28969 )
· A strategy for the implementation of standard data structures in financial management information systems ( http://proxy-ub.researchport.umd.edu/login?url=https://www.proquest.com/abiglobal/scholarly-journals/strategy-implementation-standard-data-structures/docview/2611021612/sem-2?accountid=28969 )
Questions:
1. Assess the management, organization, and technology factors that contributed to each organization’s pre- IT-initiative condition.
2. What were the key risk factors of each systems initiative? How well did each organization control, or plan to control, these risks? What would you have done additionally or differently to manage these risks?
3. How did each IT initiative help align the organization better with its goals? What business value was achieved in each instance? (You may apply one or more of the following concepts in your analysis for this question: Porter’s competitive forces model, the value chain model, synergies, core competencies, and network economics.)
InsssummaryChapter14.docx
Here is the summary of the content from Chapter 14: Making the Business Case for Information Systems and Managing Projects:
Opening Case Study
BigCommerce is a global e-commerce technology company providing a cloud-based SaaS e-commerce platform for B2C, B2B, and omnichannel solutions.
The platform includes features like online store design, catalog management, hosting, checkout, order management, reporting, and integration with third-party services.
BigCommerce offers development and professional services, including solutions architecting, data migration, and project management.
Previously, BigCommerce used spreadsheets, email, and collaboration tools like Google Drive and Google Docs for project management, which were insufficient for scaling and managing larger projects.
BigCommerce needed a project management tool to handle over 100 global projects, measure metrics, and manage customer interactions.
After evaluating several tools, BigCommerce chose Wrike for its comprehensive project management capabilities.
Wrike is an integrated SaaS tool available as a web-based tool and mobile app, supporting multiple languages.
Wrike helps coordinate projects across teams, provides visibility into project progress, resources, and costs, and improves accountability.
Wrike integrates easily with existing infrastructure and applications like Slack and Salesforce and supports both agile and waterfall project management approaches.
Using Wrike, BigCommerce improved project organization, communication with customers, reporting, and analytics, leading to better business decisions and cost predictions.
Wrike enabled BigCommerce to analyze team efficiency, improve "time to value," and enhance customer satisfaction.
Successful implementation of Wrike required changes to project management processes and attention to organizational change.
BigCommerce's management recognized the need for a new project management system to improve resource efficiency, collaboration, and project portfolio management.
14.1 Explain How to Build a Business Case
Projects and Information Systems: Projects are planned activities aimed at achieving specific business objectives. Information systems projects can involve developing new systems, enhancing existing ones, or upgrading IT infrastructure.
Business Case: A business case is a proposal seeking approval for an investment. It outlines the problem, analyzes costs, benefits, and risks, and justifies the proposed solution. It aligns the investment with the firm's strategic goals and overall information systems plan.
Factors in Business Case: Seven major factors to consider include:
Long-term strategic goals (e.g., lowering production costs, product differentiation, global expansion, competitive capabilities)
Improved decision making
Customer and supplier relationships
Survival (market requirements and ESG goals)
New products and services
Financial rationale
Alignment with the long-term IT plan
Information Systems Plan: This plan supports the overall business plan and includes:
Purpose and rationale
Current system state
New developments
Management strategy
Implementation plan
Budget
Plan Development: Typically overseen by the CIO and approved by the CEO and Board of Directors. It includes organizational goals, specific system projects, target dates, milestones, and key management decisions.
Inventory and Documentation: Firms need to inventory all information system applications, IT infrastructure, and information requirements. Metrics should be developed to quantify the value of improved decision-making.
Organizational Changes: The plan should describe necessary changes in management, employee training, business processes, and authority structures. The business case for a new system should show how it fits into this plan.
14.2 Describe Methods for Evaluating IT Investments
Portfolio Analysis:
Inventories all information systems projects and assets.
Evaluates projects based on risk and benefit, similar to a financial portfolio.
Focus on high-benefit, low-risk projects first, then high-benefit, high-risk projects.
Avoid low-benefit, high-risk projects; reconsider low-benefit, low-risk projects.
Scoring Models:
Useful for projects with multiple criteria.
Assigns weights to various features and calculates weighted totals.
Helps in reaching agreement on evaluation criteria.
Determining Solution Costs and Benefits:
Assess if the system is a good investment.
Tangible benefits can be quantified; intangible benefits may lead to long-term gains.
Total cost of ownership (TCO) includes all IT expenditure components.
Capital Budgeting Models:
Measure the value of long-term IT projects.
Calculate all costs and benefits to determine financial worth.
Principal models: payback method, ROI, NPV, IRR.
Consider cash inflows and outflows for financial analysis.
Limitations of Financial Models:
Often overlook social and organizational dimensions.
May not consider costs from organizational disruptions or intangible benefits.
Software for Technology Investment Decisions:
Technology business management (TBM) framework translates technology investments into business value.
IT financial management (ITFM) tools help analyze, plan, and control IT project costs.
IBM Apptio is a leading ITFM tool for managing technology spending decisions.
14.3 Describe Project Management Methodologies and Variables
Project management involves applying knowledge, skills, tools, and techniques to achieve specific targets within budget and time constraints. Key activities include planning, risk assessment, resource estimation, task assignment, directing activities, controlling execution, progress reporting, and result analysis.
Project management methodologies:
Waterfall methodology: A traditional, linear approach with distinct phases (requirements, implementation, deployment). Emphasizes detailed documentation.
Agile methodology: Focuses on adaptability and flexibility, using "sprints" to complete work in short, specified periods. Documentation is less emphasized compared to the waterfall method.
Project management variables:
Scope: Defines what is included or excluded in a project. Ensures the project does not expand beyond its original intent.
Time: The duration required to complete the project. Involves breaking down the project into tasks and establishing a schedule.
Cost: Calculated by multiplying the time required by the cost of human resources, including hardware, software, and workspace expenses. A budget is developed and monitored.
Quality: Measures how well the project meets management's objectives, focusing on improved performance, decision-making, accuracy, timeliness, and ease of use.
Risk: Potential problems that could threaten the project's success, affecting time, cost, quality, or completion.
Technical debt: Results from trade-offs between time, cost, and quality. Short-term decisions to meet deadlines can lead to long-term issues affecting performance, scalability, and functionality. Managing technical debt is crucial for innovation and growth, with firms actively reducing technical debt experiencing higher revenue growth.
14.4 Understand the Importance of Effective Project Management
High failure rate of information systems projects: Many projects take more time and money than anticipated or fail to work properly.
Incorrect assessment of business value: Firms may misjudge the value of new systems or struggle with organizational changes required by new technology.
Importance of project management: Proper management and execution are crucial for the success of information systems projects.
Runaway projects: Private sector projects often exceed budgets and timelines, with many delivered with missing functionality.
Statistics on project failures: Large software projects typically run 66% over budget and 33% over schedule. Digital transformation projects have a 45% chance of delivering less profit than expected.
Consequences of poor project management:
Costs exceeding budgets
Unexpected time delays
Technical performance below expectations
Failure to achieve anticipated benefits
Impact on system usage: Failed projects may result in systems not being used as intended or not used at all, leading to the development of parallel manual systems.
Design failures: Systems may not capture essential business requirements, provide timely or usable information, or improve organizational performance.
User interface issues: Poorly designed interfaces can discourage use, such as cluttered web pages or difficult data entry screens.
Data quality problems: Inaccurate, inconsistent, or improperly organized data can hinder business functions and make information inaccessible.
14.5 Discuss Project Risk Factors
Dimensions of Project Risk:
Project size: Larger projects have higher risk due to complexity and difficulty in control. Factors include dollars spent, staff size, implementation time, and organizational units affected. Large-scale projects often fail to meet objectives.
Project structure: Projects with clear, well-defined requirements have lower risk. Projects with undefined, fluid requirements and changing user needs have higher risk.
Experience with technology: Lack of technical expertise in the project team increases risk. Familiarity with hardware, software, and database systems is crucial to avoid technical problems and delays.
Change Management and Implementation:
Behavioral and organizational impact: New information systems can change authority and power distributions, leading to resistance and opposition.
Implementation: Involves all activities toward adopting and managing a new system. Systems analysts act as change agents, ensuring acceptance and adjustment to changes.
Role of End Users:
User involvement: High levels of user participation in design and operation lead to better outcomes and positive reactions to the system.
User-designer communications gap: Differences in backgrounds and priorities between users and information systems specialists can lead to communication problems and project failure.
Management Support and Commitment:
Importance of backing: Management support ensures positive perception, sufficient funding, and resources. It also enforces changes in work habits and organizational realignments.
Challenges in Business Process Management and Enterprise Applications:
High failure rate: Many large-scale projects fail to deliver promised benefits due to poor implementation and change management.
Employee concerns: Addressing fear, anxiety, and resistance is crucial. Coordination among functional groups and extensive business process change are required for success.
Spotlight on Management Case Study
Happy Feet International, a luxury vinyl plank and tile flooring distributor, expanded significantly from a small family-owned business in 2012 to a large company with over 300 employees and 13 warehouses by 2024.
The company faced significant challenges with outdated technology, including an old in-house ERP system that caused inventory tracking issues and manual processes that led to inefficiencies and higher shipping costs.
To address these issues, Happy Feet adopted the Kuebix TMS platform, a cloud-based transportation management system, which helped save over $1 million by optimizing shipping decisions.
They also implemented a new ERP system from Oracle NetSuite, which faced challenges due to change management issues, such as resistance from long-term employees and undocumented processes.
Happy Feet overcame these challenges by engaging employees in conversations about change, providing extensive training, and simplifying the new system's usage.
The integration of Kuebix TMS with the NetSuite ERP system streamlined operations, reduced manual order data entry, and improved shipment visibility, leading to better customer service and accountability for carriers.
The new ERP system resolved inventory issues, allowing for biannual inventory checks instead of monthly, resulting in significant savings.
Overall, the new systems made Happy Feet faster, leaner, and more scalable.
14.6 Understand How Project Risks Can Be Managed
Project Management and Risk Handling
Identifying and managing project risks is crucial for success.
Frequent communication and collaboration help adapt to unforeseen problems.
Managing Technical Complexity
Success depends on managing technical complexity effectively.
Project leaders need both technical and administrative experience.
Teams should have frequent meetings and secure external expertise if needed.
Formal Planning and Control Tools
Gantt Charts: Visualize project activities, start and end dates, and resource requirements.
PERT Charts: Show task dependencies and sequence of activities.
Kanban Boards: Visualize tasks and project stages, often used in agile management.
Increasing User Involvement and Overcoming Resistance
User involvement is essential in projects with undefined requirements.
Strategies to overcome resistance include user participation, education, training, and better incentives.
Addressing organizational problems before introducing new systems can improve user cooperation.
Designing for the Organization
New systems should improve organizational performance and consider changes in job functions, structure, and work environment.
Ergonomics and user interface design are important for user interaction with the system.
Organizational impact analysis should be thorough and documented.
Sociotechnical Design
Combines technical efficiency with sensitivity to organizational and human needs.
Separate technical and social design solutions are compared to select the best overall solution.
Project Management Software Tools
Automate task definition, resource assignment, progress tracking, and modifications.
Tools like Microsoft Project and cloud-based applications facilitate project management.
Project portfolio management software helps manage multiple projects and their dependencies.
AI in Project Management
AI enhances efficiency by automating routine tasks and analyzing project data.
AI tools improve team collaboration and communication, such as ClickUp Brain for task management and content creation.
14.7 Understand How the Information in This Chapter Can Help Your Career
Familiarize yourself with various methods to build a business case for investments in information systems.
Understand the importance of effective project management in developing information systems.
Learn about various project management methodologies.
Identify the principal risk factors in developing information system projects.
Explore methods and tools to manage risks in information system projects.
Real-World Scenario: Project Managers Help Intuit Launch New Cloud Platform
Intuit is a leading provider of financial management software and tools, such as TurboTax and QuickBooks.
The company launched the Intuit Analytics Cloud (IAC) project to better utilize data across the organization and improve customer experiences.
The IAC project integrated all enterprise data, product data, and third-party data into a single platform.
Cooperation across the entire company was required, involving various functional teams from Intuit’s data engineering group.
The project was broken down into manageable pieces rather than using a "big bang" approach, making it easier to handle and implement.
Smaller project deliverables helped in managing deadlines and budgets, and in gaining support from business unit leaders.
The success of these smaller deliverables allowed for demonstrable results, facilitating the authorization of project expenditures.
The IAC project was successful, and Intuit’s business units are now eager to use the new enterprise analytics cloud.
Chapter Case Study
Southwest Airlines experienced a major operational disruption in December 2022, canceling nearly 17,000 flights due to outdated software systems and poor managerial decisions regarding IT investments.
The primary issue was the reliance on a twenty-year-old crew scheduling software system called SkySolver, which was overwhelmed during winter storm Elliott, leading to significant delays and cancellations.
Technical debt, the reliance on older or deficient software needing updates, was a significant problem for Southwest, with analysts noting the airline's delinquency in addressing these issues compared to other major U.S. airlines.
In response to the meltdown, Southwest allocated $1.3 billion in January 2023 to IT upgrades and improving operational resiliency, including enhancing crew engagement technology and updating crew recovery systems.
Southwest chose Amazon Web Services as its preferred cloud provider in March 2023, making cloud migration central to its modernization efforts.
A project team led by CIO Lauren Woods developed the Crew and Aircraft Integrated Recovery and Optimizer (CAIRO) tool to automate and optimize crew and aircraft reassignment, minimizing the impact on crew members.
By January 2024, Southwest announced an additional $1.7 billion investment in technology and cloud migration, aiming to shift more of its tech estate to the cloud for improved resiliency and modernization.
Review Questions
Building a Business Case
Types of information systems projects
Components of a business case for a proposed investment
Major components of an information systems plan
Evaluating IT Investments
Difference between tangible and intangible benefits
Six tangible benefits and six intangible benefits of an IT investment
Use of portfolio analysis, scoring models, and capital budgeting models to establish the worth of systems
Limitations of using financial models to evaluate IT investments
Software available to help make technology investment decisions
Project Management Methodologies and Variables
Definition of project management
Project management activities and variables
Definition of technical debt and its causes
Importance of Effective Project Management
Problems arising from poor project management in developing an information system
Project Risk Factors
Principal risk factors in information systems projects
Importance of addressing implementation and change management in new information systems
Managing Project Risks
Importance of management and end-user support for successful implementation of information systems projects
Strategies for controlling project risk
Organizational considerations in project planning and implementation
Contribution of project management software tools to successful project management
Discussion Questions
Project management significantly impacts the success of a new information system: Effective project management ensures that the project is completed on time, within budget, and meets the required quality standards. It involves planning, organizing, and managing resources to achieve specific goals.
Ignoring organizational behavior problems can lead to system failure: Systems builders often focus on technical aspects and overlook how the system will be used within the organization. Organizational behavior problems, such as resistance to change, lack of user involvement, and poor communication, can hinder the successful implementation and adoption of the system.
End users play a crucial role in information systems project management: Their involvement is essential for gathering requirements, providing feedback, and ensuring the system meets their needs. Engaging end users throughout the project helps in identifying potential issues early and increases the likelihood of user acceptance and satisfaction.
Hands-On MIS Projects
Caterpillar is considering ending support for its Dealer Business System (DBS) and transferring it to Accenture Consultants. Key factors to consider include the impact on dealers, the transition process, and the future support structure.
When evaluating the ROI for a new CAD system, you need to account for hardware, software, networking, installation, training, and support costs. Calculate the ROI by dividing the net benefit (Total Benefits minus Total Costs) by the total cost of the investment. Consider both one-time and recurring costs and benefits over a five-year period.
Use one of the four capital budgeting models (payback method, accounting rate of return, net present value, internal rate of return) to analyze the investment's worthiness.