{"id":8103297,"date":"2026-01-06T14:18:07","date_gmt":"2026-01-06T22:18:07","guid":{"rendered":"https:\/\/agilealliance.org\/?p=8103297"},"modified":"2026-02-07T17:50:59","modified_gmt":"2026-02-08T01:50:59","slug":"reimagining-agility-in-practice-insights-from-the-pmi-uae-chapter-workshop","status":"publish","type":"post","link":"https:\/\/agilealliance.org\/reimagining-agility-in-practice-insights-from-the-pmi-uae-chapter-workshop\/","title":{"rendered":"Reimagining Agility in Practice: Insights from the PMI UAE Chapter Workshop"},"content":{"rendered":"\n<p>We had the pleasure of facilitating a <strong>Reimagining Agility Workshop<\/strong> with the PMI UAE Chapter. The session brought together <strong>16 participants<\/strong> from diverse backgrounds, experiences, and maturity levels. This diversity turned out to be one of the workshop\u2019s greatest strengths.<\/p>\n\n\n\n<p>Rather than trying to cover everything, the group collectively selected <strong>two focus topics<\/strong> that felt both urgent and relevant:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>AI &amp; Automation<\/strong><\/li>\n\n\n\n<li><strong>The Future of Frameworks<\/strong><\/li>\n<\/ul>\n\n\n\n<p>What emerged was not a discussion about tools or buzzwords, but a deep, human-centered conversation about mindset, roles, and decision-making in an AI-augmented world.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Agile as a mindset before a framework<\/h3>\n\n\n\n<p>One of the most valuable observations came from participants who were <strong>new to Agile<\/strong> and had limited hands-on experience.<\/p>\n\n\n\n<p>Instead of immediately asking <em>\u201cWhich framework should we use?\u201d<\/em>, their strongest takeaway was:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>Agile is first and foremost a mindset, rooted in adaptability and learning.<\/p>\n<\/blockquote>\n\n\n\n<p>This was a powerful reminder. Often, experienced practitioners jump quickly into frameworks, roles, and ceremonies. Seeing Agile through the eyes of newcomers reinforced something fundamental:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>Starting with mindset and adaptability is not a weakness; it is a very healthy entry point.<\/p>\n<\/blockquote>\n\n\n\n<p>This perspective aligns strongly with the idea of <em>Reimagining Agility<\/em>: moving away from rigid adoption models and toward contextual, purpose-driven agility.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">AI &amp; automation: Role anxiety is real<\/h3>\n\n\n\n<p>The most intense and emotionally charged conversations emerged around <strong>AI and its impact on roles<\/strong>.<\/p>\n\n\n\n<p>A recurring theme was the <strong>uncertainty felt by project managers, Agile coaches, and Scrum masters<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><em>What will my role look like after AI?<\/em><\/li>\n\n\n\n<li><em>Will AI replace me, or support me?<\/em><\/li>\n\n\n\n<li><em>How do I stay relevant?<\/em><\/li>\n<\/ul>\n\n\n\n<p>The group strongly agreed on one point:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>Organizations have a responsibility to reduce this anxiety<\/p>\n<\/blockquote>\n\n\n\n<p>AI should be positioned clearly as an <strong>enabler<\/strong>, not a silent replacement. Companies need to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Clarify evolving role expectations<\/li>\n\n\n\n<li>Encourage experimentation with AI<\/li>\n\n\n\n<li>Explicitly state that human judgment, facilitation, and leadership still matter<\/li>\n<\/ul>\n\n\n\n<p>Without this clarity, resistance to AI adoption is not a technology problem; it\u2019s a trust problem.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Data readiness and the limits of automation<\/h3>\n\n\n\n<p>Another critical discussion centered on <strong>data<\/strong>.<\/p>\n\n\n\n<p>Participants highlighted that:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>AI is only as good as the <strong>data it is trained on<\/strong><\/li>\n\n\n\n<li>Poor or incomplete data can lead to <strong>wrong decisions<\/strong><\/li>\n\n\n\n<li>Hallucinated outputs are a real risk, especially in complex project contexts<\/li>\n<\/ul>\n\n\n\n<p>A concrete example was discussed:<\/p>\n\n\n\n<p>When writing an <strong>RFP<\/strong>, AI can help structure, draft, and accelerate the work, but it cannot fully automate it yet.<\/p>\n\n\n\n<p>Until data quality and governance are mature enough, <strong>human review and judgment remain essential<\/strong>. The message was clear:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>AI can support decision-making<\/li>\n\n\n\n<li>It cannot replace accountability<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Business focus and realism in project management<\/h3>\n\n\n\n<p>The workshop also surfaced an important shift in expectations for project managers.<\/p>\n\n\n\n<p>In an AI-supported environment, project managers are expected to be:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>More <strong>business-oriented<\/strong><\/li>\n\n\n\n<li>More <strong>realistic and outcome-focused<\/strong><\/li>\n\n\n\n<li>Less focused on mechanical reporting, more on sense-making<\/li>\n<\/ul>\n\n\n\n<p>This reinforces the idea that AI will automate <em>tasks<\/em>, not <em>thinking<\/em>. The value of project management increasingly lies in <strong>contextual judgment, stakeholder alignment, and business understanding<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Roles, reviews, and responsible AI use<\/h3>\n\n\n\n<p>A strong consensus emerged around one principle:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>AI cannot be used effectively in isolation from clear roles and review mechanisms.<\/p>\n<\/blockquote>\n\n\n\n<p>Even with advanced automation:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Roles still matter<\/li>\n\n\n\n<li>Reviews are still necessary<\/li>\n\n\n\n<li>Human oversight remains non-negotiable<\/li>\n<\/ul>\n\n\n\n<p>Rather than removing people from the loop, AI shifts <em>where<\/em> and <em>how<\/em> humans add value.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The future of frameworks: Adapting, not copying<\/h3>\n\n\n\n<p>In the <strong>Future of Frameworks<\/strong> discussion, the group explored how Agile principles apply beyond software development.<\/p>\n\n\n\n<p>Particularly in <strong>construction and hardware projects<\/strong>, participants emphasized that:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Sprint lengths must be <strong>adapted<\/strong> to the nature of the work<\/li>\n\n\n\n<li>Traditional project plans and Agile concepts can and should coexist<\/li>\n\n\n\n<li>A hybrid, context-aware approach is often more realistic than pure framework adoption<\/li>\n<\/ul>\n\n\n\n<p>The key insight was not about choosing <em>Agile vs. project management<\/em>, but about <strong>integrating concepts in a way that serves the work<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Adaptive and hybrid approaches: One size does not fit all<\/h3>\n\n\n\n<p>Within the <strong>Future of Frameworks<\/strong> discussion, a strong emphasis was placed on <strong>adaptability<\/strong> and the intentional use of <strong>hybrid methods<\/strong> based on the nature and direction of the project.<\/p>\n\n\n\n<p>Participants highlighted that different phases of a project often require <strong>different delivery approaches<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Early phases<\/strong>, such as project initiation, contracting, budgeting, and governance, tend to benefit from a more <strong>predictive<\/strong> approach. Clear scope definition, contractual clarity, and upfront planning remain critical in these stages.<\/li>\n\n\n\n<li><strong>Implementation and product development phases<\/strong>, on the other hand, are far more effective when handled through <strong>adaptive, sprint-based ways of working<\/strong>, enabling learning, feedback, and incremental value delivery.<\/li>\n<\/ul>\n\n\n\n<p>Rather than forcing a single framework end-to-end, the group strongly agreed that:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>The real skill lies in consciously combining predictive and adaptive practices based on context.<\/p>\n<\/blockquote>\n\n\n\n<p>This perspective moves the conversation away from \u201cWhich framework is right?\u201d toward <strong>\u201cWhich approach fits this phase, this risk profile, and this business need?\u201d<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Using AI to enable adaptive frameworks<\/h3>\n\n\n\n<p>The group also discussed how <strong>AI can actively support adaptive and hybrid frameworks<\/strong> when used responsibly.<\/p>\n\n\n\n<p>Examples included:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Supporting planning and scenario analysis during predictive phases<\/li>\n\n\n\n<li>Helping teams analyze progress, risks, and dependencies during sprint-based delivery<\/li>\n\n\n\n<li>Assisting decision-makers by synthesizing data across both project plans and iterative delivery metrics<\/li>\n<\/ul>\n\n\n\n<p>However, the same principle applied here as well:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>AI supports adaptation \u2014 it does not replace human judgment.<\/p>\n<\/blockquote>\n\n\n\n<p>Clear roles, strong review practices, and reliable data remain essential, especially when navigating between predictive and adaptive modes of working.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Closing the loop with AI: From ideas to shared outcomes<\/h3>\n\n\n\n<p>To close the workshop, we intentionally <strong>used AI as a collaboration enabler<\/strong>, not just a discussion topic.<\/p>\n\n\n\n<p>During the session:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>All ideas, insights, and reflections were captured and transferred into a <strong>shared digital workspace<\/strong><\/li>\n\n\n\n<li>An <strong>AI-supported synthesis<\/strong> was used to cluster themes and highlight patterns across the discussions<\/li>\n\n\n\n<li>The most impactful idea was <strong>selected with the support of AI<\/strong>, based on relevance and collective emphasis<\/li>\n\n\n\n<li>Finally, an <strong>AI-generated summary<\/strong> was created and shared with all participants<\/li>\n<\/ul>\n\n\n\n<p>I developed this AI tool used during the workshop while working as a volunteer on our Value Delivery Team, and it serves a broader purpose beyond this single session.<\/p>\n\n\n\n<p><br>All outputs from <strong>Reimagining Agility workshops<\/strong> are continuously collected in this shared platform, enabling:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cross-workshop learning<\/li>\n\n\n\n<li>Pattern recognition across different communities<\/li>\n\n\n\n<li>A growing, living knowledge base shaped by practitioners<\/li>\n<\/ul>\n\n\n\n<p>This closing step reinforced a key message from the workshop itself:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>AI is most powerful when it enhances collective intelligence and transparency.<\/p>\n<\/blockquote>\n\n\n\n<p>Rather than replacing human interaction, AI helped us:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create alignment<\/li>\n\n\n\n<li>Preserve shared understanding<\/li>\n\n\n\n<li>Extend the value of the conversation beyond the workshop room<\/li>\n<\/ul>\n\n\n\n<p>In many ways, this final step embodied the spirit of <strong>Reimagining Agility<\/strong>, combining human insight, adaptive thinking, and responsible AI usage to learn faster and move forward together.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Final reflection<\/h3>\n\n\n\n<p>This workshop reinforced why <em>Reimagining Agility<\/em> matters.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Agile is not a checklist<\/li>\n\n\n\n<li>AI is not a replacement<\/li>\n\n\n\n<li>Frameworks are not universal solutions<\/li>\n<\/ul>\n\n\n\n<p>Agility lives at the intersection of <strong>mindset, data, roles, and context<\/strong>. <\/p>\n\n\n\n<p>And meaningful progress happens when we create safe spaces to question assumptions, exactly what this workshop enabled.<\/p>\n\n\n\n<p>A big thank you to the <a href=\"https:\/\/www.linkedin.com\/company\/pmi-uae-chapter\/\" target=\"_blank\" rel=\"noopener\" title=\"\">PMI UAE Chapter<\/a> community for the openness, curiosity, and depth of discussion. <em>The conversation has only just begun.<\/em><\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Insights from a PMI UAE Chapter workshop on Reimagining agility, focusing on mindset over frameworks and the responsible use of AI in evolving project roles.<\/p>\n","protected":false},"author":8121106,"featured_media":8103309,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_tec_requires_first_save":true,"_EventAllDay":false,"_EventTimezone":"","_EventStartDate":"","_EventEndDate":"","_EventStartDateUTC":"","_EventEndDateUTC":"","_EventShowMap":false,"_EventShowMapLink":false,"_EventURL":"","_EventCost":"","_EventCostDescription":"","_EventCurrencySymbol":"","_EventCurrencyCode":"","_EventCurrencyPosition":"","_EventDateTimeSeparator":"","_EventTimeRangeSeparator":"","_EventOrganizerID":[],"_EventVenueID":[],"_OrganizerEmail":"","_OrganizerPhone":"","_OrganizerWebsite":"","_VenueAddress":"","_VenueCity":"","_VenueCountry":"","_VenueProvince":"","_VenueState":"","_VenueZip":"","_VenuePhone":"","_VenueURL":"","_VenueStateProvince":"","_VenueLat":"","_VenueLng":"","_VenueShowMap":false,"_VenueShowMapLink":false,"_tribe_blocks_recurrence_rules":"","_tribe_blocks_recurrence_description":"","_tribe_blocks_recurrence_exclusions":"","ep_exclude_from_search":false,"_jf_limit_responses":"","footnotes":""},"categories":[183],"tags":[],"content_source":[],"class_list":["post-8103297","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-the-alliance"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8103297","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/8121106"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8103297"}],"version-history":[{"count":17,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8103297\/revisions"}],"predecessor-version":[{"id":8104707,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8103297\/revisions\/8104707"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8103309"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=8103297"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8103297"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8103297"},{"taxonomy":"content_source","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/content_source?post=8103297"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}