Discuss the Principle behind the Agile Manifesto?

Agile Manifesto accepted a notion that requirements are difficult for the user in traditional
development methodology or they can not define in detail their requirement because users
were not fully evolved in the project development. They (Users) only discover at the end of
a long life cycle of development, probably during testing or even implementation since there
is no room for correction at that time because is already too late.

This above ugly situation led to actualization of Agile Manifesto. The principle behind Agile
manifesto are

1. Early and instant delivery of valuable software that will meet the requirement of
customer should be the highest priority.
2. Agile processes embrace changes in other to allow customer competitive.
3. Users and developer must work together daily throughout the project life cycle.
4. The right people that sees solution in the problem given should be informed in the
project for the development to get their job done.
5. Communication barrier should be avoided; in that wise, the most efficient and
effective method of conveying information to and within a development team is face-
to-face conversation.

List the range of technique and methodologies that are covered by the Agile
Umbrella?

The range of technique that are covered by the Agile umbrella are

Iteration: This is dividing a project into a set of parts of each which is capable of delivering
working software that implements a required feature or part of a feature. This division is
also called incremental. Each increment contains some or all of the traditional phases of
development therefore revisiting the stages give room for changes before final
implementation.

Short Life Cycle: it has to do with time for the revisiting (iteration) which must be
reasonable without losing patience or enthusiasm and without changes in the requirements
of the user.

Risk Acceptance: In traditional methodologies risks are to be identified, assessed and

avoided but Agile sees this as missing an opportunity, because those high risk activities have
the potential of delivering large benefit.

People Orientation: Agile sees that using the right people e.g users, stakeholder etc as a
team is probably the most important element in the agile approach.

Collaboration and Communication:

Methodologies that are covered by the Agile umbrella are:

Adaptive Software Development

Scrum

Agile Modelling and

Feature Driven development

What are the key techniques used in RAD methods

The key techniques used in Rapid Application Development methods are:

1. Incremental Development: Users of RAD belief that not all system’s requirement can
be identified and met in advance. Some comes through when the users see and
make use of the developed system, therefore specifying system completely in
advance is impossible. Introduction of future iteration and timeboxes will be able to
handle the evolving requirement overtime.
2. Timeboxing is the process of dividing a system to be developed into a components or
timeboxes. The most important requirement and with the largest potential benefit,
are developed first and delivered as quickly as possible.
3. JAD Workshop: This require high level of participation from all stakeholders in a
project. It is designed to meet problem of traditional requirement by getting all the
relevant people together in a short period to hammer out decision.

Advantages of Agile approach for Business solution

As we all known that everything is changing very fast and unpredictable which based on
market requirement of low volume, high quality, custom and specific products. Therefore
Agile allow changes for customer competitive advantage.

It sees solution from every challenge because it believes that those that return large
benefits are by their nature likely to be a risky. It sees it as an opportunity.