Question

Firm's First Agile Project

As part of the team's initial project kickoff meeting, you have been asked to briefly summarize the differences between the waterfall and agile software development process. What would you say? Following your discussion, one of the team members asks, "so why are we changing to a new software development process? We are all comfortable with the way we do things now." What do you say? There is likely to be some confusion over the role of the project manager, scrum master, and product owner. What can you do to avoid this potential problem? What other potential problems can you anticipate as the team moves forward with its first agile project? What can be done to avoid these potential issues?

Answer 1

​​​​​​The basic difference between Agile and Waterfall model is flexibility. In Waterfall model you can not return back. As in a water fall once the water falls to ground it cannot be returned back. Similarly in waterfall model once you develop a software you can not change it. It is more useful when you are dead sure about the exact type of software requirements. In Agile method fliexibility is the main advantage. Software is developed in different phases called as sprint. Each phase is reviewed by client at specific intervals of time and changes are made as per requirements.

Following are some key differences:

• Waterfall is a Liner Sequential Life Cycle Model whereas Agile is a continuous iteration of development and testing in the software development process.
• Agile methodology is known for its flexibility whereas Waterfall is a structured software development methodology.
• Agile follows an incremental approach whereas the Waterfall methodology is a sequential design process.
• Agile performs testing concurrently with software development whereas in Waterfall methodology testing comes after the “Build” phase.
• Agile allows changes in project development requirement whereas Waterfall has no scope of changing the requirements once the project development starts.

Advantages of using Agile Method:

• It ensures the involvement of client at each stage so, it is a client focussed model.
• Agile teams are extremely motivated and self-organized so it likely to provide a better result from the development projects.
• It is based on incremental progress. So, Agile team and client are aware about what is complete and what is not. This reduces the risk in development of the software.
• Since the development of software is reviewed by the client at each stage, so this results in quality software being delivered.

A scrum master usually focused on a specific project team. A project manager manages the budget and the risks of the project. A scrum master motivates the team members, facilitates sprint planning and scrum meetings. A project manager focuses on processes and allocates tasks to the team members.Product Owners manage the product backlog and ensure the company gains maximum value from the product.A Scrum Master works in smaller scrum teams. They are responsible for the performance of their small scrum team. A Project Manager, on the other hand, handles relatively a bigger team. Out of all three Product Owner represents the client and has been employed by client to ensure that the software is being developed as per the requirements.

Proper explanation of the roles and resposnsibilities to the team members will help in avoidance of preoblems related to who will do what. It would provide clarity of roles and avoid duplication of efforts thus ensuring proper productivity and also helps in correct performance evaluation.

The company's first Agile project means that the team will be unaware of proper implementation of scrum agile methods. They will face some problems related to shifting from non agile method to agile method. Following are some problems faced by the team:

• Change Resistance People are resistant to changes. The team is new to agile model. The members will resist to changes. Proper training and motivational sessions highlighting the advantages of agile method and focussing on technical aspects have to be formulated to achieve success. This requires proper planning and formulation of strategy.
• Distributed Teams. Scrun team is working in distributed manner from different places in order to be cost effective and high skills procurement. This will give rise to many problems like coordination, understanding etc. The manger had to coordinate the team in unified manner to ensure the successful completion of the project.
• Communication Problem The team members work in different time zones and have different working hours. This will result in many problems. Proper management is required to handle this issue and ensure smooth delivery of software.