Basic definition<\/span><\/strong><\/span><\/p>\n<\/td>\n\n The agile methodology requires an <\/span>ongoing iteration<\/b> of designing, coding, & testing in the software development life cycle.<\/span><\/span><\/p>\n<\/td>\n | \n The DevOps methodology requires focused attention on <\/span>communication and integration<\/b>, leading to effective collaboration among the developer\u2019s team.<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n\n\n The motive of the methodology<\/span><\/strong><\/span><\/p>\n<\/td>\n\n Effective in handling and <\/span>delivering complex software <\/b>projects.<\/span><\/span><\/p>\n<\/td>\n | \n Effective in catering to <\/span>end-to-end engineering <\/b>processes.<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n\n\n Objective<\/span><\/strong><\/span><\/p>\n<\/td>\n\n The agile methodology extensively focuses on constant modifications.<\/span><\/p>\n<\/td>\n | \n The DevOps approach focuses on ongoing testing and delivery.<\/span><\/p>\n<\/td>\n<\/tr>\n\n\n Suitable team size<\/span><\/strong><\/span><\/p>\n<\/td>\n\n It is suitable for a <\/span>smaller team<\/b> as a small team facilitates quicker project development.<\/span><\/span><\/p>\n<\/td>\n | \n It is preferred for a<\/span> larger team <\/b>but also suitable for a smaller team.<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n\n\n Skillset required in the team members<\/span><\/strong><\/span><\/p>\n<\/td>\n\n The approach requires the entire group of team members to have a <\/span>variety of skills<\/b> that are also similar in nature.<\/span><\/span><\/p>\n<\/td>\n | \n The approach does not require the entire team to have a similar skill set. In fact, the <\/span>skillset gets divided <\/b>between the operation and coding teams.<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n\n\n Commonly accepted frameworks<\/span><\/strong><\/span><\/p>\n<\/td>\n\n It is compatible with tactical frameworks like <\/span>Sprint, Safe, Scrum, etc.<\/b><\/span><\/p>\n<\/td>\n | \n It is <\/span>not bound <\/b>to any commonly accepted frameworks.<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n\n\n Feedback is generally given by<\/span><\/strong><\/span><\/p>\n<\/td>\n\n The <\/span>clients<\/b> of the software or the ultimate app users.<\/span><\/span><\/p>\n<\/td>\n | \n The<\/span> internal working team <\/b>over the project.<\/span><\/span><\/p>\n\u00a0<\/span><\/p>\n<\/td>\n<\/tr>\n\n\n The key target of the methodology<\/span><\/strong><\/span><\/p>\n<\/td>\n\n Software development<\/span><\/p>\n<\/td>\n | \n End-to-end business solutions<\/span><\/p>\n<\/td>\n<\/tr>\n\n\n Shift left (test early and often)<\/span><\/strong><\/span><\/p>\n<\/td>\n\n Shifting Left leads to the developer\u2019s incorporation in the testing cycle earlier than before.<\/span><\/p>\n<\/td>\n | \n Along with Shift Left, it also uses Shift Right which leads to testing in the software\u2019s post-production phase.<\/span><\/p>\n<\/td>\n<\/tr>\n\n\n Documentation<\/span><\/strong><\/span><\/p>\n<\/td>\n\n The approach itself is <\/span>less focused <\/b>on the project’s documentation as the priority is on the working system over a team of members with similar skill sets.<\/span><\/span><\/p>\n<\/td>\n | \n DevOps’s <\/span>prime concern<\/b> remains robust documentation as the project is developed by one team and deployed by the other.\u00a0\u00a0<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n\n\n Must-have tools<\/span><\/strong><\/span><\/p>\n<\/td>\n\n Commonly used Agile tools vary from project to project and include the following:<\/span><\/p>\n\u00b7 Hudson<\/strong><\/span><\/p>\n\u00b7\u00a0 Jenkins<\/strong><\/span><\/p>\n\u00b7\u00a0 Jira<\/strong><\/span><\/p>\n\u00b7\u00a0 Pivotal Tracker<\/strong><\/span><\/p>\n\u00b7\u00a0 Kanboard<\/strong><\/span><\/p>\n<\/td>\n\n DevOps tools depend upon the stage of development, and the notable ones include the following:<\/span><\/p>\n\u00b7 Git- coding & building<\/strong><\/span><\/p>\n\u00b7 Selenium- testing<\/strong><\/span><\/p>\n\u00b7 Puppet- deploy & operate<\/strong><\/span><\/p>\n\u00b7 Kubernetes- build, deploy, & operate<\/strong><\/span><\/p>\n<\/td>\n<\/tr>\n\n\n Emphasis on automation<\/span><\/strong><\/span><\/p>\n<\/td>\n\n Low focus<\/b> on automation.<\/span><\/span><\/p>\n<\/td>\n | \n Automation is among the <\/span>primary goals <\/b>of DevOps, so the emphasis is high on it.<\/span><\/span><\/p>\n<\/td>\n<\/tr>\n\n\n
| | | | | | | | | | | | | | | | | | | | | | | | |