Why cloud Environment

Cloud computing and agile, a great combination

Distributed application development
The cloud assists conveyed application advancement with groups scattered topographically. Any
colleague can have rights to get data about the application at any minute.

Data sharing
Assets are obliged to share a colossal measure of information between diverse machines for
some applications. The cloud assumes a significant part by giving a medium to share a great deal
of information according to the prerequisites.

Prioritizing tasks
It is important to consistently organize and prioritize errands. In a conveyed framework, there is
a necessity to redesign devices. This expends vitality and requires some investment .

Transparency
Straightforwardness is important. In a cloud-based agile model, the engineer can be
straightforward and live up to expectations.

Infrastructure
Dexterous programming advancement obliges the infrastructure to be set up from the beginning.
The cloud helps by providing a base

Athletic development processes improve (as much as possible) the opportunity given by
computers that do work for you, but that is stored somewhere else and maintained by other
companies as a result of releasing software over and over again. The clients point is to assist the
organizations and to check and observe each and every fragment for upgrading standards

Combining agile development and cloud computing brings the best of both worlds. Different
organizations are using different methods for computing. It makes software faster than before.
The cloud has provided quality. There are various advantages when we combine both agile and
the cloud (Singh and Chana, 2013, Khan et al., 2011, Tuli et al., 2014).

. The automated form resolves or decreases the development expenditure while lifting the
reusability and client fulfilment to a huge degree.

Ranging from increased processing due to the most advanced technology, increasing the area of
networks data storage, and the most remarkable thing is the consistency in Internet protection.

The main insight is the enhanced excellence equality of products, improved efficiency of
developers and less errors. The continuously increasing acceptance of agile methods proves their
efficiency and usefulness. The agile process ensures frequent interfacing between developers and
customers, as well as contributes significantly to its investment. In this study, we contribute to
the body of knowledge on the comparative analysis of agile methodologies.

Diff between Rup and Scrum

RUP vs Agile

SCRUM methodology uses a project backlog instead of scope and allows the backlog to be
redefined at the end of each iteration (usually about every 4 weeks).

 SCRUM dictates that the entire "traditional" lifecycle fits into one iteration.
 In other words, a workload for one iteration (Sprint) at a time is determined and then the
entire cycle occurs within one iteration (e.g. the requirements for a particular feature are
collected, documented as a user story, then coded, tested and presented for the user
review).

RUP methodology calls for a formal definition of scope and major project milestones are
associated with specific dates.

 RUP subdivides the project lifecycle into 4 major phases (Inception, Elaboration,
Construction, Transition).
 Even though it encourages concurrent workflows across the entire cycle, the general
understanding is that certain activities will peak during certain phases (for instance,
requirements analysis will spike during the elaboration phase).


Scrum is one of the most popular agile methodologies for software development projects
Rational Unified Process methodology is used mostly in the area of web application
development. It is often used for developing web applications and websites. Rational Unified
Process (RUP) provides several benefits and tools that can be used throughout the software
development process. These tools include templates (such as HTML or web templates) and
examples from other projects that the software developer can adopt. RUP is made up of the
following four phases.

 Inception Phase: In this phase, software developers describe the scope of the
development project as well as a definition of the business case. The business case will
usually provide specific details about the business.
 Elaboration Phase: In this phase, the software developers outline in detail all the features
of the system. For example, John (as the customer) will be given a complete outline of all
the different things that the system will be able to do.
 Construction Phase: In this phase, the design and source code of the application are
developed.
 Transition Phase: In this phase, the software developers bring the completed software
solution to the customer. In our example, this is the point at which John will receive his
working system.

This merger of agile and cloud computing may provide infrastructure optimization and
automation benefits to agile practitioners