Agile Software Development and What it Means

By: DOTNUTSHELL Technolgies

is best suited to . Where an application or unit of work needs to be completed in record time, and the architecture does not debiate away from standards and frameworks already available on the market.

Agile methods emphasize face-to-face communication over written documents. Most agile teams are located in a single open office sometimes referred to as a bullpen. At a minimum, this includes programmers and their "customers" (customers define the product; they may be product managers, business analysts, or the clients). The office may include testers, interaction designers, technical writers, and managers.

Agile methods also emphasize working software as the primary measure of progress. Combined with the preference for face-to-face communication, agile methods produce very little written documentation relative to other methods. This is well suited to organisations that require standardise simple software systems which enjoy high usability and deployability.

Agile software development runs almost contrary to the waterfall development model.

The waterfall model is a sequential software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance.

In Royce's original waterfall model, the following phases are followed in order:

Requirements specification

Design

Construction (AKA implementation or coding)

Integration

Testing and debugging (AKA validation)

Installation

Maintenance

To follow the waterfall model, one proceeds from one phase to the next in a purely sequential manner. For example, one first completes "requirements specification" - they set in stone the requirements of the software. When the requirements are fully completed, one proceeds to design. The software in question is designed and a "blueprint" is drawn for implementers (coders) to follow - this design should be a plan for implementing the requirements given. When the design is fully completed, an implementation of that design is made by coders. Towards the later stages of this implementation phase, disparate software components produced by different teams are integrated. After the implementation and integration phases are complete, the software product is tested and debugged; any faults introduced in earlier phases are removed here. Then the software product is installed, and later maintained to introduce new functionality and remove bugs.

can create rapid software under the guise of an agile development plan. It is our policy to liase with our customers at all point within the software development lifecycle to gaunrantee that the end-product is what the client expects.

Software
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 

» More on Software