Agile and vs. Waterfall Project Management

Running head: PROJECT MANAGEMENT 1
Project Management
Name
Institution Affiliation

PROJECT MANAGEMENT 2
Agile and vs. Waterfall Project Management
Waterfall model is a linear approach process of software development which
comprises a different unique sequence of events. Therefore, the development process can
only proceed to the next phase when the predecessor has been accomplished. At the same
time there typically a stage gate in-between every stage where all the requirements have to
reviewed and approved by the customers before the initiation of the design process. Yes,
when related to the project “establishing an organic grocery store in Virginia” Waterfall
methodology cannot be an appropriate software development process to take. Accordingly,
the reason for not selecting the Waterfall model is because the organic grocery sector is an
industry which is evolving at a high rate due to the rapid changes happening due to various
factors such as climate change and global warming. Waterfall model is only appropriate for
business activities in which the developer and the consumer agree on what is to be delivered
(Balaji, & Murugaiyan, 2012). However, in the case of the organic grocery store business the
owner of the grocery store has no power over the customer's decision; instead the customer is
responsible for what the developer has to deliver. In this case, the most appropriate option is
the Agile approach since it has the flexibility capacity to change with the changes in the
market environment.
Agile or Scrum is a software development approach that is characterised with the
delivery of a new product is a quick way but not at once; it is flexible such that it can evolve
with the change in requirements; it has the capacity to deliver a quality product in an
incremental manner; and allow for independent decision-making through the use of capable
members who can independently make decision regarding the product being developed.
Consequently, in the case of this context Agile model is more suitable as it has the capacity to
use a hybrid where it is possible to introduce implement the project as a product of Agile and
non-agile (Sutherland, Viktorov, Blount, & Puntikov, 2017). Accordingly, the introduction of