{"id":8107624,"date":"2026-04-23T11:44:30","date_gmt":"2026-04-23T18:44:30","guid":{"rendered":"https:\/\/agilealliance.org\/?post_type=aa_event_session&p=8107624"},"modified":"2026-04-23T11:44:32","modified_gmt":"2026-04-23T18:44:32","slug":"the-role-of-the-project-manager-on-modern-agile-projects","status":"publish","type":"aa_event_session","link":"https:\/\/agilealliance.org\/resources\/sessions\/the-role-of-the-project-manager-on-modern-agile-projects\/","title":{"rendered":"The Role of the Project Manager on Modern Agile Projects"},"content":{"rendered":"\n

The following is an AI summary of the event.<\/em><\/p>\n\n\n\n

You can download the slide deck for this presentation at the bottom of the summary.<\/strong><\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

In this session, Dr. Alistair Cockburn<\/strong>, co-author of the Agile Manifesto, revisited a long-running question: Do modern Agile projects still need project managers?<\/strong> His answer was clear: yes, but not as bureaucratic administrators. On effective Agile teams, project managers play a central role in enabling communication, protecting focus, securing executive support, guiding decision-making, and helping teams navigate uncertainty.<\/p>\n\n\n\n

Cockburn updated an earlier version of this talk for 2026, adding the realities of AI, changing work environments, and modern delivery pressures. His core message was that while paperwork can be reduced or automated, the human work of project management remains essential.<\/p>\n\n\n\n

The Myth That Agile Eliminates Project Managers<\/h2>\n\n\n\n

Cockburn addressed the common belief that Agile methods replace project managers with self-managing teams. He argued this confused bureaucracy with leadership.<\/p>\n\n\n\n

If you remove time-sheet chasing, status paperwork, annual review administration, and similar tasks, there is still substantial work left:<\/p>\n\n\n\n

    \n
  • Coordinating people<\/li>\n\n\n\n
  • Removing interruptions<\/li>\n\n\n\n
  • Maintaining alignment<\/li>\n\n\n\n
  • Securing sponsor decisions<\/li>\n\n\n\n
  • Protecting budgets<\/li>\n\n\n\n
  • Building trust and communication<\/li>\n\n\n\n
  • Helping teams adapt when plans change<\/li>\n<\/ul>\n\n\n\n

    <\/p>\n\n\n\n

    He noted that early Agile experiments sometimes failed after removing project managers because nobody was left to represent the team upward, protect focus, or secure timely executive support.<\/p>\n\n\n\n

    What Projects Actually Look Like<\/h2>\n\n\n\n

    Cockburn described projects as messy, nonlinear journeys rather than straight plans. Teams begin with a goal and intended path, but real work includes reversals, surprises, and moments of crisis.<\/p>\n\n\n\n

    At those turning points, leaders must decide:<\/p>\n\n\n\n

      \n
    • Continue toward the original goal<\/li>\n\n\n\n
    • Shift to a better goal<\/li>\n\n\n\n
    • Avoid switching to a worse goal disguised as improvement<\/li>\n<\/ul>\n\n\n\n

      <\/p>\n\n\n\n

      He used examples such as Apollo missions, shipbuilding history, and major programs to show that uncertainty is normal. The project manager\u2019s job is not to enforce fantasy certainty, but to help teams make better decisions under changing conditions.<\/p>\n\n\n\n

      The Core Work of a Modern Project Manager<\/h2>\n\n\n\n

      Cockburn identified five conditions that strongly influence project success:<\/p>\n\n\n\n

        \n
      1. Executive nourishment<\/strong>
        Funding, sponsorship, and timely decisions<\/li>\n\n\n\n
      2. People quality<\/strong>
        Talent, skill growth, and motivation<\/li>\n\n\n\n
      3. Incremental development with reflection<\/strong>
        Frequent delivery cycles paired with learning and adjustment<\/li>\n\n\n\n
      4. Community quality<\/strong>
        Healthy communication, trust, and willingness to listen<\/li>\n\n\n\n
      5. Focus and alignment<\/strong>
        Shared goals and uninterrupted time to do meaningful work<\/li>\n<\/ol>\n\n\n\n

        <\/p>\n\n\n\n

        He argued that many of these factors sit directly in the project manager\u2019s sphere of influence. A good PM helps teams become cohesive, effective units rather than collections of individuals.<\/p>\n\n\n\n

        Communication Is Still the Main Job<\/h2>\n\n\n\n

        One of Cockburn\u2019s strongest themes was that most project problems are still people problems:<\/p>\n\n\n\n

          \n
        • Information hidden or delayed<\/li>\n\n\n\n
        • Teams not talking honestly<\/li>\n\n\n\n
        • Stakeholders disconnected<\/li>\n\n\n\n
        • Constant interruptions<\/li>\n\n\n\n
        • Poor collaboration across roles<\/li>\n<\/ul>\n\n\n\n

          <\/p>\n\n\n\n

          He tied this directly to the first Agile Manifesto value: Individuals and interactions over processes and tools.<\/strong><\/p>\n\n\n\n

          His warning for scaled Agile and AI-heavy environments was that organizations often keep ceremonies and tooling while losing the human collaboration Agile was meant to improve.<\/p>\n\n\n\n

          Why Incremental Delivery Matters<\/h2>\n\n\n\n

          Cockburn argued that Agile methods are especially valuable for fixed-date projects<\/strong> such as:<\/p>\n\n\n\n

            \n
          • Black Friday launches<\/li>\n\n\n\n
          • Government deadlines<\/li>\n\n\n\n
          • Major public events<\/li>\n\n\n\n
          • Regulatory deadlines<\/li>\n<\/ul>\n\n\n\n

            <\/p>\n\n\n\n

            In those environments, teams need rapid feedback loops, early testing, and the ability to trim lower-value scope near the end while preserving the most important outcomes.<\/p>\n\n\n\n

            He contrasted this with \u201cbig bang delivery,\u201d where teams discover problems only near the end when correction is expensive and late. Frequent probes, demos, prototypes, and partial releases help teams learn earlier and reduce risk sooner.<\/p>\n\n\n\n

            There Is No Single Best Practice<\/h2>\n\n\n\n

            Cockburn rejected rigid formulas. He gave examples of opposite tactics that can both be correct depending on context:<\/p>\n\n\n\n

              \n
            • Put everyone together for fast communication<\/li>\n\n\n\n
            • Isolate a key expert so they can focus deeply<\/li>\n<\/ul>\n\n\n\n

              <\/p>\n\n\n\n

              Both can work. The right move depends on the current bottleneck.<\/p>\n\n\n\n

              His broader point: project management is situational judgment, not checklist compliance.<\/p>\n\n\n\n

              Scrum Master vs Project Manager<\/h2>\n\n\n\n

              In Q&A, Cockburn explained that Scrum Masters and project managers overlap, but are not identical roles.<\/p>\n\n\n\n

              He described the Scrum Master as having influence without formal authority, focused on communication and team health. A project manager may additionally carry responsibility for sponsor visibility, funding, staffing, broader coordination, and delivery accountability.<\/p>\n\n\n\n

              So while some duties intersect, the roles are not interchangeable in many organizations.<\/p>\n\n\n\n

              Key Takeaways<\/h2>\n\n\n\n
                \n
              • Agile does not eliminate the need for project managers<\/li>\n\n\n\n
              • Bureaucratic tasks may shrink, but leadership work remains<\/li>\n\n\n\n
              • Communication and trust are still the biggest levers of success<\/li>\n\n\n\n
              • Incremental delivery reduces risk and improves learning<\/li>\n\n\n\n
              • Fixed deadlines often make Agile techniques more valuable, not less<\/li>\n\n\n\n
              • Good project managers protect focus, secure support, and guide adaptation<\/li>\n\n\n\n
              • Managing people systems matters more than enforcing paperwork<\/li>\n<\/ul>\n\n\n\n

                Final Thought<\/h2>\n\n\n\n

                Cockburn\u2019s central argument was simple: When projects become more complex and uncertain, the need for capable project leadership increases.<\/strong> Modern Agile teams still need project managers, but the role is less about control and more about enabling people to succeed.<\/p>\n","protected":false},"excerpt":{"rendered":"

                Alistair Cockburn explains the modern role of the project manager on Agile projects, showing how leadership, communication, stakeholder alignment, and incremental delivery drive success in complex environments.<\/p>\n","protected":false},"author":8033092,"featured_media":8107626,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[883,908],"tags":[2197],"event_session_cat":[],"session_aud_level":[494],"event_session_type":[],"content_source":[1697],"event_session_tags":[],"class_list":["post-8107624","aa_event_session","type-aa_event_session","status-publish","has-post-thumbnail","hentry","category-mindset","category-process","tag-free","session_aud_level-learning","content_source-agile-minicon"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_event_session\/8107624","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_event_session"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/aa_event_session"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/8033092"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8107624"}],"version-history":[{"count":2,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_event_session\/8107624\/revisions"}],"predecessor-version":[{"id":8107628,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_event_session\/8107624\/revisions\/8107628"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8107626"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=8107624"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8107624"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8107624"},{"taxonomy":"event_session_cat","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/event_session_cat?post=8107624"},{"taxonomy":"session_aud_level","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/session_aud_level?post=8107624"},{"taxonomy":"event_session_type","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/event_session_type?post=8107624"},{"taxonomy":"content_source","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/content_source?post=8107624"},{"taxonomy":"event_session_tags","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/event_session_tags?post=8107624"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}