Will the project manager and PMO disappear in the agile world

I will focus on a possible transition of organizations who are introducing the agile way of working. Starting with a traditional project setup using permanent PMO (portfolio level) and a temporary PMO (project level). What will happen if the keep the team together as an agile team. What does that mean for the project manager. I will continue my story by adding an agile team. Coordination between the teams can be managed by a scrum of scrum. Still no need for a project organization with a project manager and a project board and no need for a temporary PMO. I add more teams and the coordination asks for a project manager. What dos this mean for a PMO? We can continue and institutionalize the coordination by using frameworks like Nexus, S@S, SAFe et cetera and has an Integration Manager, a Roadmap Manager or a Release Train Engineer and Product managers and Product Owners. I will add some new to be created teams (aks for a Project Manager to organise) et cetera. I will end with an overview and positioning of different agile frameworks and the role of the permanent PMO (focus portfolio management and Center of Excellence) in an agile world.

 
4 favorite thumb_down thumb_up 3 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Intro
  • evolution of teams starting with a traditional setup and adding teams
  • consequences for Project Manager, PMO en Portfolio manager
  • Positioning of agile frameworks
  • depending on the time I can give some glimpses of some agile frameworks like SAFe, Nexus, LeSS

Learning Outcome

  • understand the added value of a permanent PMO in the agile world
  • insights in the consequences for temporary PMOs and PMO staff in the agile way of working
  • insights in the different agile frameworks and the positioning to each other (divided at team, program and portfolio level)

Target Audience

Executives, project, program and portfolio managers and PMO staff

Prerequisite

basic understanding of agile

