Search results

The case centers on Shilling & Smith's acquisition of Xteria Inc. and the resulting need to quickly scale the company's IT infrastructure to accommodate the acquisition. The case is based on a real leasing problem faced by a major retail firm in the Chicago area when it purchased a small credit card processing firm and scaled the operations to handle the retail firm's credit card transactions. The CIO of Shilling & Smith needs to determine which lease option is the best means of providing the technical infrastructure needed to support the firm after the acquisition of Xteria. Several issues will drive this decision, including the value and useful life of the equipment, as well as the strategic context of the firm. This case examines how to evaluate different lease options when acquiring data center information technology infrastructure. Specifically, the case addresses software vs. hardware leasing, different lease terms, and choosing between different lease structures depending on the strategy and needs of a company. This case enables students to understand the different types of technology leases and in which situations these leases would be employed.

The Shilling & Smith case examines how to evaluate different lease options when acquiring data center information technology infrastructure. Specifically, students learn software vs. hardware leasing, different lease terms, and how to choose between different lease structures depending on the strategy and needs of the company. A secondary objective of the case is to teach students the important components and relative costs of information technology infrastructure.

The computerisation of a government department is a very challenging process as it involves multiple stakeholders and power centers. Stakeholder identification as well as designing a system specific to the needs of a particular department can be a complex process. The computerisation of a police department in ASWI was initiated in the mid 90s but had not been a success. The case illustrates the challenges of the computerisation process in a bureaucratic environment. With multiple touch points and interdependent processes, designing and successfully implementing a technology solution for such an environment could be a major challenge. The case provides an opportunity to understand the reasons for IT project failures. The managerial strategies that can make an IT project successful and the situations in which these strategies can also be discussed.

The case illustrates an entrepreneurial voyage and venture creation and through it helps in identifying the reasons and causes for that venture's failure. It also enables discussion on the importance of planning a venture, more importantly; financing, managing, growing, and ending a venture and on how to avoid the pitfalls that befall such enterprises. This case can be used in Entrepreneurship courses as well as MBA, PGP and Executive Education programmes on Entrepreneurship.

In 2009 Wikia was the Internet's largest for-profit provider of hosted open-source wikis, with over a million daily users. After five years of existence, the organization had supported a wide range of exploratory activities, experiencing both success and failure. With approximately $3 million of cash on hand, Wikia turned cash flow positive in 2009, with revenues of approximately $4.5 million, affording it time and flexibility to try new things. Some of the company's employees and investors suggested that Wikia should attempt to expand and market itself more aggressively, but which strategic direction should receive priority? The case presents many of the issues and tradeoffs facing CEO Gil Penchina as he formulates these priorities.

The case seeks to teach students about the general business challenges facing a new firm in the area of Web 2.0, also popularly known as social networking. The case also exposes students to wiki technology and how it facilitates collaborative behavior.

John Williams, senior director of marketing for Microsoft's .NET, was trying to build the .NET brand, a comprehensive family of next-generation connectivity software products. Highlights the challenges of branding and positioning a complex technology offering. The first challenge facing Microsoft was to develop a common definition of .NET, which had been in flux over the prior two years. The second challenge was to choose between an umbrella branding strategy, a sub-branding strategy, and an ingredient branding strategy. The third challenge was to create a value proposition that would appeal to three very different target audiences: business decision makers, IT professionals, and developers.

To analyze the branding and positioning of a complex new technology offering: by defining a new product offering for public understanding and comprehension; evaluating brand strategies for optimal effect, considering possible hurdles to implementation of each strategy; and developing a value proposition attractive to differing audiences.

By 2006, Wikipedia had achieved the type of success that only a handful of young organizations could ever dream of reaching. It had grown from almost nothing in 2001 to become one of the consistently highest ranked and most visited sites on the Internet. This success brought new problems at a scale that no organization of this type had ever before faced. Exposes students to Wikipedia's brief history, the causes of its success, and the issues it faced going forward. Two topics form the focus: The first concerns the rules and norms for submission and editing, which raise questions about the ambiguity of Wikipedia's authority and the virtual cycle that keeps the site going; The second concerns the need to alter its practices as it gains in popularity, raising questions about what any wiki site, profit-oriented or open source, must do to scale to large numbers of participants and entries. These issues arise as part of a discussion about the site's priorities going forward.

To teach the factors that shape Wikipedia and wikis in general. Students will become familiar with the internal operations of wikis, open-source programs for developing text from many users. Also to facilitate teaching about factors that shape reference sites on the Internet, dividing discussion into three sub-topics: defining what Wikipedia is and what it is not, analyzing how it works, and understanding why it generates controversy in some circles.

The (A) case describes the evolution between 1999 and 2005 of an unusual innovation team within the office of the chief information officer at oil and gas giant BP. This team helped business units conceive, develop, and implement novel, value-added applications for emerging information technologies. The team leader, vice president and chief technology officer Phiroz Darukhanavala (“Daru”), eschewed a large group and venture budget in favor of a small, lean team intimately engaged with BP's business units. The case describes several mechanisms created by the CTO office during its early evolution: “Blue Chalk” events that expanded executives' appreciation of emerging technology capabilities, a network of relationships through which emerging technologies were scouted and vetted, a structured technology transfer process, and annual “game-changer” projects.

