Project Management- Agile- Pros and Cons
Positive points of agile principles
Flexibility
Agile software development methodology
incorporates user or customer feedback after each sprint. Thus the methodology
is able to undertake any further development based on the customer suggestion
using a rapid model of pivot innovation functionality. Kaisti et al.
(2014) illustrated that result of any accepted feedback requires change. Hence
in this unpredictable economy it is essential to understand and accept the
feedback to incorporate the change to embrace the software quality.
Iterative
Agile Methodology divides the whole
software development project into several sprints. Each of these sprints
includes five basic phases of software development which are Planning Phase,
Designing Phase, Development Phase, Testing and review phase. Rasnacis & Berzisa (2017)
opined that this iterative functionality allows agile methodology to understand
customer requirement and develop customer value after each sprint as per our project management homework help expert. It was
reported that customers are concerned about the quality of software they are
receiving after each development cycle instead of UML Documentations (Kaisti et al. 2014). Hence this requirement is
well addressed by Agile Methodology through collecting feedbacks after each
sprint from customers and includes their suggestions in the development phase
of the next sprint.
Negative points of agile principles
Cost
Cost implication is a major drawback
for implementing any agile methodology. This is basically due to the fact that
continuous feedback collection requires implementing changes which leads to
increased cost for software development. Soni & Kohli (2017) opined that any organization needs
to ensure that they are willing to incorporate more investment for their
software development processes.
Documentation
It is the underlying assumption of
this methodology that customers and developers are required to be co-located to
ensure that customers are available whenever developers required. Kuhl (2014) illustrated that the
proper documentation and software model designs does not have an essential role
within the software development process. Hence developers and customers are not
able to get the understanding from documents.
Comments
Post a Comment