The agile development software manifesto contains the following principles to guide teams involved in an iterative and incremental development. This is opposed to a traditional waterfall approach. Waterfall approach follows the straight path of software development: requirements first, then design, then implementation, then verification, then maintenance. Agile development teams believe that a working software should be developed in a moving cycle; requirements gathering, system design, implementation, verification, and maintenance can all happen at once.
The principles are drafted by 17 software developers in Utah on February 2001.
1. This approach wants to provide customer satisfaction by doing constant delivery of software versions.
2. This approach welcomes radical changes in the software requirements at whatever stage of development
3. This approach follows a shorter time scale, with expected deliveries set in weeks or months as compared to longer periods.
4. This approach encourages close collaboration between the business owner and the developer.
5. This approach believes that motivated workers are better at doing the job. They must be given the trust, support, and environment they need to get the work done.
6. As much as possible, a face-to-face conversation is pushed when someone from the team needs to send information to all collaborators.
7. The measure of a successful development progress is a working software.
8. Agile development software process endorses sustainable development. There is a need to maintain an indefinitely constant phase.
9. This approach enhances agility by perpetually focusing on technical and design excellence.
10. This approach encourages simplicity. It maximizes the amount of unfinished work.
11. Self-organizing teams are encouraged. This approach sees it as the source of excellent architecture, requirements, and design.
12. The team involved in agile development software pauses at regular intervals to reflect and plan ways to be more effective with their job. They must regularly adapt to the changing environments.
In 2005, another group agreeing to this manifesto drafted some project management principles and suggested them as an addition to the manifesto. Through the leadership of Alistair Cockburn and Jim HighSmith, the group called the finished product, PM Declaration of Interdependence:
• Increase ROI (Return on Investment)
• Give consistent results
• Anticipate Uncertainty
• Make good use of creativity and innovation
• Raise the performance levels
• Perk up effectiveness and consistency
This software development strategy oftentimes follows a sprint period of up to 30 days. Within the sprint, the team must come up with revised working software. They will base their priorities on the sprint backlogs. The team composed of 5-7 members will divide the tasks among themselves, swap jobs, and take other responsibilities as the situation requires it. At the end of each sprint, they would show the revision to the product owner and project manager (otherwise known as scrum master).
By using the agile development software principles, developers learn to be flexible with their development skills. They are not just confined in a straight-cut approach. The demands in today’s web development and programming are high. Everybody with a business or personal website needs someone to do the dirty job for them. This is one way of the developers to supply the need.
Feast your brain and mind into a colorful presentation of Agile Software goodness at Agile Development Software. Know more about this system development process and see if you can apply this to your systems.
Article Source: http://EzineArticles.com/?expert=Arvin_Cubil_Mejillano