學門類別
政大
哈佛
- General Management
- Marketing
- Entrepreneurship
- International Business
- Accounting
- Finance
- Operations Management
- Strategy
- Human Resource Management
- Social Enterprise
- Business Ethics
- Organizational Behavior
- Information Technology
- Negotiation
- Business & Government Relations
- Service Management
- Sales
- Economics
- Teaching & the Case Method
最新個案
- Leadership Imperatives in an AI World
- Vodafone Idea Merger - Unpacking IS Integration Strategies
- Predicting the Future Impacts of AI: McLuhan’s Tetrad Framework
- Snapchat’s Dilemma: Growth or Financial Sustainability
- V21 Landmarks Pvt. Ltd: Scaling Newer Heights in Real Estate Entrepreneurship
- Did I Just Cross the Line and Harass a Colleague?
- Winsol: An Opportunity For Solar Expansion
- Porsche Drive (B): Vehicle Subscription Strategy
- Porsche Drive (A) and (B): Student Spreadsheet
- TNT Assignment: Financial Ratio Code Cracker
-
Ça Va de Soi: A Phoenix Rises from the Ashes of a Failed IT Project - Part A - The Fall
This two-part case study of a Canadian knitwear SME called Ça Va de Soi (CVDS) presents a real-life situation: an IT project failure (part A) and how the project was "resuscitated" and transformed into a success (part B). The case highlights (1) the challenges and risks of IT projects for SMEs, (2) the importance of evaluating and selecting the right IT supplier and managing relationships, and (3) how, during a retrospective, lessons learned from a project failure can be transferred and applied to other IT projects. -
Ça Va de Soi: A Phoenix Rises from the Ashes of a Failed IT Project - Part B - The Rise
Supplement to case HEC138. This two-part case study of a Canadian knitwear SME called Ça Va de Soi (CVDS) presents a real-life situation: an IT project failure (part A) and how the project was "resuscitated" and transformed into a success (part B). The case highlights (1) the challenges and risks of IT projects for SMEs, (2) the importance of evaluating and selecting the right IT supplier and managing relationships, and (3) how, during a retrospective, lessons learned from a project failure can be transferred and applied to other IT projects.