Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile india2012 turning_into_an_agile_engg_manager_v0.2


Published on

Slides from my session at Agile India 2012. If you are a manager, an aspiring manager or someone who wants to know how to get more value from the role of a manager in Agile teams.

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

Agile india2012 turning_into_an_agile_engg_manager_v0.2

  1. 1. TURNING INTO AN AGILE ENGINEERING MANAGER February 2012 Debashis Banerjee (
  2. 2. 1902 or 2012? Are we all variations of Rodin’s ThinkerVersionOne 2011 Stage of Agile Survey says:“64% of Agile Champions are in the managementlayer”In larger companies (>500 people)•27% said lack of management support•26% said “general resistance to change”were major barriers to agile adoption.This drops to 10% in smaller companies
  3. 3. Who is an Agile Engineering Manager
  4. 4. Today’s Agenda Arm yourself with The 4 Is and 3 Ps Scenario Walkthrough; Leveraging the 4Is and 3 Ps in agile (Scrum)  Separation Anxiety  Extinction Anxiety  UN-Certainity  xe-NO-phobia  A “?” on every face  Changing Lanes Agile Behaviors managers can support
  5. 5. Arming yourself with the 4 Is 4Is
  6. 6. Learn the 3 Ps and apply the 4Is  People – Who are the people doing it?  Project – When and How are they doing it?  Product – How is it built? EM 4Is: ng/1651
  7. 7. “Agile EM” Scenario Walkthroughs Agile Methodology assumed Scrum with 2 week sprints in a cross functional teamScrum Team – Cross Functional (Dev,QA, Product OwnersService Engg) Engineering ManagerExternal Scrum teams Other company stakeholders (Directors/CEO)Scrum Master
  8. 8. Scenario 1: Separation AnxietyOne of the key members of the team decides to leave or has to be let go? The team member is handling critical sprint deliverables
  9. 9. Scenario 2 : Extinction Anxiety The scrum team is informed that the product has to be scrapped in the middle of the sprint?
  10. 10. Scenario 3 : UN…Certainity The scrum team is informed the company will be acquired but is in the middle of a major product?
  11. 11. Scenario 4 : xe-NO-phobia? (Fear of Strangers…) You are a single location team but now with new members across multiple geo locations and also an outsourced vendor?
  12. 12. Scenario 5 : A “?” On every face The product has no concrete roadmap and product owner appears disengaged and scrum team is not happy
  13. 13. Scenario 6 : Changing Lanes The technology stack needs to be changed
  14. 14. Agile Behaviors managers can support!  People:  People own backlogs as “Team” not function  Team pick their own tasks  Cross functional team members are open and give ongoing peer feedback and use retrospectives effectively  Product  The product is built right in iterations  PO can release product versions at sprints if needed  Project:  Product owner sets backlog priority and changes  Timelines are committed by team  There is a single backlog