The matrix organization of yore relied on maximizing returns on each skillset. This lead to having line managers and practice horizontals.
Engineering managers looking after developers and practice managers looking after the respective practices of BA, QA and PMO. This lead to having multiple lines of reporting for team member whilst on the project.
In Agile teams, focus is on the self organising teams of empowered employees working towards common success criteria (project success is team success). Not everyone can be a PO or a Scrum Master. So is the role of so called line managers or practice managers become redundant?
Whats their role in the agile teams?
How their role needs to transform

In this talk I will be addressing these questions. Bring out how some of their responsibilities are now taken up by the team or Product Owner or Scrum Master. I will also be suggesting how line managers can take this as an opportunity to morph into more meaningful roles that help the organization and teams. 


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

Outline/structure of the Session

2 mins - introduction with audience poll on various roles that they are playing - Coaches, Agile Team members,Line managers, Program managers etc.

2 mins - overview of current role of a Line manager

5 mins - Which of those responsibilities are valid and not valid in agile teams? with a show of hand for each of those responsibilities

10 mins - How does the role of the line manager transforms with Agile

15-20 mins - How to make this transition

10 mins - Q&As

2 min - Summary     

Learning Outcome

Participants will learn:
* Responsibilities that line managers can let go
* A new set of R&Rs for line managers
* A new model for organizing teams

Target Audience

