ANALYZING A CASE STUDY
- SOMETIMES, SPECIFIC QUESTIONS ARE SET - ANSWER THESE
- OPEN CASE STUDY (NO SPECIFIC QUESTIONS)
- Brief Overview - where, when, key background information
- Key stakeholders
- Key Issues / problems
- Prioritise issues / problems
- Potential solutions / comment on solutions implemented
- What can we learn from the case / insights / conclusions
TYPE OF CASE
- In this course, primarily mini cases with a few more developed cases
- Mini cases often present a highly summarised, horizontal view of the organisation whereas full-blown cases often present a much more detailed vertical view
-‘Detective work' and reasonable presumptions are often necessary
- In class, we will often work in groups and some cases will be presented orally.
NIBCO, Inc., a mid-sized manufacturer of valves and pipe fittings headquartered in the U.S. with $460 million annual revenues, implemented SAP R/3 across its 10 plants and 4 new distribution centers with a Big Bang approach in December 1997. NIBCO management agreed with the Boston Consulting Group recommendation to "cut loose" from its existing legacy systems and replace them with common, integrated systems for finance, materials management, production, and sales/distribution, such as offered in the ERP packages of major vendors by the second half of the 1990s. However, the company leaders chose not to heed the advice of their consultants, or the current trade press, about taking a slower, phased-in approach. Instead, they developed plans for a Big Bang implementation of all modules (except HR) with a $17 million budget and a project completion date 15 months later that allowed for only a 30-day grace period.
The project is led by a triad of NIBCO managers with primary accountabilities for business process, IT, and change management. The case describes the legacy IT environment, the ERP purchase and implementation partner choices, the selection and composition of what came to be called the TIGER team, the workspace design for the project team (TIGER den), the key issues addressed by each project sub-team, the incentive scheme, and the complexity added by a distribution center consolidation initiative that runs behind schedule. The case story ends shortly after the Go Live date, with the project leaders replaying their warnings to the executive team about initial dips in productivity and profits.
This case study can be used to demonstrate the tradeoffs between Big Bang versus slower ERP implementation approaches that allow time for organizational learning. Students can identify the technology and organizational risks associated with ERP projects in general, and Big Bang implementations in particular, and then assess how well NIBCO's leaders manage these risks over the life of the project. Specific examples of communications and training initiatives, including ways to achieve employee buy-in, are detailed in the case so that students can better understand change management practices in the context of a major system implementation.
Attachment:- Assignment.rar