Waterfall and Agile

Waterfall and Agile

Assignment 2

CIS 517 – IT Project Management

In examining programming advancement, the techniques venture chiefs like to use to deal with their tasks are Agile and Waterfall (Schwalbe, 2016). This folklore’s have distinctive ways to deal with overseeing programming advancement ventures (Schwalbe, 2016). With dexterous, the objective is to enable the task to move rapidly and effectively, while cascade is utilizing in mind-boggling and mind-boggling expense ventures (Schwalbe, 2016).

Waterfall and agile methodologies and their relationship

Venture Management Body of Knowledge (PMBOK) is a guide that contains forms (Vargas, 2001). These procedures are set up to make an industry standard (Vargas, 2001). There are thirty-nine procedures partitioned into five sub-gatherings (Vargas, 2001).

Starting Process: Initiation (Vargas, 2001).

Arranging Process: The Arranging process are score arranging, scope definition, movement definition, asset arranging, action sequencing, action span assessing, cost evaluating, chance administration arranging, plan advancement, cost planning, quality arranging, authoritative arranging, and staff securing (Vargas, 2001).

Executing Process: Executing process are Undertaking plan execution, quality confirmation, group advancement, data circulation, requesting, source choice, and contract organization (Vargas, 2001).

Controlling Process: Controlling Process are Execution announcing, scope check, scope change control, plan control, cost control, quality control, hazard observing and monitoring, and coordinated change control (Vargas, 2001).

Shutting Process: Shutting process is Contract closeout, and managerial conclusion (Vargas, 2001).

Both waterfall and agile are connected to the procedure bunches dependent on PMBOK models (Palmquist, Lapham & Ozkaya et al., 2013). Exclusively, the two philosophies are extraordinary yet are based on utilizing the five primary procedures in PMBOK to design ventures (Palmquist, Lapham & Ozkaya et al., 2013). One of the advantages of the cascade is it is a direct strategy with an essential model (Palmquist, Lapham & Ozkaya et al., 2013). The portrayal of the waterfall is framework prerequisites, programming necessities, examination, plan, coding, test and coordination, and tasks (Palmquist, Lapham & Ozkaya et al., 2013). Agile dissimilar to cascade isn’t one clear strategy (Palmquist, Lapham & Ozkaya et al., 2013). Agile contains an accumulation of techniques that share essential attributes (Palmquist, Lapham & Ozkaya et al., 2013).

Analyze the waterfall and agile Attributes

The two philosophies assume an exceptional job in the task the executives (Fair, 2012). The waterfall is the more seasoned of the two systems (Fair, 2012). It is an attempted and genuine philosophy utilized for programming production of usage ventures (Fair, 2012). Indeed, even today most ERP experts still like to use waterfall while actualizing another framework (Fair, 2012). Deft is a more current philosophy, and on account of how it joins different techniques inside itself, it is quickly turning into a favored alternative to waterfall (Fair, 2012).

Agile is base on an establishment of practices that incorporate Empiricism, prioritization, self-association, time-boxing, and cooperation (Fair, 2012). One critical establishment thing is experimentation (Fair, 2012). Induction is fused into tasks to give the capacity to ponder the advancement of the undertaking (Fair, 2012). It enables the undertaking chief to “perform, stop, reflect, enhance and proceed in a well-ordered exertion to build profitability” (Fair, 2012).

Advantages of extreme programming (XP) and analyze and the benefits of its application in high-budget short-time projects

As recently clarified, spry consolidates distinctive strategies. One of these strategies is excellent programming (Palmquist, Lapham & Ozkaya et al., 2013). The ideal approach to depict outrageous writing computer programs is, “it is a strategy that executes a basic and powerful condition that empowers groups to wind up beneficial” (Palmquist, Lapham & Ozkaya et al., 2013). One of the numerous focal points of XP is that it accentuates cooperation (Palmquist, Lapham & Ozkaya et al., 2013). XP is predicting on supervisors, clients, and designers all assuming an equivalent job in a communitarian situation (Palmquist, Lapham & Ozkaya et al., 2013).

The motivation behind why XP can give this convenient administration depends on its establishment (Palmquist, Lapham & Ozkaya et al., 2013). XP has five basic building squares, correspondence, straightforwardness, criticism, regard, and mettle (Palmquist, Lapham & Ozkaya et al., 2013).

Waterfall vs. Agile project management methodology.

Given all the examination that is accessible, agile is the better approach (Fair, 2012). Some portion of the expert system is lean, XP, Scrum, and so forth these philosophies enables spry to be adaptable with regards to ease of use (Fair, 2012). So both coordinated and cascade have key territories where they are getting it done (Fair, 2012).

If The project manager is going to run a waterfall project, there are points they need to evaluate.

The Project manager is going to run an agile project; there are points they need to evaluate.

  • The project manager is running a project that is heavy in details and is a long-term project with a single timeline (Fair, 2012).
  • The project has a linear based Equation approach, which is also creating numerous dependencies (Fair, 2012).


  • When a project has shorter planning based on multiple diversities (Fair, 2012).
  • The product will be going to deliver in functional stages (Fair, 2012).
    • The customer is going to heavily involved in all facets of the project (Fair, 2012).

Fair, J. (2012). Agile versus Waterfall. Retrieved from https://www.pmi.org/learning/library/agile-versus-waterfall-approach-erp-project-6300

Palmquist, S., Lapham, M., Miller, S., Chick, T., & Ozkaya, I. (2013). Parallel worlds: Agile and Waterfall Differences and Similarities. Retrieved from https://resources.sei.cmu.edu/asset_files/TechnicalNote/2013_004_001_62918.pdf

Vargas, R. V. (2001). A new approach to PMBOK guide 2000. Retrieved from https://www.pmi.org/learning/library/chronologically-structured-approach-controlling-closing-process-7931

Schwalbe, K. (2016). Information Technology Project Management, 8th Edition. [Strayer University Bookshelf]. Retrieved from https://strayer.vitalsource.com/#/books/9781337431095/