Succeding with Agile in a waterfall oriented organization

How do you succeed with Agile in an organzation with deep entrenched waterfall processes?

How do you succeed with Agile when both the upstream and downstream dependencies are running waterfall?

How do you succeed with Agile with an organization shipping every 18-20months?

This case study with walk you through how a team went about adopting agile and transitions from 1 release in 2 years to 5 releases (3 major and 2 minor) in 1 year.

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

Outline/structure of the Session

TBD

Learning Outcome

case study

Target Audience

Anyone wondering about benefits of Agile and is on the edge of transition

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Doc Norton
    By Doc Norton  ~  3 years ago
    reply Reply

    Lokesh:

     

    I agree with Naresh's assessment that this fits better into "Scaling Agile". Would you consider moving it there? If not, can you help me understand how "Agile Lifecycle" is a more appropriate stage for this talk?

     

    - Doc

     

  • Ram Srinivasan
    By Ram Srinivasan  ~  3 years ago
    reply Reply

    Hi Lokesh,

    From your title, it feels to me that you are trying to adopt Agile in a waterfall organization when there is  marginal/no buy-in from executives.  Is this correct?

    If yes, what is the compelling reason that a waterfall oriented org wanting to adopt Agile in a half-hearted way? 

     

    • Lokesh Shah
      By Lokesh Shah  ~  3 years ago
      reply Reply

      >>From your title, it feels to me that you are trying to adopt Agile in a waterfall organization when there is  marginal/no buy-in from executives.  Is this correct?

      No. We have a large org with multiple products. Some product teams follow Agile while others follow waterfall. Teams following Agile have exec buy-in with full support. However they do have dependencies on other products teams who follow waterfall.

      As an example think of Windows & Office. Assume Windows team follows waterfall and Office team follows Agile. The company's goal is to ship a new version of Windows at the same time as Office. So the Office team following Agile has dependencies on Windows team following Waterfall.

      • Sachin goel
        By Sachin goel  ~  3 years ago
        reply Reply

        I would tend to agree with Lokesh. At times you cant control the methods which your upstream/downstreams projects take. Hence it is interesting to see how the balance is made.

  • Sachin goel
    By Sachin goel  ~  3 years ago
    reply Reply

    I see this could be a real session for the participants coming from captives (like me). Lokesh, if you can share the presentation material / provide more information on how you will do, this could be really beneficial.

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

    Lokesh, This topic fits into the 'Scaling Agile Adoption' theme instead of 'Agile Lifecycle'. Since you'll only be given 20 mins to present your experience, it is best to clearly highlight what specific, unique aspects about your experience you'll focus on.