Decoding Portfolio Management in Agile Scrum Enterprise

Being agile enables the software development groups in Enterprises to deliver high value and high quality software with speed. However legacy applications along with the overall Enterprise landscape pose their own challenges that are outside of the scrum framework to solve.

Multiple small scrum teams though working on separate applications need to be cohesive with a big picture. As a portfolio lead, who owns multiple applications and teams related to a portfolio within an Enterprise is a Chicken in scrum terminology. The expectation from the role is that of leader, scrum master as well as an Architect providing technical and functional oversight to the teams within the portfolio. This session is about a retrospective of our work life as a Portfolio Lead who takes care of multiple scrum teams, and applications. We would like to speak about the top 3 challenges faced such as Scaling Production Support / Knowledge Retention for applications delivered through Scrum, Impact of Organizational Transformation initiatives on the scrum teams, People challenges in scrum teams and Multiple Stakeholder Expectations / Conflict Management through real life examples of our work. We would retrospect what we did, and discuss and debate what worked well, and what did not.


Outline/Structure of the Case Study

Proposed duration 45 minutes. We would like to conduct the session as a talk, discussing through the top 3 challenges as we retrospect about each of the issues that we faced related to that. We would summarize each of those, and interact with the audience to understand their opinion and experiences. This session is a Case Study where we would like to perform a retrospective of my work life as a Portfolio Lead who takes care of multiple scrum teams, and applications. The session would focus on top 3 challenges faced:

  • Production Support / Knowledge Retention for applications delivered through Scrum
  • People challenges the scrum teams
  • Multiple Stakeholder Expectations / Conflict Management

We would spend a few minutes setting the context so that the audience can relate to the challenges that we speak about. Then we would jump into discussing the three points mentioned above. For each of the points mentioned, we would walk the through real life examples of my work detailing the issue. We would speak about what we or our group did to address the same. Then we would retrospect what We did, and discuss and debate what worked well, and what did not during the same. It would be an interactive session where the audience would also be involved as we would love to engage the audience in the retrospective discussion.

Learning Outcome

Audience would have the following key takeaways:

  • Understand and Identify the challenges associated with scaling scrum adoption for multiple inter-related teams
  • Listen in to the real life problems faced by a portfolio lead
  • Discuss and Debate as we retrospect why certain problems or situations occured, what worked well and what failed
  • Take back ideas to apply while leading multiple inter-related scrum teams

Target Audience

Portfolio managers, project managers,

schedule Submitted 5 years ago

Public Feedback

    • Liked Sudipta Lahiri

      Sudipta Lahiri - 10 (Understated) Lessons from TPS!

      Sudipta Lahiri
      Sudipta Lahiri
      Sr. Vice President
      Digite Inc.
      schedule 5 years ago
      Sold Out!
      45 Mins

      I talk about 10 lessons from Toyota Production System that are important but not talked about.

      Lesson I: Getting the foundation right!

      Lesson II: Be patient to get the foundation right!

      Lesson III: 3S vs 2S

      Lesson IV: Three stages of Seiso

      Lesson V: Understanding Seiketsu

      Lesson VI: Implementing Shitsuke

      Lesson VII: Improvement initiatives are harder to sustain

      Lesson VIII: Keep broadcasting your success

      Lesson IX: Kaizen vs Sustenance

      Lesson X: Lessons from 3MUs and Visual Management


    • Liked Sarabjit Singh Bakshi

      Sarabjit Singh Bakshi - Art of Processing People in batches - Lets Re-factor our Schools

      45 Mins

      My talk will be highlighted on the currrent Education System and how Agile and Lean Mechanisms can help us refcator our education System . As we all proceed in this digital world its important to understand what extra can we do to make our children education more informative and creative . Using Agile and Lean from Gurukuls to Modern school- what do we think -Is the current education system is helping our students . Would like to give an insight on where are we going how we can improve it and how we all can contribute to make it better. We can talk on using Agile as Change Agent towards transforming the way our children precieve learning. 

    • Liked Om Prakash Bang

      Om Prakash Bang - Writing Excellent Requirements in agile way

      90 Mins

      Traditionally Project Manager was playing a role of Business Analyst in a small and medium organizations.  Leading organization have come to understand that Business Analyst as a separate role is critical for success of a project.  As organizations are undergoing agile transformation and adoption, role of business analyst need to be redefined. What are the different options for Business Analyst in scrum; Partner with Product Owner?  Transition to Product Owner?  Part of Agile Team? What are the characteristics of agile BA? The core activities, skills remain same, but the way they perform differs.

      This presentation is to give walkthrough on

      • Role of Business Analyst in agile
      • Progressive elaboration of Product Backlog Items / Feature / User Stories
      • Requirement communication in agile
      • Quality of Product Backlog Items / Features / User Stories
      • Factors in writing excellent requirements 

      Why product backlog refinement is important for the success of agile project? How it improves productivity of team?  What should be the writing style and how much level of details is good enough. The session also includes 30 - 45 Minutes of workshop on requirement elicitation.