Jharna Software

1. The case’s key problems or the issues in the case?

The key problems discussed in the case are pertaining to Jharna’s software development method. Jharna traditionally used waterfall model for software development which comprises of meticulous documentation and planning. However, because of this model the integration stage was often difficult to plan and very time consuming. The time spent to find the bugs and resolve them was often longer than expected.

Additionally, the rapid change in business needs and market competition forced Jharna to consider adopting a people oriented agile methodology for its development. Adapting to this methodology resulted in consideration of multiple issues such as:

* Incompatibility of agile methodologies with Jharna’s culture.

* Contradiction of the methodology with the name if the company

* Issues concerning the documentation

* Heavy dependence on the development, resulting in potentially shifting the balance of power away from the management

* Project managers being naive about the use and implementation of agile methods.

2. The relevant considerations for each problem area or issue?

* The agile methods are incompatible with Jharna’s culture and will result in issues concerning the change of approach for software developers.

* System’s project management should spin out of control if developers were allowed to re-factor the system as they wished.

* Contradiction of the methodology with the name if the company. Change to agile methodology will lead to contradiction with its name which might be misleading.

* Issues concerning the documentation: Emphasis to documentation is not paramount in agile style and that might lead to lesser documentation done. This might cause concern to Jharna software since it’s a CMM level 5 and needs to maintain them.

* Heavy dependence on the development, resulting in potentially shifting the balance of power away from the management

* Project...