Question

Please write a 5-6 page paper on organizations migrating from waterfall project management to Agile. What are the reasons why? What organizations have done this? Describe the advantages and disadvantages. Discuss reasons why this is necessary. Lastly, what should an organization consider when looking to migrate?

Answer 1

The traditional waterfall methodology for software development is rapidly losing its popularity as Agile methodology is now being increasingly adopted by companies worldwide for software development.

Waterfall basically is a sequential model where software development is segregated into a sequence of pre -defined phases – including feasibility, planning, design, build, test, production, and support. On the other hand, Agile development methodology follows a linear sequential approach while providing flexibility for changing project requirements, as they occur.

The top 10 differences between Agile and Waterfall Methodology:

1. The software development process is divided into different phases in the Waterfall model while Agile methodology segregates the project development lifecycle into sprints
2. Waterfall is a structured software development methodology, and often times can be quite rigid, whereas the Agile methodology is known for its flexibility
3. According to the Waterfall model, software development is to be completed as one single project, which is then divided into different phases, with each phase appearing only once during the SDLC. However, the Agile methodology can be considered as a collection of many different projects, which are nothing but the iterations of the different phases focusing on improving the overall software quality with feedbacks from users or the QA team
4. If you want to use the Waterfall model for software development, then you have to be clear with all the development requirements beforehand as there is no scope of changing the requirements once the project development starts. The Agile methodology, on the other hand, is quite flexible, and allows for changes to be made in the project development requirements even after the initial planning has been completed
5. All the project development phases such as designing, development, testing, etc. are completed once in the Waterfall model while as part of the Agile methodology, they follow an iterative development approach. As a result, planning, development, prototyping and other software development phases can appear more than once during the entire SDLC
6. One of the major differences between Agile and Waterfall development methodology is their individual approach towards quality and testing. In the Waterfall model, the “Testing” phase comes after the “Build” phase, but, in the Agile methodology, testing is typically performed concurrently with programming or at least in the same iteration as programming
7. While Waterfall methodology is an internal process and does not require the participation of customers, the Agile software development approach focuses on customer satisfaction and thus, involves the participation of customers throughout the development phase
8. The Waterfall model can be regarded as a stringently sequential process, however, the Agile methodology is a highly collaborative software development process, thereby leading to better team input and faster problem solving
9. The Waterfall model is best suited for projects which have clearly defined requirements and in which change is not expected at all, while Agile development supports a process in which the requirements are expected to change and evolve. Thus, if you are planning to develop a software that would require frequent overhauls and has to keep up with the technology landscape and customer requirements, Agile is the best approach to follow
10. The Waterfall model exhibits a project mindset and lays its focus strictly on the completion of project development, while Agile introduces a product mindset that focuses on ensuring that the developed product satisfies its end customers, and changes itself as the requisites of customers change

Service organizations such as Wipro Technologies need to adopt lean and agile methodologies to support the transition. As agile coaches, the biggest challenge we face is in transitioning the mindset of the team from that of a waterfall model to an agile thought pattern

Software development projects use different types of software development life cycle (SDLC)methodologies, depending on their nature and requirements, which basically define the way that the software development work is organized. The two main approaches are the traditional, waterfall method and the agile software development method. How are they different from each other and which one should you choose for your project?

The Agile Software Development Method Uses an Iterative and Team-Based Approach

One main difference between the traditional and agile methodologies is the sequence of the phases in which the software development project is completed.

The traditional method uses a linear approach where the stages of the software development process must be completed in a sequential order. This means that a stage must be completed before the next one begins. These stages usually comprise the following:

1. Requirements gathering and documentation
2. System design
3. Code and unit testing
4. System testing
5. User acceptance testing
6. Bug fixes
7. Product delivery

On the other hand, the agile methodology uses an iterative and team-based approach. Its main objective is to quickly deliver the application with complete and functional components. Instead of completing the software development tasks in sequence, they are completed in sprints that run from around 1 to 4 weeks and where a list of deliverables is completed in each sprint. The tasks that do not get completed within the sprint are then reprioritized and included in future sprints. This also means that the different stages of the software development life cycle can be revisited as needed.

The typical agile approach involves the following stages:

1. Project initiation
2. Sprint planning
3. Demos

With the traditional method, the details of the entire project have been visualized and defined before the project starts. In contrast, the agile methodology allows for more flexibility in that changes can more easily be made even after the project starts. It is best employed if the scope of the project cannot be clearly defined in advance. This also means that making unplanned software development changes with the traditional method is costlier than with agile.

The Agile Software Development Method Requires More Customer Involvement

Customers are highly involved in the early stages of the software development process when employing the traditional methodology. More specifically, their input is needed during the requirements gathering phase, as they must provide a detailed description of what their requirements are with regards to the software application to be developed and how they envision it to function. However, they have limited involvement after the software development process starts, aside from attending status meetings, doing reviews, and providing approvals. They usually get to see the product in its entirety after a software development life cycle is completed.

In contrast, the customers are highly involved in every stage when employing the agile development process. They can review the application at every phase and make suggestions for improvement. As a result, the customers are more engaged in the entire software development process, in turn ensuring that they are satisfied with the finished product.

The Traditional Method Has a More Formal Documentation and Review Process Than the Agile Approach

Each phase of the development process is properly documented and reviewed when using the traditional approach. On the other hand, due to the quick delivery time required with the agile method, changes are usually made directly on the code, with the developers just adding comments and annotations.

Which Software Development Method Should You Choose?

When choosing the methodology most suitable for your software development project, some of the things you should consider are the speed of completion; the size of the system; and the level of collaboration and interaction that is possible among the software development team members.

In particular, if you need to quickly release a basic product that you can later build on and add more features to, then the agile methodology may be more appropriate for your project. It works best if you have a startup, which means that you have limited resources but need a basic software application to get your business up and running. Likewise, this approach is suitable for small-to-medium-sized software applications.

On the other hand, the traditional method is better suited for projects in large enterprises where the specifications and requirements must be clearly defined before the project commences. Although the project may be divided into smaller components, each of which is developed with the agile approach, this comes with the risk that the individual components may not be compatible with each other once they are integrated to complete the final product.

Finally, the agile software development method requires a high level of collaboration among the stakeholders involved where each stakeholder must be readily available for input or feedback. In this regard, if you’re working with various groups (software developers, vendors, testers, customers, and others) that do not work in a single physical location or that may have limited availability, then the traditional approach may be the better option for you.

Both the traditional and agile software development methods have their own advantages and disadvantages. However, whenever feasible, the agile approach should be considered, as it provides more benefits, especially for startups. It enables a complete functional software application to be released faster. It is also more cost-effective, as making changes is less costly than with the traditional approach. Budgets can also be determined on a per-sprint rather than a per-project basis. Moreover, because the customer is highly involved and changes are constantly made to the application, a higher quality of work is achieved. With the use of technologies such as webcams, VoIP, and others, a high level of interaction is still possible even among remote teams. In this regard, this collaborative nature of agile fosters trust between the customer and the software development team.

In summary, the software development method most appropriate for your project will depend on factors such as schedule, cost, quality, and the other resources available to the project. As such, it should be the first decision that you and your software development team make. By organizing the different stages of your project efficiently, you can better ensure its successful completion — that is, a project that is developed on time, within budget, and where the customers are happy.