While we have been dilly dallying moving to agile practices over last few years, early this year we decided that our small product team needs to be fully agile over next 6 months. The last 12 months of transformation has helped us all see whether Agile is as agile as it is made out!

We saw 40-50% increase in team velocity over waterfall for the same team!

Waterfall focuses on a release that spans across define, design, develop and verify to develop multiple features in an almost assembly line manner. Agile divides the features into user stories (as if sub-feature) and each of these user stories is defined, designed, developed and verified within one or more iterations by a dedicated scrum team. We discovered that this difference between waterfall and agile manifests to accelerate velocity through four sources.

These sources created a transformation, that we had not planned earlier.  As we have expanded agile implementation from one team to now 5 teams, focusing on these sources of agility to preserve them is turning out to be key to scaling. This we think is the key to scaling enterprise for agile.

 
3 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

A small comparison of Waterfall to Agile in few key instances

4 factors where agility comes.

Link to enterprise agility

Learning Outcome

Factors that impart Agility.

Scaling for Enterprise.

Target Audience

Those Looking to Transform their team to An Agile Enterprise!

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Vinod Sankaranarayanan
    By Vinod Sankaranarayanan  ~  1 year ago
    reply Reply

    Hello Satish,

    We would be specifically interested to see any type of metrics that compare waterfall and agile - it would be very useful. Metrics could be points delivered, defect density, release score cards, even function points if you have used those, number of red/green builds - or any other measure that you have looked at.  It could also be team sizes, team motivation (if you have been capturing team temparatures over time) or any such as well.

     

    If you can share any observations in scaling from one team to 5 teams - and again metrics around those, it would really help our cause.

     

    thanks,

    Vinod

    • Satish Kamat
      By Satish Kamat  ~  1 year ago
      reply Reply

      Thanks, Vinod. We have seen evolution of measures as we move along this journey. We started with improvement in velocity (points and hrs), then moved into defect density, and now we are looking into an entirely new measure. I think this surprised us a bit and came from team and partly from a lead customer comment.  Pretty interesting learning.

      -satish

  • Srinath Chandrasekharan
    By Srinath Chandrasekharan  ~  1 year ago
    reply Reply

    Hi Satish,

    Your proposal looks interesting, especially the part where you mention a significant growth over the waterfall team. 

    However, for evaluating a proposal we need content / slides as well as a video of any presentation you have made earlier. Would request you to go through the link http://2016.agileindia.org/#speaker.

    Please do update your proposal with the same to help us a more objective evaluation.

    Regards,

     

    Srinath

    • Satish Kamat
      By Satish Kamat  ~  1 year ago
      reply Reply

      Sure, Srinath. I will add few more details over next daty or so.

      In my profile, i have added some refernces of earlier talks. Will dig those preso and provide here. 


  • Liked Satish Kamat
    keyboard_arrow_down

    Why Play SAFe, When You Can Have TEA (Transform Enterprise To Agile)!

    Satish Kamat
    Satish Kamat
    schedule 1 year ago
    Sold Out!
    45 mins
    Keynote
    Advanced

    The success of Agile development with relatively small teams, has got software enterprises looking at using Agile for their enterprise size teams. This scale up of the agile development was first comprehensively addressed as Scaling Agile For enterprise or SAFe. Recently, scrum camp tried to address this as Scrum at Scale. Both of these approaches provide a decent framework for integrating product backlog with release train.

    However the key aspect of scaling agile is transformation of the teams. This transformation has multiple aspects - team size, team re-composition, retraining and most importantly team attitude.

    So while the enterprise team is retrained into scalable framework, the journey of the team to be transformed to Agile as an attitude must be addressed. In Transform Team to Agile (TEA), while we provide an enterprise scalable agile framework, we bring out team transformation framework! This talk captures experiences from transformation from waterfall thinking to Agility.

    It also brings out that it is not agile that needs to be scaled for enterprise, but it is really the enterprise that needs to be transformed to be agile!