To have the software development process a fruitful one we have to consider the critical factors of success of agile development. Any organisation is expected to deliver the end product timely with required and on agreed upon terms which is many a times beaten by the extended time taken to complete the software projects or also leading to unexpected increase in the budget of the projects. So today’s development processes embed agile implementation for the accelerating growth of the company, organisation with fast competition of their work. The conventional approach of software systems succumbs towards the ever changing and much needed twist of the “Agile process” to be implemented. Agile focuses on collaborative work for the lifecycle of the project to continue iteratively with anticipating changes and introducing more flexibility than prior traditional approaches. Small sprints remain utilized which are mandatory for effective item conveyance. Conventional programming advancement forms are very little proficient to deal with the fast change in necessities. In spite of the upsides of Agile, feedback on deft approach expresses that it neglects to focus on building and configuration issues and subsequently will undoubtedly create little outline decisions. Agile programming improvement has quickly picked up a great deal of enthusiasm for the field of programming designing. Agile programming development, in spite of its curiosity, is a critical area of research inside programming building discipline. Logical research is yet rare, there has been minimal nitty gritty revealing of the use, entrance and achievement of light-footed systems in customary, proficient programming advancement organisations. In this paper we will evaluate the agile success factors for the product outcomes. The manuscript takes the approach for deciding best agile success factors influencing quality in software industry using analytic network process (ANP). This paper applies ANP to conclude the best way out using nine criteria namely Agile implementation, root cause analysis, mutation testing, cycle time, test and learn approach, continuous integration, process action, IT governance strategy, organisational change, effective risk mitigation, feedback, tangible outcomes, and two alternatives in the form Scrum and Kanban agile framework. The projected approach was tested in a organisation application in software reliability, software development environment and this paper evaluates its effectiveness by giving the weightage to the factor by realising the precise objective.

中文翻译：

---

影响软件行业质量的敏捷成功因素的分析评估

为了使软件开发过程富有成果，我们必须考虑敏捷开发成功的关键因素。任何组织都应按要求并按约定的条件按时交付最终产品，这比完成软件项目所花费的时间要长很多倍，或者导致项目预算的意外增加。因此，当今的开发流程嵌入了敏捷的实施方式，以加快公司，组织的竞争，从而加速其工作。软件系统的传统方法屈服于不断变化和急需实现的“敏捷过程”的扭曲。敏捷专注于项目生命周期中的协作工作，以与预期的传统方法相比，不断地进行迭代以预期变化并引入更大的灵活性。仍然使用小冲刺，这对于有效的物品运输是必不可少的。常规的编程改进形式几乎不能熟练应对必需品的快速变化。尽管敏捷有很多优点，但对于灵巧方法的反馈表示，它忽略了专注于构建和配置问题，因此毫无疑问将几乎没有制定大纲。敏捷编程的改进很快引起了人们对编程设计领域的极大热情。尽管有好奇心，敏捷编程开发仍然是编程构建学科内部研究的关键领域。逻辑研究还很少见，在习惯的，熟练的程序开发组织中，轻度系统的使用，进入和成就方面几乎没有任何实质性的揭示。在本文中，我们将评估产品成果的敏捷成功因素。该手稿采用分析网络过程（ANP）来确定影响软件行业质量的最佳敏捷成功因素的方法。本文运用ANP来通过九项标准得出最佳的解决方案，这些标准包括敏捷实施，根本原因分析，突变测试，周期时间，测试和学习方法，持续集成，流程行动，IT治理策略，组织变革，有效的风险缓解，反馈，有形的成果，以及Scrum和Kanban敏捷框架形式的两个替代方案。