Microsoft Visual Studio's Journey to Continuous Delivery

Microsoft Visual Studio is now releasing at a much faster pace and the Team Foundation Service has  a deployment every sprint. We adopted agile practices across the board and made significant improvements to engineering processes and systems down the way. What are the impediments to agile and how you overcome them. How do you reimagine the role of developers and testers in this new era. What kind of tools do you need to make this transition a success for your team ?

Come and learn what it takes to adopt modern processes to ship complex products like Visual Studio with engineering teams spread across the globe to ship at cloud cadence. 

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

Outline/structure of the Session

The structure of the session is pivoted around the journey of Visual Studio from 2005 onwards when we used to have longer release cycles to now when we ship every 3 months for our on-prem product and every 3 weeks for our online service.

  • Visual Studio Team - Common Challenges with large distributed team development
  • 3 Waves of learning - Techincal Debt (2005-2008), Amplified flow of Value (2008-2011), Improved Cycle Time (2012 and beyond)
  • Modern Practices and Modern ALM for Continuous Delivery (Talks about Agile Lifecycle to enable continuous Delivery)
  • Recap 

Learning Outcome

The key takeaways of the sessions are to believe that one can be succesful adopting agile practices for complex products like Visual Studio. Also some tips around how one can overcome common challenges when one goes down this journey.

Target Audience

