學門類別
哈佛
- 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
最新個案
- A practical guide to SEC ï¬nancial reporting and disclosures for successful regulatory crowdfunding
- Quality shareholders versus transient investors: The alarming case of product recalls
- The Health Equity Accelerator at Boston Medical Center
- Monosha Biotech: Growth Challenges of a Social Enterprise Brand
- Assessing the Value of Unifying and De-duplicating Customer Data, Spreadsheet Supplement
- Building an AI First Snack Company: A Hands-on Generative AI Exercise, Data Supplement
- Building an AI First Snack Company: A Hands-on Generative AI Exercise
- Board Director Dilemmas: The Tradeoffs of Board Selection
- Barbie: Reviving a Cultural Icon at Mattel (Abridged)
- Happiness Capital: A Hundred-Year-Old Family Business's Quest to Create Happiness
Jharna Software: The Move to Agile
內容大綱
Jharna Software was a medium-sized Indian software developer with an offshore center in the United States. The team in the United States usually performed systems analysis and design work at the customers' sites, while the rest of the development process was done in Indian development centers. Jharna Software was doing very well and had earned many prizes for export performance from the Indian government. It was, however, increasingly pressured by its main U.S. clients to adopt the emerging methods of producing quality software in a shorter time and with smaller budgets. Builds on the fundamental concepts of software engineering such as the plan-based approach (e.g., waterfall model) and the agile approach (e.g., extreme programming). Although agile methods are seen as an improvement over plan-based methods, they have various requirements (e.g., dynamic requirements analysis, frequent face-to-face meetings, lack of structure, strong emphasis on people rather than processes) that are difficult to meet in the offshore environment. Explains why plan-based methods are therefore commonly used in offshore locations.