The purpose of the talk is to examine the skills gap for Development Teams to have a strategic vision of the products that are being created. Whilst Development Teams members are able to gain knowledge through education and training programs, difficulties can arise when transferring learning into practical work settings.

I will share my experiences of facilitating hands-on Workshops using the Design Sprint with Scrum Framework and applying the Agile principles with multiple teams from different companies, the challenges that they faced and the benefits of using this model.


Outline/Structure of the Presentation

Introduction - 10 Minutes

What is Design Sprint – 5 Minutes

Design Sprint with Scrum – 15 Minutes

Benefits & Conclusions – 5 Minutes

Q&A – 10 Minutes

Learning Outcome

The audience will gain understanding about the benefits identified by running the Design Sprint with Scrum that include: a greater understanding of customers’ needs, reduced times in making decisions, faster prototype development times, faster developing processes, faster production times, improved customer relationships, improved reputation and improved soft skills such a communication and team work.

Target Audience

General audience, everyone is welcome.

Prerequisites for Attendees


schedule Submitted 11 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Madhavi Ledalla
    By Madhavi Ledalla  ~  11 months ago
    reply Reply

    Hi Liviu, Thank you for your submission, can you please add supporting artifacts to your presentation. It can be a slide deck or a  mind map or a vedio. This will help the review team understand the flow of your talk and make an informed decision on your proposal.  Please refer to the  guidelines in the Call for Participation section. Thank you!

    • Peter Stevens
      By Peter Stevens  ~  11 months ago
      reply Reply

      Ping! Liviu?

      • Peter Stevens
        By Peter Stevens  ~  10 months ago
        reply Reply

        I like that you take a critical approach to working with scrum and the hands on approach to design

        I think you could improve this talk by looking at the definition of the increment. How does a design sprint conform or not conform to Scrum expectations? What prevents you from doing this work in the context of Scrum sprint? Why does design stop at the first sprint.?



        • Liviu Mesesan
          By Liviu Mesesan  ~  10 months ago
          reply Reply

          Hi Peter,

          Thank you very much for your feedback!

          I will start, with answering to the last question.

          The Design Sprint is not necessary to be the first Sprint. The design Sprint is used mainly in two cases:

          • 1st is to validate an idea about a product or a service
          • 2nd is to validate some assumptions that the development team is having and they do not know the acceptance from the real user/customer of some very important functionalities of the product and they need to test that before going forward

          In both cases the Design Sprint is the most efficient way of testing the product, by building and testing a prototype with real users/customers, in just 1 week.

          At the end of a Design Sprint the results about the idea or assumptions made by the team will be in one of three possible situations:

          • the product is successful as it is
          • the product is accepted, but for being successful needs some changes
          • the product is a failure and needs a total rethink

          Design Sprint can be used as many times as there are very important decisions to make about the product development direction.


          Regarding your second question, it depends.

          Because the 2 weeks length of the Scrum Sprint is almost a standard, and the Design Sprint has just 1 week, usually Design Sprint runs between two Scrum Sprints. If the team is having a 1-week Scrum Sprint, then the Design Sprint runs as another Sprint.

          As similarities, the roles are the same as in Scrum, nothing changes.

          We have different names for “artifacts, and events” but all are having correspondent in Scrum

          For Example: The planning sessions happens in the Decide phase, the Daily Scrum is used as it is, the Review is the Interview phase and the retrospective is used as it is. As artifacts the Product Backlog contains the results from the Sketching phase, the Sprint Backlog is the Story Board, and the Increment is the Prototype.


          You touch a very important point with the first question, regarding Scrum expectations by the definition of the increment.

          In both cases, Scrum Sprint and Design Sprint, we have a deliverable at the end of the Sprint and this deliverable is getting value to the Customer and to the Team. The difference is that in Scrum we have the Increment, that meets the DoD and is releasable to production and it brings value being used by the customer, and in Design Sprint we have the Prototype, that is disposable, and has the main purpose to learning, by getting feedback from the users/customers.

          The main difference between the Design Sprint and Scrum, is that the Design Sprint is a Methodology and Scrum is a Framework.


          About your third question I discuss when I present What is the Design Sprint.

           Based on your recommendations I will update the presentation with few slides about the similarities and the differences between Design Sprint and Scrum. In this way it will provide more clarity and consistency for the audience.

    • Liviu Mesesan
      By Liviu Mesesan  ~  11 months ago
      reply Reply

      Hi Madhavi,

      Thank you for your patience, it seems that my notifications didn't work properly.

      I updated my proposal with the  the presentation. Please let me know if I need to do anything else.

      Kind Regards!

      Liviu Mesesan