When it comes to developing a
system in the organization there are a number of different methods that can be
used. Four of the most popular methods are waterfall development methodology,
Rapid application development methodology, agile development methodology and DevOps
methodology. Each one has its own benefits and limitations (Banica, et al. 2017). Different
organizations use different kind of developing systems, and one of the
organizations was using a different method for developing system, but then they
opted for an alternative for developing system. The alternative method was
chosen as per requirements of the organization.
The organization identified is a
large organization that has set its clear goals and objectives. In order to
improve its future performance the company decided to use the agile development
methodology for developing a new system. The organization was not satisfied
with the decision it made because the methodology used did not turned out to be
effective. Agile development methodology starts with planning that is also
known as backlog, then comes collaboration known as Iteration, the third step
is called deliverables and lastly there is feedback that can be done daily. The
different forms of agile development include crystal, extreme, feature-driven
development (FDD) and scrum. The organization did make the right decision of
choosing agile development method to some extent because there are a number of
advantages of this method. Some of these advantages are discussed below (Umbreen, Abbas and Shaheed 2015)
Firstly, this method reduces the
chances of risks in terms of lower cost overruns and bugs. Secondly, it has
lower changing requirements for the organization since the software is
developed in iterations. Thirdly, defects and mismatches can be detected early
so this improves efficiency. With all these benefits involved the question is
that why couldn’t the organization take advantage of this method. This is
because there are several disadvantages as well. This is a time consuming
method that is highly labor intensive since the people who are developing this
need to complete each and every step. Also in case the employees in the
organization are used to of the waterfall method then they might find it difficult
adopting this method (Cockburn 2000)
The main issue that the
organization faced was that it made use of the wrong method. The Agile method
is commonly used in the case of small organizations. Since this was a large on
this method did not proved to be beneficial. This method is similar to the RAD.
Communication effectively can be a little complex in large organizations so
Agile method is not that useful. In case of large organizations process models
would be better to use. The two main things that every organization has to keep
in mind when selecting a method is, the nature of the system that is going to
be developed and the size of their team.
Other factors that affect the choice of the methodology is that the
level of skills available in the workforce of the organization. Highly skilled
workforce can better adapt to changes as they may come up with better solutions
however, workforce with lower skills may not want a change as it will be
challenging for them. Organizations that have highly skilled employees are
usually recommended to use the Rapid application development methodology (Little 2005)
Moreover, whenever a change is
being introduced in the organization it is important to clearly discuss the
idea first with its employees. Employees are the biggest assets of the company
and are closer to action hence, it is important to take their feedback on the
issue. Once they are motivated to adopt the new system they will more easily
accept change and so the results would be better. Furthermore, the budget that
the company has and time that it has also determines the methodology that it is
going to use. In addition to this according to Cockburn (2000) and Little (2005)
the risk associated with each type should be considered carefully
Keeping all the above discussion
in mind I think the right approach would have been the RAD method. This is
because the business had clearly defined its goals and time was important for
the business that was looking forward to a good result.
References on developing a
system in the organization
Banica, Logica, Magdalena Radulescu, Doina Rosca,
and Hagiu Alina. 2017. "Is DevOps another Project Management
Methodology?" 21 (3): Informatica Economică vol.
Cockburn,
A. 2000. "Selecting a project's methodology." IEEE Software
17 (4): 64 - 71.
Little,
Todd. 2005. "Context-Adaptive Agility: Managing Complexity and
Uncertainty." IEEE Software 22 (3): 28 - 35.
Umbreen,
Munazza, Jalil Abbas, and Syed Muqsit Shaheed. 2015. "A Comparative
Approach for SCRUM and FDD in Agile." International Journal of Computer
Science and Innovation (2): 79-87.