Teams adopting Agile, Project managers, Line Managers, Agile champions within organizations

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Tathagat Varma
    By Tathagat Varma  ~  3 years ago
    reply Reply

    Pankaj - I think this topic has been beaten death to death in agile conferences many times over. I think, what will be more interesting to audience will be to talk about real-life experiences of erstwhile managers who chose to tread on this path, and how has been their journey - their challenges, dilemma, career progression, value to the organization, and so on. By itself, the topic is not interesting enough without real-life discussion of the journey.

    regards,

    TV

  • Naresh Jain
    By Naresh Jain  ~  3 years ago
    reply Reply

    Pankaj, thanks for the proposal. IME, the managers who really need this session, will not attend this session because they feel, they already know all of this. This is mostly Agile 1-0-1 for Managers. What can we do different to attract them to this session?


  • Anand Bagmar
    Anand Bagmar
    Director - Quality
    Vuclip Inc.
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Intermediate

    The key objectives of organizations is to provide / derive value from the products / services they offer. To achieve this, they need to be able to deliver their offerings in the quickest time possible, and of good quality!
    In order for these organizations to to understand the quality / health of their products at a quick glance, typically a team of people scramble to collate and collect the information manually needed to get a sense of quality about the products they support. All this is done manually.


    So in the fast moving environment, where CI (Continuous Integration) and CD (Continuous Delivery) are now a necessity and not a luxury, how can teams take decisions if the product is ready to be deployed to the next environment or not?

    Test Automation across all layers of the Test Pyramid is one of the first building blocks to ensure the team gets quick feedback into the health of the product-under-test.

    The next set of questions are:
        •    How can you collate this information in a meaningful fashion to determine - yes, my code is ready to be promoted from one environment to the next?
        •    How can you know if the product is ready to go 'live'?
        •    What is the health of you product portfolio at any point in time?
        •    Can you identify patterns and do quick analysis of the test results to help in root-cause-analysis for issues that have happened over a period of time in making better decisions to better the quality of your product(s)?

    The current set of tools are limited and fail to give the holistic picture of quality and health, across the life-cycle of the products.
    The solution - TTA - Test Trend Analyzer

    TTA is an open source product that becomes the source of information to give you real-time and visual insights into the health of the product portfolio using the Test Automation results, in form of Trends, Comparative Analysis, Failure Analysis and Functional Performance Benchmarking. This allows teams to take decisions on the product deployment to the next level using actual data points, instead of 'gut-feel' based decisions.

    There are 2 sets of audience who will benefit from TTA:
    1. Management - who want to know in real time what is the latest state of test execution trends across their product portfolios / projects. Also, they can use the data represented in the trend analysis views to make more informed decisions on which products / projects they need to focus more or less. Views like Test Pyramid View, Comparative Analysis help looking at results over a period of time, and using that as a data point to identify trends.

    2. Team Members (developers / testers) - who want to do quick test failure analysis to get to the root cause analysis as quickly as possible. Some of the views - like Compare Runs, Failure Analysis, Test Execution Trend help the team on a day-to-day basis.

    NOTE: TTA does not claim to give answers to the potential problems. It gives a visual representation of test execution results in different formats which allow team members / management to have more focussed conversations based on data points.

  • Liked Alexey Ilyichev
    keyboard_arrow_down

    Alexey Ilyichev - Skype goes agile: don't repeat our mistakes

    Alexey Ilyichev
    Alexey Ilyichev
    Agile Coach
    ScrumTrek
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In 2011, I worked for Qik, a startup that got aqcuired by Skype. At that time Skype was in the middle of an agile transition. Аfter aquisition, Qik team was told to adopt the Agile process used by Skype. I worked with the team as an agile coach. After adopting Skype's "agile" process, our ability to deliver was brought down to almost zero. In this talk, I'll tell you the story as it happened, analyze the key problems that we faced and describe how we finally solved them. Come to this talk, if you want to avoid similar mistakes. If you are already through with your transition, I would be interested to know if you see any patterns. 

  • Liked Sunil Mundra
    keyboard_arrow_down

    Sunil Mundra - Getting A Partner To Adopt Agile

    Sunil Mundra
    Sunil Mundra
    Principal Consultant
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    20 mins
    Case Study
    Intermediate

    Due to the business benefits which accrue from Agile, clients are demanding their IT Departments/Partners to adopt Agile. It is quite common to find a situation where the client has adopted Agile, but its Partner/Vendor has not.


    This talk is based on my consulting engagement with a client who had adopted Agile and their partner had not, and the client wanted the partner to Adopt Agile.


    The talk will cover the critical challenges encountered in getting the partner to adopt Agile, especially given the wide difference in cultures of both organizations and also the organizations being located in different continents. The talk will also cover the key learnings from this journey.

  • Liked Shirish Padalkar
    keyboard_arrow_down

    Shirish Padalkar - Application Security - The Agile Way

    Shirish Padalkar
    Shirish Padalkar
    Senior Consultant
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Traditionally application security has involved upfront design and a big bang penetration test after development. This leads to the phenomenon of “bolt-on” security that translates into increased cost and complexity.

    Drawing on our experience on real-world projects, we show how security can be baked-in on an agile project. Using case studies we demonstrate how security concerns are captured during project inceptions, how developers write secure code, security testing is automated and how configuration management can help achieve secure deployments. This talk introduces several new concepts like secure by design, secure design patterns and lightweight code reviews.

  • Liked Sudipta Lahiri
    keyboard_arrow_down

    Sudipta Lahiri - 10 (Understated) Lessons from TPS!

    45 mins
    Talk
    Intermediate

    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 Anand Bagmar
    keyboard_arrow_down

    Anand Bagmar - The Agile “Chalta-Hai (It’s OK)” Manifesto

    Anand Bagmar
    Anand Bagmar
    Director - Quality
    Vuclip Inc.
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    The Agile Manifesto was formulated by 17 people in 2001. We know the principles of the Agile Manifesto … but do we really understand it?

    Depending on the organisation culture, the team culture and various other factors, they reach varying levels of Agile adoption. Martin Fowler talks about the levels of adoption and the path to get better via his post on “Your Path through Agile Fluency”.

    Not surprisingly, not all Agile project implementations are successful.

    This session is going to take you through a journey to talk about some of the Myths of Agile and also behaviors that inhibit organisations and teams to reach great(er) heights in Agile Fluency to achieve Agile’s benefits.  As a result, the Agile Manifesto has remained on paper, but teams have come up with their own ‘workarounds’ - which are not truly solutions to solve a complex problem well.

    We accept it because of our “chalta-hai (it’s ok)" attitude. At the end, what are we then left with? The Agile “Chalta-Hai (It's OK)” Manifesto.

  • Anand Bagmar
    Anand Bagmar
    Director - Quality
    Vuclip Inc.
    schedule 3 years ago
    Sold Out!
    90 mins
    Case Study
    Intermediate

    The key objectives of Organizations is to provide / derive value from the products / services they offer. To achieve this, they need to be able to deliver their offerings in the quickest time possible, and of good quality!
    In such a fast moving environment, CI (Continuous Integration) and CD (Continuous Delivery) are now a necessity and not a luxury!

    There are various practices that Organizations and Enterprises need to implement to enable CD. Testing (automation) is one of the important practices that needs to be setup correctly for CD to be successful.

    Testing in Organizations on the CD journey is tricky and requires a lot of discipline, rigor and hard work. In Enterprises, the Testing complexity and challenges increase exponentially.

    In this session, I am sharing my vision of the Test Strategy required to make successful the journey of an Enterprise on the path of implementing CD.

  • Liked Yilmaz Guleryuz
    keyboard_arrow_down

    Yilmaz Guleryuz - Fibonacci Pairing: Learning through Collaboration

    Yilmaz Guleryuz
    Yilmaz Guleryuz
    incognito
    WareNinja
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    According to many researches, we learn the best when we experience it personally, and we comprehend when we teach to someone else.

    So if you want to achieve ample understanding of a topic, you’ll need to follow these basic steps:

    "Listen -> Observe -> Do -> Share"

     

    Pair-programming is a well-known practice, and it has been introduced by one of the thought leaders of Agile world, Kent Beck. I respect any technique that encourages collaboration and interaction among teams, and gets teams to communicate better.

    However, if you want to establish understanding of mastery or a skill-set, and increase the shared knowledge across your team members, then you need to re-think & apply new techniques.

    In this talk, I’ll share about What-Why-How of "Fibonacci Pairing" technique, which is yet another discovery from practice.

    The main goal of that technique is to establish understanding and improve collaboration, without overcrowding by artificial ways like lecturing.

    Fibonacci Pairing is simple yet very effective technique that can improve team work. This technique should be regarded as a complementary way to improve team culture effectively.

    We will elaborate with practical examples, real life experiences, and applicable ways onto different contexts.

  • Liked Vinod Sankaranarayanan
    keyboard_arrow_down

    Vinod Sankaranarayanan - Ownership Transfer

    90 mins
    Talk
    Intermediate

    Getting a different team to take over an application brings in challenges from multiple perspectives. There will be differences around processes, engineering as well as culture. Larger transfers would also involve changes to infrastructure. For long, the industry has done a disservice to this field by calling it Knowledge Transfer. Knowledge Transfer, is but a subset of the scope of activities involved in this exercise. We propose to rename this as Ownership Transfer.
    In specific - we put this process into practice with one of our customers. After more than 5 years of supporting the platform, ThoughtWorks worked with The customer teams to transfer knowledge and context back to the customer. A few highlights on the application.
    • More than 80% of all online ticket sales are done through this application
    • More than 400,000 visits a day
    • Close to 5 billion USD of ticket sales
    • More than 70 VMs supporting the production application
    • Upwards of 300 VMs supporting other development and testing environments
    A few highlights on the program,
    • More than 150 IT members involved in the program
    • A ramp-down was part of the process to get the final numbers to about 60
    • The transfer had to occur from Bangalore back to London
    • Infrastructure had to re-optimised from Bangalore over to London
    • Two organisations were involved viz. ThoughtWorks and the customer
    Since both Bangalore and London were following agile practices, the teams decided to utilise core agile concepts to effect the transfer. This became all the more important as business required critical features to be delivered on a continuous basis. 
    Before we started off on this exercise, we created a methodology to effect the transfer. This methodology is fairly context agnostic and should support a healthy, sustainable and mature way to transfer ownership. The transition itself was about a year long and involved multiple aspects around agile such as remote pairing, program MVP and above all, continuous delivery and non-disruption to business through the process.
    The session will introduce a framework that can be applied to most Ownership Transfer situations. In particular, this will be of interest to groups who are looking to transfer ownership from one team to another. These could be from a development team to a support team, or from one vendor to another as well. This will also provide insights on transferring ownership across distributed teams.  

  • Liked Vishal Prasad
    keyboard_arrow_down

    Vishal Prasad - Agile Project Forecasting with Focus Factor

    Vishal Prasad
    Vishal Prasad
    Project Manager
    Springer Nature
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    How many deliverables should we commit to our customers in, say, the next two weeks? An intriguing question asked by many Agile teams at the beginning of every iteration. The answer to this question depends largely on the team's thinking, philosophy, and skills -- which unfortunately cannot be measured. Then how do we forecast the deliverables?

    How about a mathematical formula that provides an unbiased control based on the historical achievements of the team, which can be used for prediction? That's exactly what focus factor does.

  • Liked Vineet
    keyboard_arrow_down

    Vineet - Cook your Product better : story map and no estimate is the new recipe

    Vineet
    Vineet
    Product Management
    Aconex
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    I'll share my experience on how we shipped products faster using story maps and how team's focus on smaller goals than estimates / numbers / complexities helped us achieve it. 

    The session would give an insight on:

    • Aligning team with product vision 
    • Shiping features fast / faster 
    • Better product backlog management 
    • Delivering without estimation 

     

    Some of our challenges / questions were:

    • Are we delivering value ? 
    • How do we know we have delivered enough for our customers ? 
    • What is our priority right now ? 
    • Do we have a bigger picture ? 
    • Aligning team with product vision
    • Is tracking numbers the right thing to do ? 
    • How fast should we ship ? What are the related challenges ? 

    We solved these questions / challenges first by using story maps and then removed estimation. Story map gave a clearer picture of what's planned and what's in the next customer release. Other ideas helped us easily identify when to ship and what to ship (I'll discuss more about these in the session). 

    Story map is a great way to collaboratively identify the features, prioritize them and create milestones. We used story maps as our card wall also. It was an interesting experience :) 

    No estimate helps the team focus more on goals and less on numbers. It helps the team to think more about the customers and how would they use the product and less about velocity, charts and commitment. It changes team's perspective and team starts shipping a usuable product for customers. 

     

  • Liked Unnat Gupta
    keyboard_arrow_down

    Unnat Gupta / Shree Damani - Calculating RoI on Agile Enablement

    45 mins
    Talk
    Advanced

    "We want to be Agile!!...

    Why?

    Because its cool, and its becoming a norm, it will help us to cope with changing requirements, help us deliver faster etc etc."

    Isn't this a common sentiment in organizations struggling with the ever changing user/customer taste?

     

    With Agile going main-stream with most organizations looking to have at least a few business critical projects run in an Agile way, the question of ROI comes up. Shifting from a traditional way of building software to an Agile way, requires change and as any good business leader would know; change is not free. Business leaders would like to understand and justify the return on Investment to make this shift. In our talk, we will be talking about how to look at the Agile process holistically and how this process affects budgeting and how early value realization can help offset the cost of change. We will also discuss stories of other in house IT shops and product houses who have made this shift and the journey they have undertaken

    From our experience of working with such organizations, we have found that for these process-focused Agile adopters, much of their measurements include:

     

    - how long is our stand-up?

    - how long is our build?

    - how many stories do we have?

    - how many points can we fit into a sprint? etc.

     

    From their perspective, they already have plenty of metrics. Often it's also the case that they're getting benefit, just because common sense does kick in behind the scenes, and because they're delivering more frequently as a result in the reduction of documentation, so they don't always run out of money either. That leads to bad habits, possibly, rewarding wrong practices. In this talk we want to discuss metrics we have used on the projects and have found useful. Metrics like: Cycle Time, Time to market (also called Lead Time), Collaboration, Quality (in terms of code complexity , code coverage, test pyramid) and bus factor. One thing to note is that any of these metrics alone would not provide holistic way of measuring benefit, and hence a combination of them is required.

     

  • Liked Unnat Gupta
    keyboard_arrow_down

    Unnat Gupta / Shree Damani - Know Your MVP!!

    45 mins
    Talk
    Intermediate

    MVP is defined as : "that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort."It doesn't say a thing about the product being valuable to the customers or market segment.

    MVP is minimum viable product *NOT*  minimally marketable feature set / first release!  MVPs are the experiments we learned from on the way to our first release of the software.

    To us the core of the difference between "Minimally Viable Product" and "Minimally Marketable Product" is in the purpose.  An MVP's purpose is to learn, an MMP's purpose is to serve.  Understand the problem vs address the problem.

     

  • Liked Unnat Gupta
    keyboard_arrow_down

    Unnat Gupta / Shree Damani - Prioritization Techniques: Lets move beyond MoSCoW!!

    90 mins
    Workshop
    Intermediate
    • Have you been in a situation where everything gets prioritized as MUST HAVE?
    • Have you been in a situation where you have find it difficult to get different stake holders to agree on relative priority of different features?
    • Most of the time is spent in discussiing low value features?
    • Whoever screams the loudest, gets their pet features prioritixed high?
    • Do you want to learn some more prioritization games/techniques that can be used to start prioritizing at Feature level and subsequently refine it to story level?
    • You feel the current technique(s) you use for prioritization are time consuming and ineffective?

    If answer to any of the above questions is yes, this is the workshop for you to attend

    Why Prioritization?

    Customers are never thrilled to find out they can’t get all the features they want in release 1.0 of a new software product. In reality, customer expectations are high, timelines are short, and resources are limited. Any project with resource limitations has to establish the relative priorities of the requested features, use cases, or functional requirements. Prioritization helps the project manager resolve conflicts, plan for staged deliveries, and make the necessary trade-off decisions. Thus, requirement prioritization is used in Software development for determining which requirements of the software product/application should be included in a certain release. Requirements are also prioritized to minimize risk during development so that the most important or high risk requirements are implemented first.

    Several methods for assessing a prioritization of software requirements exist. In this workshop we are going show some of techniques/games we have used for feature prioritization.

     

  • Liked Sarabjit Singh Bakshi
    keyboard_arrow_down

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

    45 mins
    Talk
    Intermediate

    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 Ajay Avinash Solanki
    keyboard_arrow_down

    Ajay Avinash Solanki - Agile Coaching - Giving and Receiving Feedback

    90 mins
    Workshop
    Advanced

    Agile is based on crossfunctional and self organizing teams. Agile is based on the Plan, Do, Review and Adapt Feedback Loop. Feedback is the basis of Agile. Feedback can be amongst team members, between Scrum master and the team, Product owner and Scrum Master, Stakeholders and Product Owner and various combination of the same. We generally give a deficit based feedback. We point out to the short commings, mistakes, fix blames etc. This is a very emotionally chaged discussion which leads to a lose lose situation and a bad relationship. Contrary to this Giving feedback should be based on strengths. It is a planned approach which has to be rehearsed before hand. The main objective of giving the feedback is to find out solution instead of fixing the blame. Let us learn the techniques by which this can be made possible.

  • Liked U S VINEESH
    keyboard_arrow_down

    U S VINEESH - Agility lessons from Nature

    45 mins
    Talk
    Intermediate

    When Darwin said “fittest,” Darwin did not mean strongest or fastest or even smartest: he meant most adaptable, best at handling change.

    Ants have existed close to more than 100 million years now and they can be considered as one of the most flourishing beings on our earth. They have colonized almost every landmass and they thrive in most ecosystems. Have you ever wondered what makes them so successful?

    This success of theirs in so many environments has been attributed to their social organisation and their ability to modify habitats, tap resources, and defend themselves. Ants are one among the most agile creatures that we have seen till date.

  • Liked Nilotpal Das
    keyboard_arrow_down

    Nilotpal Das - Head First Agile and Organizational Transformation

    45 mins
    Experience Report
    Intermediate

    This is a collection of real time case studies of failed projects. It is an autopsy of these failed projects studying why these projects failed and how application of agie principles could have saved them.

    It is also a study into the organizational culture, behavioral attributes and the people issues and how agile addresses them.

    And finally it is a study of why doing a few projects with agile is not sufficient. How complete organizational transformation into agile practices is necessary for long term success for projects, processes and people.

  • Liked Unmesh Joshi
    keyboard_arrow_down

    Unmesh Joshi - Organizational Patterns

    Unmesh Joshi
    Unmesh Joshi
    Application Developer
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Organizational Patterns study by Jim Coplien done throughout 90s forms the foundation of Agile. Its important to understand these patterns and go beyond  'popular practices' like stand ups, user stories and TDD. Individuals are important and there are certain characteristics of these individuals which makes a team Agile or not. This presentation covers some of the very important patterns which form the basis of Agile, without these, any Agile project is bound to fail.

    Jeff Sutherland, creator of scrum, now actively uses Organizational patterns to explain acrum and also started an effort at www.scrumplop.com to collect patterns which make Scrum work.

  • Liked Unnat Gupta
    keyboard_arrow_down

    Unnat Gupta - Agile Business Analysis Anti-Patterns

    45 mins
    Talk
    Intermediate

    In this talk we will pick up various (5-7) business analysis anti-patterns, specially for Agile projects, that either we ourself have practiced at some point of our BA carrier or have seen other BA's doing. We will talk about the symptoms which act as a sign of presence of these anti patterns, why are the problems associated with them and what are the ways to get rid of them.

    These anti-patterns may range from behavior with customers to behavior with the own team.

    Some of the anti-patterns we are planning to discuss:

    1) BA aka The Order takers
    2) Task (UI/backend) based stories
    3) Engrossed in too much detail to miss the view of bigger picture - story verus feature 
    4) As a “user”...., where the user is either "system" or "product owner"
    5) Leave the NFRs / CFRs to the Developers/Tech lead
    6) Detail the hell out of stories
    7) Focus on Happy Paths only
    8) Focus on building a software over solving the real problem
    9) Resist change in requirements