{"id":1158,"date":"2022-08-18T12:56:38","date_gmt":"2022-08-18T12:56:38","guid":{"rendered":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/?post_type=chapter&#038;p=1158"},"modified":"2022-08-19T12:31:32","modified_gmt":"2022-08-19T12:31:32","slug":"12-4-recent-trends-in-agile-project-management","status":"publish","type":"chapter","link":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/chapter\/12-4-recent-trends-in-agile-project-management\/","title":{"rendered":"12.4 Recent Trends in Agile Project Management"},"content":{"raw":"Organizations, whether they are multinational corporations, non-profits, government agencies, or international organizations, often make use of agile project methods and frameworks. Although agile started with the software development projects (see Section 12.1), its utilization has become common in other IT projects, and eventually non-IT projects such as new product development projects have practiced agile methods increasingly. A survey conducted by PMI (Project Management Institute) found that 23% of the organizations worldwide utilized agile techniques whereas 47% used predictive approach. However, another 23% also used hybrid approaches (e.g., using waterfall\u2019s sequential and linear project life cycle stages while establishing a more frequent communication and feedback system with the client and stakeholders).\r\n\r\nA recent study is the 15th State of Agile Report conducted in 2021 by digital.ai[footnote]Digital.ai. (2021). 15th State of Agile Report. <a href=\"https:\/\/digital.ai\/resource-center\/analyst-reports\/state-of-agile-report\">https:\/\/digital.ai\/resource-center\/analyst-reports\/state-of-agile-report<\/a>[\/footnote]. Their data is up-to-date and reflect the impact of COVID-19 pandemic. Their sample is dominantly composed of people who work in agile teams or in organizations which implement agile approach. This report highlights salient insights from the practice as detailed below:\r\n<ul>\r\n \t<li>The most popular agile approach is Scrum. 66% of the respondents identified Scrum as the methodology they follow most closely. Besides, 9% indicated that they use ScrumBan and 6% blends the Scrum with XP. Therefore, Scrum\u2019s share is 81% in total.<\/li>\r\n \t<li>The most popular scaling approach is SAFe with 37%. SAFe was followed by Scrum@Scale \/ Scrum of Scrums (9%) and Enterprise Scrum (6%).<\/li>\r\n \t<li>The top five agile techniques and practices used by the organizations are daily standups (87%), retrospectives (83%), sprint\/iteration planning (83%), sprint\/iteration reviews (81%), and short iterations (63%).<\/li>\r\n \t<li>The top five agile planning and delivery tools are Kanban boards (77%), taskboards (67%) spreadsheets (66%), agile project management tools (64%), and bug trackers (62%).<\/li>\r\n \t<li>The top five reasons to adopt agile are \u201cenhance ability to manage changing priorities\u201d, \u201caccelerate software delivery\u201d, \u201cincrease team productivity\u201d, \u201cimprove business and IT alignment\u201d, and \u201cenhance software quality\u201d.<\/li>\r\n \t<li>The top five challenges in organizations regarding agile practices are \u201cinconsistent processes and practices across teams\u201d, \u201corganizational culture at odds with agile values\u201d, \u201cgeneral organization resistance to change\u201d, \u201clack of skills\/experience with agile methods\u201d, and \u201cnot enough leadership participation\u201d.<\/li>\r\n \t<li>Eighty-one percent of the respondents recommended Jira as a software tool in agile planning and management. Jira was followed by Digital.ai agility (formerly VersionOne) and Azure DevOps. Thirty-five percent recommended Microsoft Project.<\/li>\r\n<\/ul>\r\n<div><\/div>","rendered":"<p>Organizations, whether they are multinational corporations, non-profits, government agencies, or international organizations, often make use of agile project methods and frameworks. Although agile started with the software development projects (see Section 12.1), its utilization has become common in other IT projects, and eventually non-IT projects such as new product development projects have practiced agile methods increasingly. A survey conducted by PMI (Project Management Institute) found that 23% of the organizations worldwide utilized agile techniques whereas 47% used predictive approach. However, another 23% also used hybrid approaches (e.g., using waterfall\u2019s sequential and linear project life cycle stages while establishing a more frequent communication and feedback system with the client and stakeholders).<\/p>\n<p>A recent study is the 15th State of Agile Report conducted in 2021 by digital.ai<a class=\"footnote\" title=\"Digital.ai. (2021). 15th State of Agile Report. https:\/\/digital.ai\/resource-center\/analyst-reports\/state-of-agile-report\" id=\"return-footnote-1158-1\" href=\"#footnote-1158-1\" aria-label=\"Footnote 1\"><sup class=\"footnote\">[1]<\/sup><\/a>. Their data is up-to-date and reflect the impact of COVID-19 pandemic. Their sample is dominantly composed of people who work in agile teams or in organizations which implement agile approach. This report highlights salient insights from the practice as detailed below:<\/p>\n<ul>\n<li>The most popular agile approach is Scrum. 66% of the respondents identified Scrum as the methodology they follow most closely. Besides, 9% indicated that they use ScrumBan and 6% blends the Scrum with XP. Therefore, Scrum\u2019s share is 81% in total.<\/li>\n<li>The most popular scaling approach is SAFe with 37%. SAFe was followed by Scrum@Scale \/ Scrum of Scrums (9%) and Enterprise Scrum (6%).<\/li>\n<li>The top five agile techniques and practices used by the organizations are daily standups (87%), retrospectives (83%), sprint\/iteration planning (83%), sprint\/iteration reviews (81%), and short iterations (63%).<\/li>\n<li>The top five agile planning and delivery tools are Kanban boards (77%), taskboards (67%) spreadsheets (66%), agile project management tools (64%), and bug trackers (62%).<\/li>\n<li>The top five reasons to adopt agile are \u201cenhance ability to manage changing priorities\u201d, \u201caccelerate software delivery\u201d, \u201cincrease team productivity\u201d, \u201cimprove business and IT alignment\u201d, and \u201cenhance software quality\u201d.<\/li>\n<li>The top five challenges in organizations regarding agile practices are \u201cinconsistent processes and practices across teams\u201d, \u201corganizational culture at odds with agile values\u201d, \u201cgeneral organization resistance to change\u201d, \u201clack of skills\/experience with agile methods\u201d, and \u201cnot enough leadership participation\u201d.<\/li>\n<li>Eighty-one percent of the respondents recommended Jira as a software tool in agile planning and management. Jira was followed by Digital.ai agility (formerly VersionOne) and Azure DevOps. Thirty-five percent recommended Microsoft Project.<\/li>\n<\/ul>\n<div><\/div>\n<hr class=\"before-footnotes clear\" \/><div class=\"footnotes\"><ol><li id=\"footnote-1158-1\">Digital.ai. (2021). 15th State of Agile Report. <a href=\"https:\/\/digital.ai\/resource-center\/analyst-reports\/state-of-agile-report\">https:\/\/digital.ai\/resource-center\/analyst-reports\/state-of-agile-report<\/a> <a href=\"#return-footnote-1158-1\" class=\"return-footnote\" aria-label=\"Return to footnote 1\">&crarr;<\/a><\/li><\/ol><\/div>","protected":false},"author":3,"menu_order":5,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-1158","chapter","type-chapter","status-publish","hentry"],"part":1145,"_links":{"self":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/1158","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/users\/3"}],"version-history":[{"count":5,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/1158\/revisions"}],"predecessor-version":[{"id":1226,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/1158\/revisions\/1226"}],"part":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/parts\/1145"}],"metadata":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/1158\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/media?parent=1158"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapter-type?post=1158"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/contributor?post=1158"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/license?post=1158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}