Scaling from Project > Program > Portfolio - The Agile Transformation and Journey

schedule Feb 26th 04:30 PM - Jan 1st 12:00 AM place Esquire

The case in point is a journey of Agile transformation when the organization was looking to manage releases through shorter iteration cycles. As the journey began, the organization had to leapfrog into 3x growth in terms of both people and business needs due to a round of substantial investor funding.

The agile transformation started with just 6 teams in the organization and due to the nature of the team structure, the 3-member PMO team did not have the luxury for pilot projects and had to simultaniously roll out at one go across the 6+ component teams.

In a span of 6 months, the number of teams grew to 12+ and the number of releases more than doubled. Also, 80% of the releases cut across more than 3 teams and the challenge was to keep the process pretty lean. PMO team worked closely with key stakeholders from Product, Engineering, Architecture and Operations to forumate and roll-out a simple 3 step process that aided the teams to deliver releases better than before. Here is when the organization leaped from project to portfolio of releases cutting across 10+ themes.

Similar to what is quoted in the "Scaled Agile Framework" which the PMO tripped on much later in the process, there were organization wide prioritization done based on the product strategy, infrastructure and technology needs which eventually got translated into multiple programs within the organization, cutting across various teams. A concept of 3-in-a-box (PM, Architect and Engineering Owner) was formulated to bring in the required vigor in to the planning and execution process.The 3 in the box was further extended to Dev +QA + Ops who worked as a team to deliver the various stories across the contributing stacks.

The challenges across value-driven prioritization from 100+ releases across the portfolio, release planning with engineering and product, the execution framework and scalability in engineering infrastructure commensurate with the agile processes, working with operations teams and all the way till adoption was seamlessly scaled using the initial framework that was set for just 15 releases.

The presentation details how agile helped and is helping the product and technology teams in delivering better results than before. This would also detail the necessary Agile and operational metrics across the project teams, the program and the portfolio levels that aid the mid and senior management to take informed decisions. As always, this would not cover the IP and actual data of the organization but provide a clear framework to substantiate the process.

 
2 favorite thumb_down thumb_up 6 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

1. High level overview of the organization, team structure, what is a release in the system, dependencies. What is an Epic in our purview. How component teams can still exist which is an agile no-no.

2. The Agile Framework - 3 simple steps and how it has evolved over time as the organization grew

3. Experiments with Agile Flavors and techniques (including Engineering practices)

4. The Push and Pull Framework (Portfolio rationalization using value points, release planning using Agile scrum and the Kanban approach for execution)

5. Agile metrics relevant to engineering, product and business

6. Q & A

Learning Outcome

1. How continuous agility is an enjoyable and meaningful journey than a destination to aim for. It also lists how one needs to experiment with the various methodologies based on the need than fixating on one.

2. How engineering practices such as TDD, Continuous Integration need to significantly scale and aid the success of agile adoption in organizations. Also, how they were uncovered as being the problems.

3. How Agility is not just at team level but at organizational level (across product, biz, engineering, operations, biz operations and field teams)

4. How support from senior management and the team is so imperative for successful formulation and rollout of agile adoption

5. What and why to measure - Metrics - the necessary and sufficient ones for Agile Portfolio Management

Target Audience