The (B) case describes how the CTO office team members in 2011 again solicited advice from their ecosystem of thought leaders and held workshops to significantly enhance their impact. As a result, they began developing solutions for broader, more fundamental business problems that came to be known as Grand Challenges: extremely difficult business problems whose solutions could potentially create hundreds of millions—or billions—of dollars in business value.

After reading and analyzing the case, students will be able to:

• Understand the management challenges associated with realizing the business value of new technologies

• Explore how innovation management evolves as an innovation team learns from its successes and failures and, more importantly, builds a reputation within and outside the company

• Examine a prototypical “advocate” model of corporate entrepreneurial practice

• Explore a leading example of a successful internal innovation program

Understand the management challenges associated with realizing the business value of new technologies

Explore how innovation management evolves as an innovation team learns from its successes and failures and, more importantly, builds a reputation within and outside the company

Examine a prototypical “advocate” model of corporate entrepreneurial practice

Explore a leading example of a successful internal innovation program

Mergers and acquisitions (M&A) are often very complex management endeavors. Analyzes the IT component of M&A for two financial institutions. Students are tasked with assisting Mike Farrell, the CIO of New Millennium Financial (NMF), a new company created through the merger of FinStar Financial and D&L Bank, in determining the optimal combined IT portfolio. To accomplish this task the strategic business objectives of the firm must be clearly understood and the IT projects in the pipelines of both institutions analyzed. Students must make an IT portfolio management decision and answer the question: What is the optimal IT strategy and project portfolio for NMF?

To apply a framework to manage a company's IT portfolio, i.e., understand the company's strategic context, develop business objectives that align with its strategy, assess IT investments, and develop a portfolio of IT projects that support the objectives. The framework is iterative, i.e., IT investments are assessed on a regular basis based on their performance and risk/return tradeoffs. Also to introduce a leading Web-based tool, ProSight, that helps managers organize IT portfolios.

This case is based on a real-life consulting engagement with a major Fortune 100 telecommunications company. The name of the firm has been disguised for confidentiality reasons. Completing the case teaches students how to develop a cost-containment ROI analysis and develop a business case for a large enterprise technology project. The class discussion focuses on strategies to understand and manage the risks of the project and organizational issues. In addition, the case teaches students good questions to ask when reviewing a complex project business case, and how to present a project for funding approval. This case is the second in a series of three cases designed to teach students ROI analysis for technology projects; the first is “B&K Distributors: Calculating Return on Investment for a Web-Based Customer Portal” and the third is the case “ROI for a Customer Relationship Management Initiative at GST.”

The case objective is for students to learn how to compute a return on investment (ROI) analysis for a large cost-containment technology project. Students learn the best practice of computing the range of possible outcomes (the best, worst, and expected case), and how to present the results to senior management. In addition, students learn how to incorporate important management issues of personnel reduction and technology project risk into an ROI analysis.

“MDCM, Inc. (B): Strategic IT Portfolio Management” examines the steps involved in developing a portfolio of IT projects aligned with a company's strategic objectives. Specifically, the case describes a situation where a firm has launched a transformation strategy but has yet to develop a complementary IT strategy. Students must select the optimal portfolio of projects aligned with the strategic objectives and define the global project execution strategy. The projects have both risks and dependencies. U.S.-based MDCM, Inc. specializes in medical device contract manufacturing and assembly. For the past five years, MDCM had grown by making more than twenty acquisitions of companies based outside the United States. This growth strategy enabled MDCM to better match its services to its customers, who had become larger and more global. In MDCM (A), the CIO of MDCM needed to determine the company's IT strategy and objectives. In doing so, he needed to ensure that they were properly aligned with the company's overall strategy and the new organization developed under an initiative called Horizon 2000. In a lecture prior to the cases, students should be introduced to the framework of IT portfolio management and how it can help focus IT efforts. In MDCM (B), the CIO has performed an audit of MDCM's IT and found twelve projects that are potential investment candidates for the next three years. The challenge for the IT Portfolio Management team is to identify the priority and appropriate sequence of investments to be made. The case assumes that students have knowledge of corporate IT. More specifically, the case is targeted for those who are or plan to become executives who would manage IT strategy and IT investment decisions either directly or in an oversight role. This case is the second in a series; the first is the case “MDCM, Inc. (A): IT Strategy Synchronization.”

For this case, students create a portfolio management process and apply it to the IT project portfolio of a global manufacturing company. Students will learn how to balance risk and return of projects and short-term vs. long-term wins. They also create an activity network diagram, stressing the importance of understanding global resource constraints and execution timing. Students also learn the nuances of portfolio selection, e.g., outsourcing decision making and build vs. buy for a global firm.