Primaveras Problems Prior to the Adoption of Agile Methodology - Case Study Example

Primavera Gets Agile Primavera’s problems prior to adoption of agile methodology Prior to use of agile methodologies, Primavera used the waterfall method. The waterfall method involved linearly sequential software development life cycle where developers had to fully complete one phase before embarking on the next phase of development. This model was not suited to the development of more complex projects hence end product turned out to be quite different from the client needs. Another problems was concerned with fixing of identified problems later on in the project lifetime proved difficult and or expensive. Therefore, the ability to create a product that pleased the customer was greatly limited due to use of these methodology. This model was also rigid in terms of allowing for changes to be made hence no working software was developed until late in the life cycle. The model was not suited to highly complex and object oriented projects since the people who were in command rarely had interactions with the development team or the process itself. Lastly, coordination between the various departments was poor and finally the risks and uncertainties associated with the model are high. Reasons for agile techniques adoption Agile techniques are the best answer to Primavera’s problems. The main advantages that come with implementing these techniques are; They encourages holding of regular scrums/meetings which boosts morale of the development team. The techniques have the inherent ability of being dynamic and able to soak in any changes even late in the project. They relies on the ability to rapidly make decisions. The incorporation of the various affected departments ensures the continued and improved coordination between the departments. The techniques provides for all members to give their input. Lastly, agile techniques are time conscious. Before agile techniques were implemented the developers would work overnight and into the weekends and their morale was low hence their social and family life was greatly affected. But after the techniques were adopted, all that changed due to the positive effects the techniques had on the team and the development process. The top management was also incorporated into the development process and thus the departmental coordination was greatly improved. The product delivery was always on schedule and the development team would get good feedback up from both their customers and their managers. This therefore proved that agile methodology was the best solution Primavera’s earlier problems. Primavera’s strategies and steps on adopting agile methodologies Primavera’s strategies and steps into adoption of agile methodologies included the following: The first step was to incorporate all the top management from the various departments and training them to be scrum masters. The removal of cubicles in favour of open desks was another step. This would foster cooperation and teamwork among the development team. Another step was the decision to have developers working in teams with each team having their own vision and mission. Back sliding to allow others to figure out how to work together was also another step. Holding of regular scrum meetings and frequent inspections to adjust customer wants. Imposing a fixed time duration of 30 days to deliver increments of value. Carrying out of regular tests development and functionalities tests. Challenges and obstacle with first implementation of agile methodologies The main challenge that Primavera faced during the initial implementation stages of agile methodologies was the reluctance of the top management team to give it a try since they were sceptical. They had been used to their traditional waterfall development model which had served their purpose before. Another challenge may have been the time it took for all the parties involved to adjust to the new procedures being implemented and comprehend its significance. The notable one being backsliding. The teams were to be left alone to figure out how to work together and apply the self-management approach. Primavera was able to solve the main obstacle of managerial sceptism by bringing in one of the authors and professionals on scrum to talk to the team. He did eventually convince them to give agile methodologies a try. The team was given enough time to fully comprehend and understand the importance of agile methodologies and they too were fully on board with it. An object mentor was also brought in to maintain a high level of software during every sprint. Why agile methodologies produced better and superior product that traditional waterfall model. The advantages that come with using agile methodologies far outweigh those that come with the waterfall model. These are as highlighted below; With implementation of agile, the time it took to complete tasks was greatly reduced and the teamwork ensured that the developers did not have to work overnights and into the weekends in order to complete their projects. This greatly improved their family and social life and thus boosted their morale which ultimately meant that their input into the product development was hundred per cent. The development of working functionalities every month and their testing ensured that all any errors were caught early and solutions found. The tests ensured that the product met all the user requirements and exceeded their expectations. The daily scrums or meetings involving the developing team and the scrum masters who were the top management ensured greater cooperation between departments and that all product requirements and changes in customer needs were incorporated into the functionalities. It also made the team aware of each other’s progress and what was expected of them each day. The sound object oriented design of scrum also pushed the development team towards features and paying of close attention towards good design principles. The agile methodologies created a highly motivating and energetic development environment. It made the place vibrant as people begun to work together, exchange of ideas and participation in daily trade off decisions. The practise of continuous testing, continuous integration and continuous improvement of code also added to the overall and success of the final product. The participation of top management ensured that decisions were driven down to where knowledge was applied also greatly improved the developing team’s morale. Primavera’s business development since the publication of the case study Agile methodologies’ continued impact on Primavera is evident in the positive feedback that they get from their happily satisfied customer base and also the improved attitude their employees have towards the working environment at the firm. The product delivery time has greatly reduced and planned releases have all gone as smoothly as planned. There is now near perfect coordination between the several departments and thus a conducive environment. Primavera has experienced tremendous growth ever since and its success is unrivalled. It has never experienced any layoffs unlike most other companies hence its success has enabled it to open new branches in other parts of the country. The employees are currently happy and satisfied to be part of Primavera and they feel that they own the company rather than thinking what they are doing for the company. References Beyer, H. (2010). User-centered agile methods. San Rafael, Calif.: Morgan & Claypool Publishers. Martin, R. C. (2003). Agile software development: Principles, patterns, and practices. Upper Saddle River, N.J: Prentice Hall. Samra, T. S., & School of Pharmacy, L. (2012). Software risk management: an exploration of software life cycle methodologies, best practices and tools for their application to medical device software risk management. Los Angeles, California: University of Southern California. Schwaber, K. (2004). Agile project management with Scrum. Redmond, Wash: Microsoft Press. Read More