يتجاوز التحول نحو أساليب العمل الرشيقة (Agile) مجرد التغيير الإجرائي، ليمثل تطوراً جوهرياً في نموذج القيادة؛ حيث يتحول دور مدير المشروع من "محور للضبط والرقابة" إلى "ميسر استراتيجي" يركز على تمكين الكفاءات وتذليل المعوقات الهيكلية لضمان تدفق القيمة. وفي هذا السياق، لا يتقيد المدير بتبني دور أحادي كمدير سكروم (Scrum Master) لتعزيز الحوكمة الإجرائية أو مالك منتج (Product Owner) لتوجيه الاستثمار، بل يبرز كـ "قائد هجين" يجيد الموازنة بين مرونة التنفيذ ومتطلبات الامتثال المؤسسي، خاصة في المشاريع ذات الحساسية العالية. ورغم تحديات التغيير الثقافي وصعوبة التخلي عن مركزية القرار، إلا أن التغلب عليها يكمن في تعزيز الشفافية المطلقة، واعتماد مبدأ القياس المستمر للأداء، وتحويل المخرجات التدريجية إلى برهان عملي يؤكد كفاءة النموذج الرشيق في تعظيم العائد على الاستثمار وتحقيق المستهدفات الاستراتيجية بكفاءة وموثوقية. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The key thing to take into account in your question is: agile can be implemented with any life cycle and any type of method that support the life cycle. with that in hands the organization can resolved about the roles. Just to remember a project management role is just somebody that implmenents project management and project management is "agnostic" about the methods and life cycles. Then, call the role as you want. Saving Changes...
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
I see it less as moving into a specific role and more as changing how you operate. The shift is from controlling delivery to enabling flow, helping the team remove blockers, align priorities, and keep focus on value. Titles may change depending on the organization, but the real change is in how decisions are made and how teams are supported. Saving Changes...
Robert LondonProject & Risk Consultant, and Career Coach (PMP, RMP, CSM, CSP,CCC, MSIE| CoffeeCat Solutions, LLCDC/VA/MD Area, United States
There is magical thinking that when you go to Agile you don't need a project manager. If there is only a scrum master, and you look deeply into the roles of the project team, you'll find that an architect or a lead technical staff member is unofficially leading the team as the project manager. Project managers with technical experience are indispensable for helping the Agile team for sprint planning, sprint execution, negotiating with executives and stakeholders, mitigating risks and issues, process improvement and overall keeping the project on track. Saving Changes...
One of the biggest misconceptions in Agile transformations is that the Project Manager role disappears. In practice, what usually happens is that the role shifts from managing tasks to managing the system around delivery.
Early in many Agile transformations, organizations often assume:
Scrum Master = Project Manager
Agile teams are fully self-managing
Coordination becomes “lighter”
Then reality shows up:
Dependencies still exist
Executive stakeholders still want visibility
Priorities still conflict
Cross-team alignment still has to happen
Risks, capacity constraints, and external commitments don’t magically disappear
That’s where experienced PMs often become even more valuable.
What changes is the nature of the work:
Less detailed task assignment and status chasing
More facilitation, alignment, dependency management, and decision support
More focus on flow, operating cadence, and organizational coordination
More translation between executive expectations and team realities
In mature Agile environments, I’ve seen PMs evolve into roles like:
Technical Program Manager
Delivery Lead
Program Manager
Agile Program Lead
Portfolio / PMO functions focused on coordination and governance
I’ve also seen organizations struggle when they remove PMs too aggressively under the assumption that Agile teams will “self-organize” everything. Usually someone ends up unofficially filling the coordination gap anyway — often engineering leads or architects who now have two jobs.
One of the biggest mindset shifts for me personally was realizing that Agile doesn’t eliminate the need for coordination — it increases the need for intentional coordination as systems become more decentralized.
The PM role just moves closer to enabling alignment, decision-making, and organizational clarity rather than controlling individual tasks. Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
From my experience, Agile transformations rarely eliminate the need for project management. What changes is the nature of leadership, coordination, and integration.
In many organizations, the project manager evolves from a task controller into an integration and decision facilitator across teams, stakeholders, dependencies, and strategic priorities.
Part of the role may overlap with Scrum Master or Product Owner responsibilities, especially in smaller or less mature environments. But in complex systems, those accountabilities are different:
• Scrum Master focuses on team flow and process effectiveness • Product Owner focuses on value and prioritization • Project Manager helps sustain coherence across the broader system
One of the biggest challenges I observed during Agile transformations was not the adoption of Agile practices themselves, but the loss of explicit integration ownership.
Execution became more distributed. But decision-making, dependencies, trade-offs, and alignment often became less visible.
What helped most was shifting from controlling work to enabling clarity, transparency, collaboration, and better decision quality under change.
Agility distributes execution. But without explicit integration, delivery speed can increase while organizational coherence declines. Saving Changes...
Community Champion