Agile Project Managers, Agile Coaches, Scrum Masters, Engineering Leads, Architects, CxO

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Ellen Grove
    By Ellen Grove  ~  3 years ago
    reply Reply

    Thanks for posting your slides!

  • Vivek Vijayan
    By Vivek Vijayan  ~  4 years ago
    reply Reply

    I understand that you will present a case study on how you transformed your organization into Agile which will be really helpful. I did not understand how the scaling of agile adoption was carried out. If you can add some more details on the scaling as you have detailed in the starting that the business needs increased to 3X that yould be great. 

     

    Further, if "scaling" was not what you really want to talk about, by any chance does this proposal fall under "Agile lifecycle" theme?

    • Venkatraman L
      By Venkatraman L  ~  4 years ago
      reply Reply

      Hello Vivek

      Can you please confirm if your queires have been answered ?

      • Vivek Vijayan
        By Vivek Vijayan  ~  4 years ago
        reply Reply

        Hi Venkat

        Indeed. Thank you. 

    • Venkatraman L
      By Venkatraman L  ~  4 years ago
      reply Reply

      Hello Vivek,

      Based on your feedback, I have tried to detail the synposis of the entire presentation and flow. I have called out the reason for the 3x growth.

      There is quite a bit of synergy with the Scaled Agile framework (SAFe) and hence I do feel this is still very much part of Scaled Agile Adoption. The organization had scaled in terms of size and  business massively and the framework had to adapt and scale accordingly. The various Agile Methodologies such as Xp, Kanban and Lean were brought in beyond just Scrum. The concept of aligning the 3x growth in releases to the strategy and roadmap was super important.

      Kindly do let me know if you have more queries. The previous presentation is available as part of the writeup

    • Venkatraman L
      By Venkatraman L  ~  4 years ago
      reply Reply

      Hi Vivek,Thanks for the query. I shall be updating the proposal in couple of hours that should clarify your queries. I still beleive this falls under scaling agile but we can surely discuss that if you think it should move elsewhere. I am open to it :)

      Tx for your feedbak

      Venkat


  • Aman King
    Aman King
    Agile Technologist
    ThoughtWorks
    schedule 4 years ago
    Sold Out!
    20 Mins
    Experience Report
    Beginner

    Are you an Agile Practitioner? Or are you responsible for Agile transformation?

    Organizations that have begun their Agile journey welcome the guidance of an experienced Agile Coach. But external guidance cannot continue indefinitely as the only way to scale Agile.

    If you are in an Agile team, are you prepared to take on the coaching role for other teams once your Agile Coach moves on?

    If you are a manager, are you looking at grooming in-house coaches to scale and self-sustain transformation?

    The transitioning of practitioners into coaches can be key to your Agile journey. Individuals get to build on their potential, while the organization becomes more self-reliant.

    This session explores my personal journey from practitioner to coach. It should help you too in taking that first jump into the role of a coach. I will share real-world examples of dealing with on-the-fly situations, and of preparing upfront where possible. I will recommend resources, and mention handy techniques that should be in a coach's toolkit. The session essentially provides a kick-start for first-time coaches.

  • Liked Nikhil Joshi
    keyboard_arrow_down

    Nikhil Joshi - Build - Measure - Learn : Without spending a fortune

    20 Mins
    Experience Report
    Beginner

    At times we have great product ideas but the biggest barrier to entry lies in answering few questions such as:

    - How do I define and validate Problem hypothesis, Solution hypothesis and Underlying assumptions?

    - How do I quickly setup a platform for people to register their interest?

    - What will keep the potential customers engaged, excited until the first release (or beta) is out?

    - How do I get feedback from the early adopters?

    - And eventually when I have answers to some of these questions, how do I make a decision to persevere or pivot?

    If you've faced a challenge while answering any of these questions while building/validating your product idea, this session is for you. We'll look at tools and techniques to validate the product hypothesis early-on without spending months or fortunes. We'll also look at a case study to highlight how some of these tools, techniques helped us validate our product idea.

  • Liked Naresh Jain
    keyboard_arrow_down

    Naresh Jain - SAMPLE PROPOSAL - Product Discovery Workshop

    Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 4 years ago
    Sold Out!
    90 Mins
    Tutorial
    Beginner

    Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?

    Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.

    During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.

    This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.

    This is a sample proposal to demonstrate how your proposal can look on this submission system.

  • Liked Savita Pahuja
    keyboard_arrow_down

    Savita Pahuja - Battlefield Agility

    Savita Pahuja
    Savita Pahuja
    Agile Consultant
    Palo-IT
    schedule 4 years ago
    Sold Out!
    45 Mins
    Workshop
    Intermediate

    Battlefield Agility® is a quest to make our deliveries better, more collaborative, faster and effective. It relies on age old principle from the Army to provide a holistic view of the problem landscape which a project team needs to solve and be able to succeed in this, through small collaborative groups working in coordination to achieve the bigger goals.

    Battlefield Agility® derives from the Agile manifesto and principles and adds to it the key ingredient of individual wisdom to create a plan for a team which will help it succeed in successful deliveries . This is a goal based approach to increase MVP and ROI.

    The purpose of this method is to make team members more focused about their work, equal distribution of work in the team and increase productivity.

    Battlefield Agility enumerates the mechanisms of planning, better field view to all team members, ease of multitasking, reduce task switching.

    Key benefits of Battlefield Agility® 

    • A focused approach to software development as development proceeds through small battles to be won
    • Reduced multitasking and better efficiency of team members
    • Faster deliveries as the work is divided to right sized battles to be won
    • Parallel efforts by team members ensure the time to market is significantly lesser
    • Less process overhead as the collaboration is real time and more time is spent on the ground than on meetings
    • Small teams ensure close camaraderie and collaboration among team member
    • The team can even work on disparate work areas ( if required) in order to make best us of their expertise

     

  • Liked Tania van Wyk de Vries
    keyboard_arrow_down

    Tania van Wyk de Vries - Agile metrix: How do you measure the success of your agile implementation?

    45 Mins
    Case Study
    Advanced

    Humans are creatures of habit and agile is really challenging that part of our existence everyday. I have seen many teams thinking they now get agile and they take what they learned and just practice it everyday without really reflecting on where they are at or the fact that they are not really moving forward. So in order to say your teams and organisation are really becoming more and more agile everyday you need some metrix to measure against.

     

    The collection of the metrix are 2 fold:

    1. Metrix are tracked through the agile project management tools teams use. We have defined the below set of metrix to interrogate our data to tell us how we doing.
    2. Some of the metrixs are done by getting feedback from teams and clients through surveys.

     

    Some of the metrix include:

    1. Measurement of quality
    2. Measuring customer satisfaction
    3. Measuring team happiness
    4. Measuring continuous improvement in process and technical practices
    5. Measuring time to market
    6. Measuring ROI
    7. Measuring productivity
    8. Measuring overall project progress
    9. Measuring change and improvement

     

  • Liked Archana Joshi
    keyboard_arrow_down

    Archana Joshi - Applying Agile Principles in Primary School Education: An experience

    20 Mins
    Experience Report
    Intermediate

    An important issue that has plagued the Indian sub-continent is that of education and more importantly primary education. Since past few months, my weekends are usually occupied in teaching English classes to underprivileged children from 5th grade at a government primary school. As an Agile coach and a practitioner I was drawn towards unifying the concepts of Agile to help increase the quality of education.

     

    As a teacher, I was given a set of high level goal by the school administrator that needs to be accomplished every quarter. My goals for the first quarter were :

    • > Kids should be able to identify basic words
    • > Form short sentences.
    • > Converse reasonably in English

     

    I started with the traditional chalk and blackboard style of teaching focusing on the spellings, grammar, sentences, reading and so on. In initial few sessions, I quickly realized that it took too long for the kids to understand and so was not yielding the desired results. Some of the problems were like

    • > Too much focus on semantics and grammar
    • > Kids not opening up in the class room
    • > Only able to read words but not talk or frame sentences

     

    This is where I had to reflect and consider course correction in my style of teaching and Agile came to my rescue. This is a talk which highlights how Agile techniques were applied in teaching kids effectively.

     

     

  • Liked Rituparna Ghosh
    keyboard_arrow_down

    Rituparna Ghosh - Driving Continuous Improvement for Excellence through Lean Agile

    45 Mins
    Experience Report
    Advanced

    Despite being a CMMI Level 5 company, in the early 2000 business exigencies prompted Wipro to look towards a sustainable continuous improvement drive.  Wipro started it Lean-Agile transformation initiative way back in 2004-05. In the initial days, the euphoria of a new subject helped in the adoption. The evangelists came from the ranks and their success stories helped us in broadbasing the initiative. In the past decade or so the organization has grown 5 fold – not to mention the increase in the complexity of operations. The early adopters and evangelists too were not in a position to take ahead the journey. They often took up different roles either within the organization or externally. Knowledge became tribal in nature without there being a continuous cycle for continuous improvement. 

    This is a live case study of how the organization took ahead the transformation initiative and breathed fresh life into it, in an environment which was much more challenging. We built a cadence of Continuous Improvement by

    1. Adopting a SuHaRi model of Inform-Perform-Transform  
    2. Aligning the roles and responsibilities to aid Continuous Improvement
    3. Building a rewards and recognition programme for increased participation
    4. Involving Senior leadership to drive the cultural change by aligning policies and principles
    5. Measuring engagement and effectiveness – not only in terms of measurable metrics, but also in terms of intangible benefits
  • Liked Naveen Indusekhar
    keyboard_arrow_down

    Naveen Indusekhar - Enticement for Agile Team and Metamorphosis of Managers

    45 Mins
    Workshop
    Beginner

     

    What does productivity mean to the team? What does sponsor want from a team? What happens to Leads and Managers? A ROLE PLAY by JP and Naveen

    The topic assumes that the organization is medium or large sized (about 2K+ employees) and has recently migrated or is in the process of transitioning to Agile methodologies. Further, stakeholders are aligned to the idea and they are wholly in understanding of what and why they want to go (gone) Agile.

    Do you see a scenario in the corridor where a Manager is talking to another Manager – “What happens to us in future? Where do we go? Are we required in this organization? Agile is killing us.”

    Do you see Leads (by designation) saying to his Manager “Hey my career was set to take off – I was to become a Senior Lead, and a Manager in 4 years. Agile has made me an average team member and stalled my growth.”

    What about a team member to another saying “Man, there is no point in increasing the velocity – that becomes a bench mark for us and we need to sprint at that pace for the rest of our lives! I also had lot of time for myself in chunks when other functional group was slogging and I could read a book, attend a training, catch-up with my friends, blah, blah, blah. Let us add substantial buffer in estimates to have a comfortable life and commit on minimal ideal hours. Let us rock as a team!!!!”

    Or a Manager talking to HR “I’m unable to hit the bell curve as an entire team is involved in successful delivery of the project” and HR saying “Sorry, but you are violating global HR policy by not doing so – there ought to be a superior performer and a poor performer.”

    You may hear a team member saying “I was headed to becoming a super DBA and now you are asking me to pick testing tasks, web development task, etc. If I don’t spend 100% of my time in my domain, I will be termed as jack of all trades and master of none. This is not aligning with my career development plans.”

    A VP saying to another “Not sure if Agile has increased our productivity, how do I know it is productive? I understand teams are empowered and self-organizing, but are they self-productive? And what is this fuss about Managers’ not happy with “no-role”. Nothing should change for them.”

     

    A workshop where JP and Naveen play various characters to address these challenges in an Indian office context. Welcome to an enthralling way of presenting the core human challenges in Agile adoption and implementation.