Research paper on 'What happens to Engineering Manager in Agile world'

This is an extremly simple topic with a very complex answer. I have spent last 3 years experimenting and working with lot of people to understand what happens to the so called Manager role in Agile world. With a self organizing, empowered team, does Manager still have a role? Do you shelve these senior people who drove all your deliverables in the past for your company? Do you just let go the technical expertize these people bring along?

The research information around the experiment and results will be shared and am very positive that this will help lot of organizations move forward with great benefits. We will see how certain gaps that are created with introduction of Agile can be solved through these senior professionals. At the same time teams don't need to compromize or business doesn't need to compromize on new found agility by adopting any of the Agile practices.

The very next discussion that I will touch base as part of this presentation is the role of Project Leads. Many Leads resist movement to Agile because they feel their growth will now be stagnated. Is this true? It is again an interesting data set captured by talking to Leads in waterfall world and understanding what they really aspire for.

Looking forward to sharing my insights with real implementation and resulting data that I'm sure each of you will benefit from.

 
 

Outline/Structure of the Case Study

1. Introduction to the problem statement: "What happens to Engineering Manager in Agile world?" - 5 min

2. Present various implementations that have been done in the industry and why they didn't work in general - 5 min

3. Deep dive into implementation that has worked for the author post assesment of all other methods - 10 min

4. Share actual data around "new role of an engineering manager" and his engagement cycle - 10 min

4. Deep dive into understanding similar challenge in the Lead role in waterfall method and proposal of an answer to that in Agile world - 5 min

5. Counter arguements and Q & A. - 10 min

Learning Outcome

In an Agile world, contrary to the belief that certain roles become redundant, one can learn that these roles can be more productive and add more value to your business if managed well. By letting certain segment mismanaged, your organization can topple very fast. It is an inclusive journey and it is just a mindset change of being Agile that matters. The great positive learning by the author in his own experience is bound make many take advantage of this technique without having to suffer the pains of the journey.

Target Audience

Anyone practicing Agile

schedule Submitted 6 years ago

Public Feedback


    • Joshua Kerievsky
      keyboard_arrow_down

      Joshua Kerievsky - Anzeneering

      Joshua Kerievsky
      Joshua Kerievsky
      CEO
      Industrial Logic Inc.
      schedule 6 years ago
      Sold Out!
      60 Mins
      Keynote
      Beginner

      Anzen. It helped a 100-year-old, 60,000-person aluminum manufacturer regain its greatness. It powers the culture, operations and massive growth of an online artisan marketplace. It's the common denominator of every great Lean and Agile principle and practice. Anzen is the Japanese word for safety.

      Every day, your time, money, information, reputation, relationships and health are vulnerable. Anzeneers protect people from injuries, hazards or near-misses by establishing anzen in relationships, workspaces, codebases, contracts, processes, products and services.

      When anzen is present in a software product, everything just works: people regularly use and recommend the product; engineers modify it without fear; it contains few defects; it can be deployed with ease; it is immune from threats; and it helps protect the organization's finances, reputation and investors. Anzen is a gateway to habitual excellence.

      Anzeneers approach failure as an opportunity to introduce more anzen into their culture, practices, and tools.

      In this talk you will learn what anzen is, how it promotes safe risk taking, how to identify faux safety, when it can be taken too far, challenges of growing an anzen culture and what it means to be an Anzeneer.

    • Ankur Sambhar
      keyboard_arrow_down

      Ankur Sambhar - Promiscuous Pairing - Yes it works !!!

      Ankur Sambhar
      Ankur Sambhar
      Vice President
      J P Morgan
      schedule 6 years ago
      Sold Out!
      20 Mins
      Talk
      Intermediate

      Being Agile developer, have tried & tested various flavors of pair programming over the years while working in highly motivated self-managed team. Some experiments worked while some worked better :)

      This talk is about sharing the personal experience of practicing promiscuous pairing which allowed the team to be always in the beginner's mind state and being able to push the boundaries consistently.

    • Sachin Natu
      keyboard_arrow_down

      Sachin Natu / Naresh Jain - Inverting Test Pyramid - A First Hand Experience Report

      45 Mins
      Experience Report
      Intermediate

      Test automation is extremely crucial in adoption of an agile delivery. However, it can take one for a ride, if the approach is not correct. In this sensational, heart throbbing, experience report, we'll share our story of how we turned around an inefficient, expensive automation style to lean, efficient style. In addition to sharing a real-world example, we'll also share some of the key challenges we faced and how we solved them. If you are convinced about the Testing Pyramid, but are struggling to invert it, then this session is for you.

      Business Impact:

        Earlier Defect Detection - Higher test coverage at Unit/Intermediate layers lead to earlier defect detection. Reduced number of issues found on higher test environments/Production. Reduced cost of defect fixing.

        Reduced maintenance cost - UI tests are fragile and costlier to maintain Vs backend tests. No of changes in services layer are comparatively less.

        Reduced test execution time - Backend tests are much faster. Almost 7-10  times faster than UI Tests - improved build certification time.

        Test feedbacks are naturally distributed across layers of application. Test feedbacks are more pin pointed/ granular.

    • Naveen Indusekhar
      keyboard_arrow_down

      Naveen Indusekhar - 9 Steps to Agile Adoption: a fail-safe experiment

      45 Mins
      Experience Report
      Advanced

      While Agile adoption and practice is a complex model for mid/large sized Product companies to implement, we see a need for some sort of framework that can help drive it.

      Why do you need to be Agile? Where do you start, when do you start, and also how do you start? These are questions that reside in most of us during early stages of adoption. Here is a 9-Step breakdown that will help companies and teams adopt multiple Agile methodologies in different situations and scenarios. Maturing it from a ‘Persona Perspective’ framework helps the ‘decision-maker’ have a case for investment, further evaluate if it works, and improve it all through!!

      The discussion and idea is just my proposal that should help a team or an organization and is need not be the only way to implement Agile in an organization. Further detailing into these phases can form an overall Mindmap structure that is open to adopting from an organization and people standpoint.

    • Pooja Wandile
      keyboard_arrow_down

      Pooja Wandile - Scaling Scrum To Large Distributed Teams and its Challenges

      Pooja Wandile
      Pooja Wandile
      AD
      CTS
      schedule 6 years ago
      Sold Out!
      60 Mins
      Experience Report
      Intermediate

      As designed for use, Scrum works well for small co-located teams, cross functional teams. As the popularity of Scrum starting growing, more and more companies started adopting Scrum with mixed results. But overall, the trend has been increasing. Off late, big enterprises have also started adopting agile for their business needs and building complex products. In a recent study, the number of enterprise customers adopting scrum has doubled in last 2 years and they have used distributed scrum on large programs. So, the question is, can agile scale beyond small and co-located teams and what challenges could be there?

      This presentation talks about our experience of implementing scrum on a large program, the challenges of scaling scrum and how to overcome these challenges.