Jharna Software: The Move To Agile Methods
1. Create a process map of the software development process described in the Jharna Software case. As we discussed in class, there are many methods available for process mapping. You may use any conventions that you choose. What characteristics of the process is it important to represent? Why?
Process Map: Attached Appendix 1
With the help of the process map it is easy to understand how the process and the project work is divided in India as well as in US. It is crucial to emphasize the importance of continually comparing the requirements with the customers’ expectations about the final product. The process map should also indicate how the project is initiated with the help of project manager. This process map is focused on demonstrating the tasks and the flow undertakings of the project work. To concentrate on this we need to know when the project is divided into modules and when a team leader is allocated. Development of the project coding and the type of documents that are involved should also be focused in process map to better understand about the various types of documents involved in the process and to stress the significance of them. The process map represents the sequential way in which the all the tasks are carried out based on the project rather on the routine process in the organization. Another main feature that is important to represent is the involvement of contingency plan and the integration of the final product.
In this process map, the rectangle represents a process, the parallelogram (diamond) represents a decision, the oval symbol represents the start and end of a terminal and the paper symbol represents the document. In this process map the sequential tasks that are necessary to perform the project are represented and it is done from the team’s perspective. The note (information) to explain about the task also becomes useful for greater understanding of the whole process. As document plays an important role in the project, mentioning them in the process map helps the user to know more with lesser information.
2. Is the software development process a good candidate for redesign? Why or why not?
Software development process is certainly a good candidate for redesign in Jharna Software. Redesign should be considered for a rapid change in the management and the staff mainly to reduce the costs, to increase the quality of the software product and also to speed up the software development process. It is visible that they are facing greater problem in the integration stage and has been difficult to keep up with it. Considering Jharna Software, it is noticeable that from the early days, Jharna software has given prior importance to high quality and low-cost service products. It has even received several awards for its performance while competing with the highly reputed companies like TCS, Infosys, and Wipro which were also more focussed towards the financial services industry and the integration services.
The present software development process was a traditional waterfall approach where once a stage (e.g. requirements gathering) in Jharna is completed there is no going back which implies that when the customer request for the change of requirements in later stage it becomes very difficult to modify the work and the whole work is redone. To avoid this, a new system that is adaptable to the changes should be considered. Otherwise there will be continuing problem in the integration stage which keeps on building up unless a drastic measure is considered.
Jharna Software’s main strength is its highly skilled workforce and thus they can maintain the quality. Recently, it has been noticed that the developers in Jharna Software worked beyond the customary 40 hours a week that implicated working late hours and on weekends too. This clashes with their initial vision of providing non bureaucratic and employee friendly...
Bibliography: Scacchi, W. (2001). Understanding and (Re)Designing Software Development Processes. Institute for Software Research, University of California, (p. 40). Irvine, CA.
Bose,Indranil(2006). Jharna Software: The move to Agile Methods. Asia Case Research Center, The University of Hong Kong.
(2000) How to capture knowledge without killing it. Harvard Business Review.
Please join StudyMode to read the full document