Although there are many comparisons Comparison of different Agile Methodologies given by different researchers but our analysis shows that Scrum model is best for development of smart devices applications. We describe in this article Comparison of different Agile Methodologies.
Agile works over comprehensive documentation during development. It require customer collaboration during software development so that good software develop. Although there are many software development methodologies developed after 1990’s. Some of them were developed by the combination of old and new ideas. Some were introduced totally by new ideas. In agile methodologies, process of working is based on close collaboration between the developer and stakeholder. It releases increment within a short period to compete the market. It requires minimum documentation to save development time.
Although, In literature we have studied many agile methodologies which highlights different aspects of projects. Now it is very crucial stage to determine which software model is best option for yours project. Selection of the software development model for the project plays a vital role in the success of project. So we are here giving here comparative analysis of software development model.
Table: Comparison of different agile process model
|Parameter||Agile Process Model|
|Scalability||Suitable for every size project||Suitability for small size project||For every size project Suitable||appropriate for complex project||For every size project Suitable||Suitable for smaller project|
|Team size||5-10 people||6-10 people||Clear:3-6
|Maximum 800||Team of all sizes||Smaller team
|Iteration Length||4-6 weeks||1-4 weeks||Clear:1-2 weeks
|Maximum 2 weeks||Maximum 6 weeks||4-8 weeks|
|Special Feature||15 days daily meeting and team collaboration||Suitable with small team||Team can select most suitable method||Focus on upfront design and building phase||Dynamic development by Prototyping method||Collaboration among team and self organization|
|Team Management||Self organized||Self organized||It Self organized||Controlled organized||It Self organized||Self organized|
|Development approach||It Iterative-incremental||Iterative-incremental||It Iterative-incremental||Iterative||Iterative-incremental||Iterative-incremental|
|User interaction||Users involved in all almost phases||User involved through product owner||Users involvement during releases||In it User involve in initial stage and plan by feature phase||User involvement during releases||User involvement during releases|
|Requirement gathering||Product backlog||User stories||Use cases||Features||Business study||Speculation|
|Development feature and practice||Sprint and product backlog. Sprint and sprint planning meeting||User stories. Pair programming Test driven development.||Crystal family methodology. Crystal’s clear. Crystal’s orange. Crystal yellow||UML Diagrams. Build different features like plan by feature and design by feature||Prototyping. Feasibility and business study||Dynamic cycle of speculation, collaboration and learning|
|Distributed Team||allowed||Not allowed||Not allowed||allowed||Not allowed||allowed|