 Welcome to IT Project Management – Methodologies. In this learning activity, we'll explore two unique project management methodologies used for developing software. As an IT project manager, you have to decide which methodology suits your software development project. A methodology is a standardized set of rules and working concepts that guides a project, and picking the right one is imperative to your success. In software development, the two most common methodologies are waterfall and agile. Let's take a look at each one. Traditionally, IT project managers use the waterfall methodology, which is a linear approach to software development. Just like a real waterfall, this process always flows downhill. These projects flow sequentially from start to finish, with little to no deviation from the original plan. At the end of the process, the customer receives the finished project. IT project managers are starting to use a new approach called agile. This methodology is iterative, meaning teams can repeat steps. Unlike waterfall, agile teams can go back upstream instead of having to keep moving downstream. Agile teams work in sprints, which are short periods of time. By the end of this two- or three-week period, the team presents a working version of their product to the client. The client reviews it and provides feedback, which starts the team on the next sprint. Instead of moving in one direction, agile teams repeat these steps as many times as needed to complete the project. Selecting the best methodology for your project depends on many factors. While waterfalls, fixed steps, and downward motion may seem rigid, it can be the safer method. Problems are identified early on in the process. More documentation is created, which makes it easier for team members to pick up where someone else left off, and it provides a structured approach. In agile, the team works closely with the customer throughout the sprints by using a working version approach. While this flexible approach allows the team to respond rapidly to customer feedback, it can be chaotic if a team member leaves before the project is finished. You may be wondering if you have to choose one methodology over the other. Nope, it's actually not necessary. You can successfully mix both methodologies. This blend may be the most successful approach for your team. Whether you choose waterfall, agile, or a blended approach, your project will benefit from your understanding and application of these methodologies. You have completed IT project management methodologies.