• Liked Vibhor Agarwal
    keyboard_arrow_down

    Microsoft Visual Studio's Journey to Continuous Delivery

    Vibhor Agarwal
    Vibhor Agarwal
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    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. 

  • Liked Roy Nuriel
    keyboard_arrow_down

    The Quality Assurance Journey - From Waterfall to Continuous Delivery

    Roy Nuriel
    Roy Nuriel
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In the past several years we have seen more and more organization taking the decision and moving their development divisions to adopt Agile methodology. In most cases the change starts with a POC of a new and – in most cases – small project that validates the ability of the organization to make the shift to Agile. In many cases the development team takes the lead: changing the process, moving to unified teams, selecting which Agile practice to adopt, etc.

    In this session I will share how we made the shift, while focusing on the change in our quality process.

    As an R&D group that develops an Agile solution (HP Agile Manager), we wanted to get it right. We changed the way in which we develop software from waterfall to Agile, and built a process to support the teams in a complex and large enterprise. While previously we were accustomed to delivering releases in 1-2 year cycles, we now operate within a SaaS model where we update our production environment on a weekly basis. 

    We have experimented with the same process that our customers are going through and, as a result, we adapted the way our QA engineers work. In accordance with their new role, we gave them a new title – Dev Testers.

    Here are some of the dilemmas we faced:

    -          What are the differences between "Dev Tester" and "QA Engineer"?

    -          How can we measure quality in 2-week sprints?

    -          What needs to change when testing a SaaS solution that is delivered on a weekly basis?

    -          When and how should load testing be performed?

    -          Automated v. manual testing

    -          What testing should be part of the CI process?

    -          How do offshore Dev Testers take part in our Agile practices (e.g. daily meetings)?

    We dealt with all of these questions, and I would like to share the lessons we learned, our conclusions, and some of the challenges that we still face.

  • Liked Vibhor Agarwal
    keyboard_arrow_down

    Microsoft Visual Studio's Journey to Continuous Delivery

    Vibhor Agarwal
    Vibhor Agarwal
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    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. 

  • Liked Roy Nuriel
    keyboard_arrow_down

    The Quality Assurance Journey - From Waterfall to Continuous Delivery

    Roy Nuriel
    Roy Nuriel
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In the past several years we have seen more and more organization taking the decision and moving their development divisions to adopt Agile methodology. In most cases the change starts with a POC of a new and – in most cases – small project that validates the ability of the organization to make the shift to Agile. In many cases the development team takes the lead: changing the process, moving to unified teams, selecting which Agile practice to adopt, etc.

    In this session I will share how we made the shift, while focusing on the change in our quality process.

    As an R&D group that develops an Agile solution (HP Agile Manager), we wanted to get it right. We changed the way in which we develop software from waterfall to Agile, and built a process to support the teams in a complex and large enterprise. While previously we were accustomed to delivering releases in 1-2 year cycles, we now operate within a SaaS model where we update our production environment on a weekly basis. 

    We have experimented with the same process that our customers are going through and, as a result, we adapted the way our QA engineers work. In accordance with their new role, we gave them a new title – Dev Testers.

    Here are some of the dilemmas we faced:

    -          What are the differences between "Dev Tester" and "QA Engineer"?

    -          How can we measure quality in 2-week sprints?

    -          What needs to change when testing a SaaS solution that is delivered on a weekly basis?

    -          When and how should load testing be performed?

    -          Automated v. manual testing

    -          What testing should be part of the CI process?

    -          How do offshore Dev Testers take part in our Agile practices (e.g. daily meetings)?

    We dealt with all of these questions, and I would like to share the lessons we learned, our conclusions, and some of the challenges that we still face.

Sorry, no proposals found under this section.