The session is meant for decision makers to understand the challenges and solutions in adopting agile practices for complex products. At the same time it also caters to agile team members to understand how to put the processes into practice to deliver cus

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Joel Tosi
    By Joel Tosi  ~  3 years ago
    reply Reply

    Hi Vibhor,

       I'm not convinced your title makes complete sense, when I think of cloud cadence - I think deploy anytime and at least a few times a week.  

     

    Could you elaborate more on the 3 phases?  The first phase - I assume it was legacy code, and so on.  Could you provide me a one sentence learning outcome from each phase?

     

    Best,

    Tosi

    • Vibhor Agarwal
      By Vibhor Agarwal  ~  3 years ago
      reply Reply

      Hi Tosi

      We are shipping our online service every 3 weeks and have plans to improve further. I can send more info to you next week - maybe a skeletal deck.

      BTW - are the sessions finalized or when will they be finalized by so I can plan for it better.

      Thanks

      • Joel Tosi
        By Joel Tosi  ~  3 years ago
        reply Reply

        Hi Vibhor,

            Thanks much. The sessions are not finalized yet, though we are working on that now, trying to get more information / clarity where needed to help us make our decision.  

         

        With that being said, please don't feel the need for a detailed deck.  I'm looking for the flow mostly and what attendees can gain from each phase..

         

        Best,

        Tosi

        • Vibhor Agarwal
          By Vibhor Agarwal  ~  3 years ago
          reply Reply

          The way you should think about it is the 3 phases of the overall transformation which started with :-

          1. Reduce technical debt as a focus - resulted in 15x bug debt reduction, high predicatability, customer sat. I will explain the 'Hows' as well but the key learning is to have a common definition of 'done' criteria and adhering to executing on that criteria.

          2. Once the debt is under control, increase the flow of customer value - SFE (scenario focussed engineering), standard agile practices to increase dev/test/PO collaboration, usage of right tools , continuous integration, etc. The key learning here is team collaboration towards a common goal driven by SFE.

          3. Reduce cycle time - Compress the cycle time to get bits out to customers early so you can get continuous feedback and iterate. Create strong customer channels and invest in automation infrastructure. Make it easy for customers to provide feedback.

          Hope this helps.

          Thanks

          Vibhor

           

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

            Hi Vibhor,

             

            When you say you reduced technical debt 15x, how did you quantify it? That is, what did you measure?

            Ram

  • Nitin Ramrakhyani
    By Nitin Ramrakhyani  ~  3 years ago
    reply Reply

    Vibhor,

    Can you please update the abstract based on the feedback/ suggestions given by Joel and Steve? That'll get reviewers the latest perspective on the proposal and decide on the shortlist.

    Thanks,

    Nitin

    • Vibhor Agarwal
      By Vibhor Agarwal  ~  3 years ago
      reply Reply

      Hi Doc

      I dont think 20 minutes would do justice to this kind of content. I think 45 mins would be required at least. Thanks for asking.

      Regards

      Vibhor

       

    • Vibhor Agarwal
      By Vibhor Agarwal  ~  3 years ago
      reply Reply

      Thanks Nitin. I updated the learning outcome based on the feedback received. Let me know if you need any additional info.

  • Doc Norton
    By Doc Norton  ~  3 years ago
    reply Reply

    Vibhor:

    I was wondering if you would feel comfortable giving this in a 20 minute session? This is not a requirement. What do you think?

    - Doc

     

    • Vibhor Agarwal
      By Vibhor Agarwal  ~  3 years ago
      reply Reply

      Hi Doc

      I dont think 20 minutes would do justice to this kind of content. I think 45 mins would be required at least. Thanks for asking.

      Regards

      Vibhor

       

  • Joel Tosi
    By Joel Tosi  ~  3 years ago
    reply Reply

    Hi Vibhor,

      This is an interesting submission. Have you presented this before?  I like the perspective of real-world transformation along with motivating factors and challenges along the way.

    I feel that the learning outcomes possibly don't align with the session.  I would offer for your consideration that people already attending the conference understand why they should adopt agile practices.  Your session could help them see a road of transformation that they might be able to relate to along with some takeaways - stumbling blocks you encountered.  What helps with distributed teams?  etc

     

    What do you think?

    Best,

    Joel

    • Vibhor Agarwal
      By Vibhor Agarwal  ~  3 years ago
      reply Reply

      Thanks Joel for your comments . I have done these kind of sessions to our customers as part of EBCs (Executive Briefing calls) and given I own some of the Microsoft Visual Studio ALM tools , we have shown them how some of the tooling can enable such transformations. What you summarized would be a good way to call out the learning outcome of the session. Let me know if you have any additional comments.

       

  • steve ropa
    By steve ropa  ~  3 years ago
    reply Reply

    Hi Vibhor,

     

    I'd like to echo Joel's comments about the learning outcomes.  An experience report of how you reached this level of  success is of great interest to me for a couple of reasons.  One, seeing that a very complex product even *can* be successful with Agile.  A lot of people seem to get discouraged by the pitfalls and challennges you have overcome.  The second is that you might be able to call out a few of the roadblocks and puzzles that might be on the audience's horizon.  Both of those outcomes would be very compelling to me.

    Regards,

    Steve

    • Vibhor Agarwal
      By Vibhor Agarwal  ~  3 years ago
      reply Reply

      THanks Steve for your suggestions. That certainly is the intent of the talk.


  • Liked Naresh Jain
    keyboard_arrow_down

    Scaling XP Practices inside your organization using Train-the-Trainer Model

    Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Advanced

    How do you effectively scale skill-based, quality training across your organization?

    Over the years, I've experimented with different ideas/models to scaling skill-based training across an organization. In the last 4 years, I've pretty much settled down on the following model. Its very useful when mentoring teams on skills like Test-Drive-Development (TDD), Behavior-Driven Development (BDD), Product Discovery, Writing User Stories, Evolutionary Design, Design Patterns, Problem Solving, etc. I've successfully implemented this model at some very prominent fortune 500 enterprises.

    The goal of this workshop is to explore what other successful models organized have used to scale skill-based training in their organization.

  • Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Intermediate

    "Release Early, Release Often" is a proven mantra and many companies have taken this one step further by releasing products to real users with every commit a.k.a Continuous Deployment (CD).

    Over the years, I've built many web/infrastructure products, where we've effectively practiced CD. However at Edventure Labs, when we started building iPad games, we realized there was no easy was to practice CD, esp. given the fact that Apple review takes a few days.

    Our main question was: As mobile app developers, how should we architect/design our apps for CD?

    We were a young startup, learning new behavior about our users (kids aged 5-8) everyday. We could not afford any delay in releasing latest, greatest features to our users. To solve this problem, I believe we've built an innovative solution to enable any mobile app developer to achieve CD.

    If you are building real products, which have platform/3rd-party dependencies and you want to practice CD, this session is for you.

  • Liked Naresh Jain
    keyboard_arrow_down

    SAMPLE PROPOSAL - Product Discovery Workshop

    Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Beginner

    Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?

    Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.

    During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.

    This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.

    This is a sample proposal to demonstrate how your proposal can look on this submission system.