Waterfall and Agile

Assignment 2: Waterfall and Agile

Explain waterfall methodologies and identify their relationship to the PMBOK® process groups

Waterfall methodology is a sequential design process in which the eight (8) stages are completed and the developers move on to the next step (Base36 Staff, 2012). According to Base36 Staff (2012), the eight (8) stages include: (1) conception, (2) initiation, (3) analysis; (4) design, (5) construction, (6) testing; (7) implementation, and (8) maintenance. It is a linear approach to software development. Waterfall gives a basic roadmap for development, whereas PMBOK gives a repository of techniques to manage that development process better (Morton Consulting Staff, 2011). In the waterfall model, each phase of a product’s life cycle takes place in sequence, so that progress flows steadily downwards through these phases like a waterfall (Bowes, 2014).

Explain agile methodologies and identify their relationship to the PMBOK® process groups

Agile methodology helps teams respond to unpredictability through incremental, iterative work cadences, known as sprints and is an alternative to waterfall, or traditional sequential development (Agile Methodology Organization Admin, 2008). It’s a different way of managing IT development projects and teams. According to Waters (2007), in agile software projects, project management relies far more on the project manager’s skills in communication, facilitation, coordination, and emphasizing far less on planning and control. Scrum, Dynamic Systems Development Methodology (DSDM), and Extreme Programming (XP) are various methodologies that are collectively known as agile (Waters, 2007).

Analyze the need for waterfall and agile methodologies

Emphasis was placed on creating a sustainable, disciplined, and repeatable development process; which resulted in a sequential set of phases that attempted to design, construct and deploy software to meet the business need (Johnson, 2010). Because the waterfall process is a linear one it is perhaps easier to understand, especially for non-developers or those new to software development (Bowes, 2014). According to Bowes (2014), one of the pros for agile methodologies is that working software is delivered much more quickly and successive iterations can be delivered frequently, at a consistent pace. Modifications to requirements can be integrated at any point of the process when using agile methodologies; even late in the development. This methodology is used to minimize risk by developing software in short time boxes which are called iterations that generally last for one week to one month (Tatva Soft Staff, 2014).

Agile methodologies make software development less complex. With agile methodologies, direct communication and constant feedback from customer representative leaves no space for any guesswork in the system (Tatva Soft Staff, 2014). According to Tatva Soft Staff (2014), waterfall model is very simple and easy to understand and use method that is why it is really beneficial for the beginner or novice developer.

Explain the advantages of extreme programming (XP)

Extreme Programming (XP) is a disciplined approach to delivering high-quality software quickly and continuously (McLaughlin, 2015). The advantages of Extreme Programming include robustness, resilience, cost savings, lesser risks, and better overall satisfaction (Nayab, 2010). According to Nayab (2010), Extreme Programming allows for cost-estimates based software features instead of developer activity. Extreme Programming empowers your developers to confidently respond to changing customer requirements, even late in the life cycle (Wells, 2013). Extreme Programming also emphasizes teamwork.

According to Tatva Soft Staff (2014), the XP model helps to establish rational plans and schedules and to get the developers personally committed to their schedules; which is surely a big advantage in the XP model.

Analyze the advantages of extreme programming’s application in high-budget short-time projects

Some experts believe that extreme programming works best with small to medium size projects (Allen, 2014). According to Allen (2014), it is also believed that extreme programming works best for high risk projects. Instead of delivering everything you could possibly want on some date far in the future, the process of Extreme Programming delivers the software you need as you need it (Sanjeev, 2014). This model is consistent with most modern development methods so, developers are able to produce quality software (Tatva Soft Staff, 2014). It emphasizes on customer involvement.

Explain the factors to consider when selecting a project management methodology (Waterfall vs Agile)

Each project management methodology has its own strengths and weaknesses. Some of the factors to consider when selecting a project management methodology are (a) commitment and support from top management, (b) organizational structure, (c) communication; (d) culture, and (e) training. For any point in the size–criticality space, methodology designers select a scope of concerns, prioritizing some quality of the project (Cockburn, 2000). According to Cockburn (2000), the four principles to use when selecting a project management methodology for an organization includes: (1) a larger group needs a larger methodology, (2) a more critical system needs more publicly visible correctness in its construction, (3) a relatively small increase in methodology size adds a relatively large amount to project cost; and (4) the most effective form of communication is interactive and face-to-face. With that being said, customer availability must be a factor to consider.

Conclusion

Both the agile and waterfall methodologies have their strengths and weaknesses. There is value in combining both the waterfall and agile approaches. Both methodologies bring about efficiency and provide customers with maximum value. Even though the waterfall methodology is old and traditional, depending on organizational needs, it still proves to be just as useful and necessary as the agile methodology. When it comes to the waterfall and agile methodologies, no project is too big or too small.