What are Criterion for evaluating agile-driven software development projects
In my point of view agile driven software development projects can evaluated on different criterion. It depends on the requirements and nature of the organization. This can be evaluated on the criterion of the user satisfaction that it satisfies the user or not. It can also be evaluated on time basis whether it provide required output and information. Also we can evaluate it on delivery on time or it takes longer time as compare to other software development projects.
Quality and maintainability is another way to evaluate the agile driven software because quality plays very vital role for the succession of the any software and its maintainability also has important role for the succession of the software if software is not easily maintainable then it will be very difficult for you to get the required results.
Congruent with the principle of being responsive to changing client needs, user satisfaction is rated as the dominant criterion for evaluating agile-driven software development projects. Meeting delivery schedules and producing quality software also emerge as important criteria followed by maintainability and cost.
Not surprisingly, documentation, whose role is downplayed in agile development, is rated as least important for assessing agile-assisted projects. Our respondents added delivery of business value and frequency of delivery as other key evaluation criteria, with the latter measure emphasizing the iterative nature of agile techniques.
Problems/Challenges in Adopting and Using Agile methods
In my point of view there are problems and challenges in adopting and using agile methods. Most of organizations are not ready to change as their management feels hesitation to adopt and use agile methods and there is a risk of failure of the project. It requires proper training for using and if training is not taken for using this method it will not be easy to adopt and use.
Lack of interest of the managers for adopting and using agile methods is another problem. Reward for using agile techniques and method is small when it is compared to other which is a challenge for adoption and use of agile method. Non availability of formal guideline and peer support are also challenges for the adoption and use of agile methods.
There are many limitations of the agile methods such as:
- Limited support for complex.
- Large software.
- Sub contracting.
- Large team involvement.
- Lack of proper testing.
- Project requirements.
- Standards and improper documentation.
These are challenge for adoption and using of the agile methods.
For more educational Stuff