Agile Requirements As Introduced In The Agile Manifesto

By Author: Tamra Cross
Total Articles: 7
Comment this article

The agile requirements were established during the second half of the 1990s. The Agile Manifesto was published during 2001. Incremental type software processes had actually been in use since 1957 and lightweight software methods since the mid 1990s.

The manifesto basically said that more effective ways of software production were emerging. In this evolving process, particular methods and exchanges had been noticed and deemed well worthwhile. Versatility in development procedure and in the people involved is a necessity.

The working relationships between people are thought of as better and more effective than written developmental procedures. Extensive documentation is not working software. The input from the end user is a valuable commodity whilst the software is being developed.

Change is a valuable part in the development procedure and designs tend to be too inflexible to include this requirement. Both self-organization as well as eagerness are desired, in addition to pair programming as well as co-location. Accomplishing operating software at the earliest possible time is really a prerequisite and holds ...
... a lot more weight compared to actual documentation. Ongoing stakeholder feedback is crucial, while the software development routine advances. Development should be centered on rapid response to changing needs, whilst at the same time keeping up a flow of steady advancement.

Getting the software working as quickly as possible will provide both customer interest and contentment and enable the inevitable alterations and corrections to be suggested sooner rather than later. Stakeholder consultations should occur often, and involve as many stakeholders as possible, for this is an important part of the developmental process. Allow motivated developers leeway to experiment. Desirable changes often occur when teams seek their own direction. Technical excellence through both high quality design and focused attention should deliver efficient simplicity in the end product.

This method of software design divides tasks into iterations of one to four weeks each. Each of these time units contains its own planning, analysis, design, coding and testing. Stakeholders should be present whenever testing is done and any suggestions they make noted and if practical incorporated into the design.

Face to face talk is preferred to impersonal memos and written documentation. Working groups need to contain a representative for the client. Daily communications between stakeholders should be a common occurrence and they are meant to uncover problems at the earliest possible opportunity. Testing and development occur simultaneously and complement each other.

This sort of software creation is considered to be more designer focused than end user focused. The idea that this form of software development focuses more about the methods for actually reaching the end user's specifications as well as developing the appropriate code, compared to concentrating on the general specification of the solution design, isn't totally correct. There are many illustrations of this technique for software development being used with great success.

Admittedly, these types of methodologies can be less efficient in larger organizations, as well as in different styles of projects. Numerous developers feel that agile requirements are somewhat extreme. Approaches which mix requirements with more plan driven methods are common of late.

Alex Stein is a software developer and freelance writer. For more information on agile requirements please visit http://www.piersonrequirementsgroup.com