schedule Submitted 2 months ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Fincy Yousuff
    By Fincy Yousuff  ~  2 weeks ago
    reply Reply

    Hello Henry!

    Thank you for your proposal!

    The topic as such is very relevant and having worked with the PM Community I can vouch that this has been a statement of dilemma for quiet some time. 

    Could you help me out with the following though:

    1) Could you mention how the presence of Agile PMO would help/benefit business or the organization? I see you have added functions/responsibilities in Slide 21. How would these reflect into benefits to the organization?

    2) I checked your website for videos from one of your previous talks. But I couldn't find any. Could you add a link to one of your videos with this proposal please?

    Awaiting your reply. Have a great day ahead!

     

    • Henny portman
      By Henny portman  ~  2 weeks ago
      reply Reply

      1). If I look at agile PMOs I see the following business advantages:

      - they can support the organization, in their role as a lean/agile centre of excellence to introduce new ways of working to speed up delivery, faster time to market etc

      - they can play a key role in the agile transformation, to increase the business agility of the organization so the can act or react faster on external business opportunities.

      - they, in their role as portfolio management, can translate the organizational strategy in agile team demand. As a consequence they will give the trigger to downsize the number of agile teams supporting a product that will not be of strategic importance anymore. The PO will not do this. The PO will continue to build up the backlog to keep the team(s) busy. Other way around is also true. If a new product will be introduced as a result of the strategy the trigger for new or additional agile teams will come again from the agile PMO.

      2). On my blog I have stated the last presentations I gave. I would assume that recordings will be presented via the links on the websites of the conference organizations. Last month my two presentations during the conference in Marrakesh were recorded but they are not yet on their site. I know my latest webinar is available on the Fortes site but that one is on audio and in Dutch. So I am really sorry I can not supply by myself any recording. The presentation in Marrakesh is close to this one. Maybe you can contact the organizer to get direct feedback (Farid Yandouz <farid.yandouz@trustedadvisors-group.com>) regarding my presentation. Please let me know if you need more information. Best regards Henny

      • Fincy Yousuff
        By Fincy Yousuff  ~  2 weeks ago
        reply Reply

        Thank you Henry for adding this information!

        For those who would be reading the proposal, I felt it would be a good addition if the benefits are mentioned. That way they know not only "what" the role of Agile PMO is but also "why" an Agile PMO will be beneficial in their organization.

        Have a great day!

         


  • 45 Mins
    Talk
    Intermediate

    Story is a profoundly important device to unite design teams around a shared product vision. This powerful communication tool helps us retain information and empathize with others. As companies scale and teams sprint through product iterations, it’s easy to lose sight of how your product should fit into the lives of your customers. The best way to keep everyone pointed in the right direction is with a clear, compelling story—a story that will unite and guide teams towards success.

    But how do we fold storytelling into our design practice? Aarron Walter uses real-world stories of product teams at Disney, Apple, Airbnb, Twitter, and more to show how storytelling improves team communications and elevates design practice.

  • Liked Gopi Kallayil
    keyboard_arrow_down

    Gopi Kallayil - 9 Principles of Innovation at Google

    45 Mins
    Case Study
    Intermediate

    Since its founding, Google has created six products that each have at least a billion monthly users. Google continues to innovate rapidly, and in many new areas. The organizing principles and cultural elements that drive this monster of innovation are a hot topic among designers. So what are they? Find out in this engaging talk by Google’s Chief Evangelist, Brand Marketing.

  • Liked Anand Bagmar
    keyboard_arrow_down

    Anand Bagmar - Build your own MAD-LAB - for Mobile Test Automation for CD

    45 Mins
    Case Study
    Intermediate

    In this age of a variety of cloud-based-services for virtual Mobile Test Labs, building a real-(mobile)-device lab for Test Automation is NOT a common thing – it is difficult, high maintenance, expensive! Yet, I had to do it!

    Attend this talk to understand the Why, What and How I built my own MAD-LAB (Mobile Automation Devices LAB). The discussion will include –

    • Understanding the context,
    • Why no cloud-based solution worked for me,
    • The automation strategy for Android / iOS / Web platform,
    • The tech-stack (cucumber-jvm / Appium), and,
    • The core implementation to build your own MAD-LAB! (already open-sourced)
    • How this results in Continuous Delivery (CD)
  • Liked Jutta Eckstein
    keyboard_arrow_down

    Jutta Eckstein - Beyond Agile – Preparing for Digitalization

    45 Mins
    Talk
    Intermediate

    The digitalization calls for rapid organizational flexibility and adaptability. This has an impact on all dimensions of a company: its strategy, structure, and the processes. Agile will help implementing some of this flexibility and adaptability yet mainly in terms of processes. Thus, the digital transformation needs companies to change beyond Agile. Beyond Budgeting, Open Space, and Sociocracy provide the missing links for a company to fully embrace digitalization. The combination of these concepts enables a company not only to survive but also to thrive (digital) disruptions.

  • Liked Anton Zotin
    keyboard_arrow_down

    Anton Zotin - Why your company will most probably not become Agile?

    Anton Zotin
    Anton Zotin
    Agile Whisperer
    FlixBus
    schedule 2 months ago
    Sold Out!
    45 Mins
    Talk
    Executive

    You have tried Scrum, Kanban, XP, Crystal and other even less known frameworks and methods that claim to help you to become Agile. You have applied them pure, you have tried to tweak them, and even you have made some homemade cocktails out of them. So yet you still can't say your company is Agile. Your Cxx-s are willing to change the company, and themselves. Your employees on all levels genuinely want to step into the Agile journey. Yet there is nearly no progress toward a real organizational agility.

    What is the secret? Why is it so hard? Why there are so many crashes on this way in our industry? Why most of the companies will still fail to become Agile, and yours will most probably too.

    I'm going to answer all these questions during this talk. We will figure out what aspects of a large-scale agile transformation have a mission-critical impact and how they influence each other. Where to put your efforts? How to cut corners? And moreover, how to survive on this journey.

  • Liked Asheesh Mehdiratta
    keyboard_arrow_down

    Asheesh Mehdiratta - How do you rejuvenate your fading Communities of Practice?

    Asheesh Mehdiratta
    Asheesh Mehdiratta
    Transformation Leader
    Shell
    schedule 1 month ago
    Sold Out!
    20 Mins
    Talk
    Advanced

    As part of organizational digital transformation journeys, CIOs are moving from hierarchical models to 'self organizing' Feature teams, in order deliver efficient and effective IT, but still need to retain the deeper functional expertise. Hence the growing importance of building and sustaining "Communities of Practices" (CoPs), as the traditional functional silos are broken down, with the transformation themes.

    But if you are a Change Agent responsible for the Transformation, you understand how challenging it is to nurture, and especially sustain these CoPs.

    So join my session, as I will share how I have used the ADKAR change concepts to form my own RECIPE for building, nurturing and especially sustaining enterprise wide Communities of Practice (CoPs).

    You will pick up this simple framework, along with instant techniques, tips that you can apply, and learn from my experiences in overcoming the challenges of scaling communities, and working with distributed communities.

    You will be able to recognize the success and failure patterns, and in the end will walk away with practical advice on building "long lived" Communities.

    Come join my session to change your WORLD!

  • Liked Nilesh Kulkarni
    keyboard_arrow_down

    Nilesh Kulkarni - Outcome Based Agile Coaching

    45 Mins
    Workshop
    Intermediate

    Session name - Outcome based agile coaching

    We all want to become good agile coach. But what does that mean? How do you get better outcome from your agile coaching sessions? In this session, participants will experience how to improve outcome of your coaching session. Some areas we will focus in this session are output Vs outcome, why, what, how of coaching, how to make coaching outcome etc.

    This will be a hands on workshop with very minimal guidance from facilitator. Participants will have experiential learning through the activities to understand how to align agile coaching to deliver maximum impact on business outcome.

  • Liked Gaurav Rastogi
    keyboard_arrow_down

    Gaurav Rastogi - Agile Vendor Management Manifesto

    45 Mins
    Talk
    Executive

    Want to discuss and share the Manifesto which a group of coaches including myself have written.

    Please refer to www.vendormanagementmanifesto.org for details

    1.1 The Governance
    The delivery team is governed by contracts. There are 2 types of contract we will be considering
    •The Master Contract : This is a contract signed between the Customer and Supplier Management teams and governs the entire set of Scrum projects being executed.
    •The individual work order level contracts: This is a contract which will govern the detailed work to be done by teams.

    This manifesto will take into account both the type of contract

    1.2 The Roles
    The roles covered under this Manifesto are as follows
    The Customer Management This is the management team of the customer
    The Vendor Management Team Vendor Management team will work on behalf of the Customer Management team in preparing the contract and negotiating the same with the Supplier’s management
    The Team The team will consist of multiple Scrum teams working on the projects governed under the Master Contract. They will end up working under the individual Work Orders signed up with the customer.
    The Supplier Management The Supplier Management team will negotiate the terms and conditions of the Master Contract of the contract along with the The Customer Management team (and the Vendor Management team).

    1.3 The Objective of this Manifesto

    The Objective of this Manifesto is to define guiding principles around the Customer-Supplier working environment with regards to working on Scrum projects. The assumptions made are
    •The environment is customer-supplier (i.e. an outsourced environment)
    •The environment is distributed and may not be co-located
    •The environment involves multiple vendors

    The Customers and Suppliers are integrated elements of a working environment in a project. The Customers and Suppliers will work together with a common goal and that is “Producing Value for the End Customer”. This manifesto supports the Agile Manifesto Value “Customer Collaboration over Contract Negotiation”.

    There are 12 principles which will support the Agile Value and are presented below in a format of Left over Right. The items on the left are valued more than the ones on the right.

  • Liked Pavel Dabrytski
    keyboard_arrow_down

    Pavel Dabrytski - Psychology of Coaching: Understanding Science of Change

    Pavel Dabrytski
    Pavel Dabrytski
    Agile Coach
    Think Agile
    schedule 1 month ago
    Sold Out!
    90 Mins
    Workshop
    Advanced

    In October 2016 I received a call, "Hey dude, I don’t know nothing about Agile, but I need to become an Agile coach a-s-a-p – my company just got a new contract." I laughed for a second, explained that it takes a bit longer than a week to learn to coach, and wished him luck. I also knew that, shortly, he would be walking into his customer's office in this new role.

    Agile Coach is the new black! But how can you, a good coach, stand out from the crowd of less competent peers? Let me offer you this workshop to explore the science of coaching and the ways in which it works. We start with concepts of neuroplasticity and the brain processes of creating new neuron pathways. Then we move to motivation and learn which type is the best. Finally, we finish with the discussion on brain activation states which we practice in a few short exercises. By understanding the new field of coaching psychology, you will become a better practitioner.

    I am an affiliate member of the Institute of Coaching at McLean Hospital, the Harvard Medical School affiliate. I studied coaching psychology at Harvard Extension School.

  • Liked vinaya muralidharan
    keyboard_arrow_down

    vinaya muralidharan - Psst...your data could be lying to you!

    vinaya muralidharan
    vinaya muralidharan
    Agile Coach
    Capgemini
    schedule 2 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Lies, damned lies and Statistics!

    (the phrase is frequently attributed to the British Prime Minister Benjamin Disraeli).

    Many of us work in environments that value Agility or are at least attempting to be more Agile.

    We frequently turn to data, metrics, reports to help us navigate through our complex software environments, to help make sense of what's happening, to support subjective information we see around us and gain insights about the way we work.

    But with the myriad of reports and metrics available to us, it is easy to misinterpret, over-analyze, overlook and generally make a big mess of things.

    Through this talk, I will present some of the popular Agile reports and metrics and how they can be misread.

    I will also share tips of how to counter some of these "lies".

  • vinaya muralidharan
    vinaya muralidharan
    Agile Coach
    Capgemini
    schedule 2 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Product Owners and others responsible for creating and maintaining the Product Backlog often focus on functional items.

    With good engagement in the Backlog Management process from the Development Team and Architects, technical and architectural items also find their way into the Product Backlog.

    But what about the human-centric items related to accessibility, inclusivity, internationalization and sustainability?

    Through the talk and with the help of several supporting examples and a short exercise, I would like to highlight the importance of addressing these aspects in the Product Backlog. The examples will include examples of good and bad backlog items and design decisions.

    I will also share some tips on how Product Owners and supporting roles can work these aspects into the Backlog Management process. These will include some ideas from Design Thinking but will not be limited to that.

  • Liked Laxman
    keyboard_arrow_down

    Laxman - Playshop on Strengthening Customer Centricity through Digital Transformation

    90 Mins
    Workshop
    Intermediate

    Business organizations are seeing seismic changes, and the business
    landscape is continuing to evolve. In an age of rapid digital
    transformation, customers are choosing a myriad of ways to interact
    with your organizations. It is thus imperative that organizations stay
    ahead of the curve to achieve its strategic goals in service excellence.

    The playshop will be dynamic, highly engaging using a Hands-
    On, Minds-On Learning approach to producing a deeper, more meaningful understanding through an experiential process.

    Building a customer-centric organization by pushing customer-centric
    culture to the next level. Customer Centricity is all about a Customer
    Centric Culture. The responsibility of Customer Centricity in an
    organization is with the employees.

    Customer-centric culture aligns your product and service with current and future needs of a defined set of customers to maximize mutual long-term financial value. It depends on an organization’s capability to understand, predict and respond to customer, market and competitor dynamics. A Customer-Centric Culture transcends individual departments and functions; it integrates the way all employees behave and perform.

  • Liked Alhad Akole
    keyboard_arrow_down

    Alhad Akole - Trust the Stranger!

    Alhad Akole
    Alhad Akole
    Agile Coach
    Shell
    schedule 3 weeks ago
    Sold Out!
    20 Mins
    Experience Report
    Advanced

    In Distributed Agile many times, people don't trust members on other shore. My topic will cover few of the aspects which has helped our teams to gain that trust of customer and give co-located results.

    In Session I will speak about case study covering below points which helped our customer who is a “first time offshore” to “Trust the Stranger”!

    1) Building the Trust

    2) Creating Continuous Visibility

    3)Rotation of resources between shores

    4)XP practices

    1)Code Ownership

    2)Use of technology to share code/ builds

    5) CI CD – tools enhance visibility

    6) Test Automation to look at Tested Running Features

    7) Speak about my code! - Technical presentations within teams

    8) Explore Business Flows!- Business Understanding among Business Owners, Product Owners, Proxy PO, team.

    9) Innovations in business areas

    10) Distributed Agile – tools techniques

    11) Measuring the business Value (using custom Framework)

    12) Saying No!

    13) Re-Enforcing agile Practices!

  • Liked Pooja Wandile
    keyboard_arrow_down

    Pooja Wandile - DevOps For Legacy Systems: A Roller Coaster Ride

    20 Mins
    Experience Report
    Beginner

    Every organization aspire for faster time to market, release of features on demand, reducing the time between concept to cash and better quality of products. Agile has been a popular choice to achieve this objective. While agile was becoming a streamline approach, software industry saw the advent of DevOps. By adopting DevOps practices, organizations were trying to bridge the gap that existed between different groups within the organization, such as business, delivery, QA, Operations, Infra, etc. In spite of adopting agile practices, organizations were not fast enough to respond to changes. And one of the major reasons was the misalignment of purpose and processes withing these groups, hence while features were dev ready but it would still take the same amount of time to release to market as it was before. That's where organizations found the missing piece in DevOps in the entire delivery process.

    Everyone started hoping on it without realizing the complexity involved in its adoption. It is now a big buzzword in the industry. DevOps involves bringing changes not just in the delivery but also in the operations. with greenfield projects its a bit easier than doing it with legacy systems because greenfield projects have the opportunity to start from scratch which legacy systems lack.

    The purpose of this proposed talk is to share experience of devops implementation on such legacy systems which are complex and not just on its own but a web of multiple systems working together. How scaling devops practices becomes a necessity when working with enterprise applications.

  • Liked Atulya Mahajan
    keyboard_arrow_down

    Atulya Mahajan / Kiran Chhabra - Parenting Lessons for Agile Transformations

    45 Mins
    Talk
    Intermediate

    Agile transformations are no child's play. There is inertia, restlessness, impatience and the constant desire to run away. Traits that anyone who has been a parent to little kids has encountered, and learnt in their own way how to handle.

    This session looks at parallels between parenting and trying to influence teams through an agile transformation. We look at some of the things that successful parents do that can be done by leaders trying to take their teams through a transformation.

    Because if teams sometimes behave like children, the leader needs to be a parent too!

  • Liked Sunil Mundra
    keyboard_arrow_down

    Sunil Mundra - Be Alive, Be Agile

    Sunil Mundra
    Sunil Mundra
    Principal Consultant
    ThoughtWorks
    schedule 1 month ago
    Sold Out!
    45 Mins
    Talk
    Executive

    The Key challenge organisations are facing today is having to deal with the exponential rate of change which is happening in the external environment. The extent and pace of change is so disruptive that no organisation, regardless of age or size can take their competitive advantage or even their survival for granted.

    The main reason why organisations are struggling to change is that they are modeled as mechanistic or close-ended systems. On the contrary, all natural socio-economic systems essentially which are living systems have dealt with change very effectively since eternity.

    This talk is about infusing life into organisations. The speaker will highlight the key characteristics of living systems which enable them to deal with change effectively and also suggest actionable guidelines that will help leaders/influencers to bring their organisations to life. This approach will enable organisations to not only survive but thrive on change.

  • Liked Mangalam Nandakumar
    keyboard_arrow_down

    Mangalam Nandakumar - Why story points make no sense for a product company

    45 Mins
    Talk
    Advanced

    T-shirt sizing. Fruit Sizing. Planning pokers. You might be familiar with any or all of these estimation (relative sizing) techniques. Story points based estimations (along with velocity mapping) is touted as a predictable method to plan for software delivery. Teams are expected to get a good sense of the effort needed to deliver a piece of work by comparing estimates with references of similarly complex work they have delivered in the past.

    The accuracy of point based estimates fares more or less in the same range as sheer gut feel. So, the natural inclination for software teams is to try and make it more accurate than gut feel. Thereby, we obsess with breaking functionality into smaller byte sized stories. We freak out when there is "scope creep". We debate endlessly about ideal days vs. person days. We fuss over the specific visual representation for the burn-up or burn-down.

    Does it matter anymore how many days the team spent chipping hard at a feature that added no value to the business? Have we made agile teams into mini waterfall teams by focussing on the wrong metrics? Can product companies afford this?

    Process heaviness in product companies can cost a lot. We need to find better ways to invest in success metrics. We need to change the conversation from productivity to value add.

    My talk intends to challenge prevalent estimation practices and contest their validity in product companies. I will also introduce ideas around capturing relevant business metrics and sizing stories using business value.

  • Liked Sandip Shah
    keyboard_arrow_down

    Sandip Shah - What to do when order to follow is: ‘You need to follow Agile from now on!!!’

    Sandip Shah
    Sandip Shah
    Project Manager
    Allscripts
    schedule 4 weeks ago
    Sold Out!
    20 Mins
    Demonstration
    Beginner

    Purpose of the session is to discuss about Agile implementation approach and acceptance

  • Liked Sandeep Yadav
    keyboard_arrow_down

    Sandeep Yadav / Nisha Yadav - Building Roadmap for Scaling Agile

    45 Mins
    Talk
    Executive

    Today's enterprises operate in highly complex and uncertain environment and Agile adoption is highly challenging in such large organizations.

    While the context for each Agile transformation is different and there are several scaling models readily available, the components of the Agile implementation road map which ensure outcome are of universal nature.

    This session will cover model for building the roadmap and the activities to be carried out by Agile leaders and Agile Coaches for successful Agile implementation at scale.The model covers why to? How to? What to? When to? and Duration? for each component on the roadmap.The model will lay foundation for crafting the Agile implementation strategy and also to write the Agile implementation business case. The model is based on my practical experience of large scale Agile implementations.

  • Liked Koti Reddy
    keyboard_arrow_down

    Koti Reddy - Scrum and Human Body - An Analogy

    Koti Reddy
    Koti Reddy
    Agile Coach
    UnitedHealth Group
    schedule 1 month ago
    Sold Out!
    20 Mins
    Experience Report
    Intermediate

    I would like to take an analogy of comparing the Scrum Framework with a human body. The human body consists of cells, tissues, organs and the human body system relies on collaboration and coordination of all the parts of the human being in self-organization way to keep the body healthy and functioning. Similarly in scrum framework, the roles, events, artifacts and rules together work like a human body to keep the scrum sustain and work for not only to it but to everyone.

    Human body cells employ iterative and incremental approach. They divide and multiply. That allows the body to grow and to replace damaged or worn cells. Similarly, in iterative and incremental manner, Scrum helps to build more valuable products over a period of time.

    Empiricism is like the sensory experience which helps in the formation of ideas and making decisions. Also the introspection at regular intervals and taking corrective actions to improve as an individual is similar to the empiricism. Three pillars for the individual’s existence are Body, Mind, and Spirit. Balancing is the key to create an extraordinary life.

    Similarly, Transparency, Inspection and Adaptation are the three pillars to sustain the Scrum framework. Also the principles of shared visual work space, self-organization and empirical process which make a scrum team successful.

    Similarly i will be providing a view on all the scrum essentials analogy