Analysis of Case study of sapient

Gupta tried to recall what had happened in the course of the project and an emailed that he had been sent crossed his mind. The email communication about the transitioned of the development of the sapient in Gurgaon of which it was from the Global HR outsourcing Inc. GHRO). The project was about the development of the HRM portal that could carry out on the payroll as well as benefits of clients of GHRO. Although the project excited Douglas, it had some challenges. Douglas in the course of the project had a team of 60 members that was divided either into five or seven people. The work of the team was to on the work done as well as on the ways of improving on the work which had been left. The team started up with the waterfall projects and that of the agile projects.

in the process of blueprint design phase began as the teams were organized into different tracks. Initially, the agile project didn’t have design phase but sapient hybrid agile retained most of the traditional methodology. When the customers who had been used to waterfall design tried to switch to the agile, the transition that was in between made a lot of issues to arise in it. Of which one of them was inadaptability to software development that is different from the previous one. Therefore the end product turned out being great a disaster. The new method had evolved known as ‘Hybrid’ to make sure that there is the robust end product of which they could end up picking the pros of waterfall models and that of agile. First we are going to look into the development of agile and waterfall models, and later on, we look into ‘agile waterfall hybrid model’ together with the cons and pros of each one.

There is no software that can be produced until it is in the late stage of the lifecycle. Agile model Agile can be described as the group of developing software methods in which there are incremental and iterative developments whereby the solutions, as well as the requirements, can evolve through the collaboration of cross-functional of the teams and organization. The model has principles which bring processes to the backseat. Advantages of the Agile model is that there is involvement of the client in the course of the process. ROI which is one of the working software can be delivered frequently. Use of agile methodology does testing and coding. Ways of eliminating the flaws of the waterfall and agile development by use of the hybrid model. It doesn’t have documentation. The principle of the agile says that agile it’s more of working software rather than comprehensive documentation.

The methodology of the agile usually has believed that the documentation needs to be good enough and a lot of emphasizes has to be done on shipping of the working software. as the online examination of the project starts, SIT (System integration testing) had to be done then promoted to the coding of UAT environment in which the second cycle of testing was done. After that, all the high priority defects could be captured and resolved as well. There was also no scrum master. The scrum master is known to make sure that the team has to live according to the practices and also the values of the scrum. The scrum is responsible for helping the team to do the best work it could. In case one wants to start a project they need to decide the best model for the team of which it requires planning.

Things like resource utilization, the complexity of requirements and time are for software model. Some of the values of agile are; individuals as well as interactions over that of the tools and process. Customer collaboration to that of the negotiation of the contract. It is important for the project manager to look into challenges and risks once he want to start up a project.