"Design Thinking" - Create Innovative Right Products

Design Thinking is an approach to solving Design/Wicked problems by understanding users’ needs and developing insights to solve those needs. It helps to address the right questions and to create the “Right products”.

Design Thinking is an iterative innovative approach. It is not meant as a replacement for the organization’s standard development approaches; rather Design Thinking works inside of agile projects, offering frameworks for collaboration and innovation.

Design Thinking ultimately helps you to address the right question and to create the right solution for it. It Means creating innovative "Right Product" by combining diverse people, creative space and an iterative approach.

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

Outline/structure of the Session

1. Theory of Design Thinking & All the phases on Design Thinking

2. A Real Case study will be shown. How I used Design Thinking to Develop an Innovative Solution

3. Innovative Games

4. Supporting Videos

 

Learning Outcome

This session will provide an understanding of what design thinking is, how it can be used to develop “Right products”.which customer will Love, how it can be used to avoid waste, how it relates to and enhances various agile practices and principles.

Target Audience

Product Development

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Jerry Rajamoney
    By Jerry Rajamoney  ~  3 years ago
    reply Reply

    Hi Manik,

    Good day. The topic you have chosen is a nice concept. But I would like to hear more from you on the following items.

    1. Is this User story mapping concept is the same which was used by Jeff Patton (http://www.agileproductdesign.com/presentations/user_story_mapping/)? If you are going to use the same, what more value add you have found by adapting the same in your cases?

    2. Since we are talking about "Beyond Agile" theme - How will you justify this proposal? The concern I have is since the User Story Mapping model is already used by many Scrum Teams how will you align this to go beyond Scrum? Could you please eloborate more on this.

    If you are not clear about my query please let me know.

    Thanks for your time.

    Regards,

    Jerry

    • Manik Choudhary
      By Manik Choudhary  ~  3 years ago
      reply Reply

      Hello Jerry,

      I have changed the proposal to Design Thinking. I will show a Real Case Study, How I have used Design Thinking to Developed Innovative Solution.

      Regards, Manik

    • Manik Choudhary
      By Manik Choudhary  ~  3 years ago
      reply Reply

      Hello Jerry,

      I am conducting a user story mapping (USM) workshop on a Particular case study given.  I have different ways of doing user story mapping. I will cover the the following during my  workshop 

      1. How to use user story mapping for a large project?
      2.  How to transfer User stories to a Jira Tool (Agile Project Management Tool)?
      3.  How to combine Design Thinking with User Story Mapping ?
      4.  Best Practices of User Story Mapping?
      5. Show User Story Mapping of Real Innovative Product

      Question 2 : Why in the "Beyond Agile" theme ?

      According to me, there are 3 stages to develop any innovative products

      1.      Product Vision - Design Thinking

      2.      Product Backlog - User Story Mapping

      3.      Product Creation - Agile / Lean / XP

      Agile covers only Execution of the product (Product Creation). Anything before Agile (Product Vision & Product Backlog )  is  “Beyond Agile” .

      Regards, Manik         

       

      • Tathagat Varma
        By Tathagat Varma  ~  3 years ago
        reply Reply

        Manik - from the proposal, the reviewer panel is not sure how well the proposal fits into Beyond Agile track. Surely, topics like Design Thinking are emergent from software development point of view and hold much promise. If you could refine the pitch more, the team could take another pass at the proposal. For example, do you want to present a case study? 

        -TV

        • Manik Choudhary
          By Manik Choudhary  ~  3 years ago
          reply Reply

          Hello TV,

          I have changed the proposal to Design Thinking. I will show a Real Case Study, How I have used Design Thinking to Developed Innovative Solution.

          Regards, Manik

           

  • Prasad
    By Prasad  ~  3 years ago
    reply Reply

    Manik

    We need to bring a different prespective or interpretation of Jeffs idea.  Jeff has presented multiple times in these same confrence. We need to bring something is going to benifit the community at a large..


  • 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 Sudipta Lahiri
    keyboard_arrow_down

    Capacity Planning for Dynamic Teams

    Sudipta Lahiri
    Sudipta Lahiri
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    Fixed price (and fixed scope) projects dominate the offshore industry. These projects have offshore/onsite teams. They often have large team size (over 100s of people in one team).

    Agile thinking uses team velocity/ throughput and uses that to project an end date (Kanban system) or how much scope can be accomplished in a given time duration (number of sprints in SCRUM). They assume a stable team. However, this is not applicable for projects. They experience resource and productivity ramp-up issues. Often, resources keep changing as new projects come in. Projects do not have past velocity or throughput data. Extrapolating historical data from other similar projects, though possible, is inaccurate for multiple reasons.

    This talk is based on our experience of working with such project teams. They want to adopt agile methods. We show how they can adopt the Kanban Method and yet do: A) Initial Capacity Planning B) Assess the impact of scope creep to the project end date.

    The session assumes a basic understanding of the Kanban method.

  • Liked Ellen Grove
    keyboard_arrow_down

    Build Your Dreams: User Requirements Gathering with LEGO Serious Play

    Ellen Grove
    Ellen Grove
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    Let your hands be the search engine for your brain! LEGO® Serious Play® is a powerful thinking, communicating and problem solving technique that can help you and your team do serious work through structured play activities using a popular and playful 3D modeling toy. Through a facilitated process of building models that, storytelling and reflection, every person at the table is engaged and actively participating in the discussion, whether the topic is individual aspirations, team relationships, developing a new product or solving a wicked organizational problem. Everyone builds and everyone tells their story – all participants have equal opportunity to put their own points of view on the table, unlocking new perspectives and exposing the answers that are already in the room.  LEGO Serious Play has been used successfully for team-building and problem solving in a variety of organizations, from NASA to RBC to academic settings and public utilities.  

    This presentation provides a hands-on introduction to LEGO Serious Play, so that you can experience firsthand how using LEGO to do real work unleashes creativity and enables meaningful conversations in a very short time. We will explore how to use this playful technique to collaboratively elicit information about user requirements and strategic design issues using the open source User Requirements with Lego methodology developed by a team at the University of Lugano, Switzerland.  This approach is particularly suited to Agile teams that want to get team members and stakeholders sharing their different perspectives on common goals in an open and light-weight manner.

  • Liked Nitin Ramrakhyani
    keyboard_arrow_down

    Lean Roots to Grow, Wings to fly!

    Nitin Ramrakhyani
    Nitin Ramrakhyani
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    A lot has been said about Kanban and how these can be implemented in Software development, but the learning remains superficial till we go deep down to its roots to understand the core underlying practices and principles and why/how these practices evolved over a period of time. Infact the roots of most of the Agile methods can be traced back to Lean/Toyota Production Systems, a set of practices and techniques used by Toyota to build great set of cars with limited amount of resources. Even though building software is much different than building a car, there are many lessons and practices that can be learnt and applied nonetheless.

    In this interactive and visual talk, we'll take a virtual trip to Japan and learn some of the best practices/concepts that originated at Toyota for building "world-class" cars and see how each of these can be applied to software development. Learning about the roots of Lean should help the attendees in sowing the seeds of Lean improvement in their organizations and would help in building better software and improving the efficiency of the software delivery lifecycle.

  • Liked Tathagat Varma
    keyboard_arrow_down

    Designing agile feedbacks for agile learning - an experience report

    Tathagat Varma
    Tathagat Varma
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Feedback is perhaps the most important aspect of the overall agile lifecycle. If the feedback is too wide and shallow, it won't give enough actionable feedback. If it is too narrow and deep, it might fail to register feedback outside its focus area. So, how does one go about designing feedbacks that enable agile learning. We call them agile feedbacks.

    In this brief session, we will share an experience from designing agile feedbacks for agile trainings and workshops. The objective was to get most critical feedback in shortest amount of time to enable quick action planning. We created feedback that took a maximum of 5 minutes and enabled the most important learning in both, focussed as well as open-ended manner that allowed us to focus on the most critical items. We employed elements of Design Thinking and Rapid Iterative Testing and Evaluation (RITE) to improve the process and quality of feedback themselves. We will also be touching up these concepts and how effective they were.

  • Liked Tathagat Varma
    keyboard_arrow_down

    Agility @ The Scale of Busine$$

    Tathagat Varma
    Tathagat Varma
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    [24]7 Customer, Inc started out in customer service space from Bangalore in 2000. Today, it is a sucessful mid-size company in voice-based customer support that also creates IP and products in big data and predictive analytics for some of the biggest names in business, and is a a high-growth company headquartered out of US. The growth in product R&D happened both organically as well as from acquisitions across multiple geos. While the initial / startup stage processes had been extremely successful in building the company's strong foundation, it was felt that the next stage of growth might not be a linear extrapolation of the past successes. Recognizing this futuristic need, it initially embraced agile software development methods in Q1 of 2013 to improve responsiveness, predictability and time to market in the product development organization. In Q2 of 2013, it embarked upon an ambitious company-wide program. The charter was to establish an end-to-end execution framework to make the entire operations efficient and effective - right from marketing and pre-sales to delivery, deployment, operations and ongoing optimization. 

    In this session,

    • We will analyze challanges involved in scaling-up agile adoption outside the software team across the entire organization.
    • Specifically, we will also discuss how we addressed some of those unique challanges that are associated with growth and scale, and
    • What does it take to achieve true end-to-end agility. 
  • 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.

  • Liked Tarang Baxi
    keyboard_arrow_down

    1000 Words - Illustrating Project Challenges with Visuals

    Tarang Baxi
    Tarang Baxi
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    A project can face varied challenges through its life, foreseen and otherwise - runaway scope, high defect volumes, depressed velocity, and many more. Addressing many of these first requires recognition of the problem and then action from one or more sets of project stakeholders. Telling the story with simple visuals can be a very powerful way to articulate a challenge (the what), the potential root causes (the why) and the options available to fix it (the now-what). Teams typically already track a lot of data related to throughput, quality, scope and cost. Creative use of this data combined with simple, hand-crafted visuals can be much more effective than hundreds of bullet points. In this hands-on workshop, you get to exercise your visual thinking and visual communication skills. We introduce some simple visual thinking techniques like Look-See-Imagine-Show, and then let you apply them in a project simulation, so that you can practice hand-rolling simple visuals that speak volumes (no fancy tools needed!).

  • Liked Sudipta Lahiri
    keyboard_arrow_down

    Forecasting with confidence

    Sudipta Lahiri
    Sudipta Lahiri
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Advanced

    Forecasting has always been a subject of interest to all project management teams. Team have used multiple methods (from detailed MS Project scheduling to Earned Value Management) to try and estimate when a project will finish. People spend a lot of effort to come with one precise hard date knowing fully well how their past predictions have failed, how their assumptions have been invalidated, etc.

    If one were to discuss further with a Project Manager, they will understand that there is a level of confidence that a Project Manager associates with this date.  Perhaps, he is very confident (90% - it is rarely 100%)! It could be even as low as 60-70% depending on the number of issues and risks in the project. In other words, an end date is always associated with a probability, which we in our management talk and presentations, ignore or fail to highlight. In reality, a Project Manager would like to say - I am 70% confident that can deliver this scope of work within the next 3 months but 90% confident that I can deliver this in the next 4 months.

    Kanban systems predict the future by extrapolating current throughput on the present backlog. Most Kanban tools use the CFD for the same. This gives you the gap between the rate at which you need to finish your work versus the rate at which you are finishing work at present. Like MS Project, it also gives one date when this backlog will finish, assuming current throughput.

    Fact is that future is not definitive! Project risks change, requirements change, team resources change... the list goes on! So, just like this inadequate for traditional tools, it is inadequate to limit ourselves to this analysis in the Kanban Method also.

    This session, using Kanban Tool, will demonstrate:

    1. The use of probabilistic theory to have a confidence % associated with a particular delivery date
    2. Once you know the gap between the current throughtput and the desired throughput, what resourcing changes can be done to bridge this gap. While it is understood that resourcing is not the only option to bridge the gap, it is perhaps the most commonly used method. 

    This approach has been vetted by David Anderson and has been presented in the LSSC 2013 conference by one of my colleagues.

  • Liked Manik Choudhary
    keyboard_arrow_down

    Making of Innovative Solutions: Lean Start-Up and Design Thinking Practices

    Manik Choudhary
    Manik Choudhary
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    Content :

    I will showcase Real Case Study on how Innovative Solutions can be developed using a mix of tools and techniques from Lean Start-Up ,    Design Thinking, User Story Mapping and Lean & Agile Development.

    - Lean Canvas is 1-page document that describes Business Model.

    - Design Thinking is an iterative innovation approach to develop the “Right Product”. Various phases of DT are 1. Understand 2. Observe 3. Define 4. Ideate 5. Prototype 6. Validate.

    - User Story Mapping helps teams get a common understanding of requirements from the user's point-of-view and facilitates creation of clearer backlog items.

    - Lean is right way to reduce waste and to efficiently and rapidly deliver high quality products.

    Summary :

    How the tools and techniques from Lean Start-Up, Design Thinking, User Story Mapping and Lean Development helped us in developing Right Innovative Solution in the right way.

     

  • Liked Anand Bagmar
    keyboard_arrow_down

    Build the "right" regression suite using Behavior Driven Testing (BDT)

    Anand Bagmar
    Anand Bagmar
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    BDT is a way to identify the correct scenarios to build a good and effective (manual & automation) regression suite that validates the Business Goals. We will learn about how this is different from BDD, and do some hands-on exercises in form of workshops to understand the concept better.

  • Liked Dinesh Sharma
    keyboard_arrow_down

    Thinking Environment - Do you have one?

    Dinesh Sharma
    Dinesh Sharma
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Advanced

    Everything we do depends for its quality on thinking we do first. Our thinking depends on the quality of our attention for each other.

    A Thinking environment is the set of ten conditions under which human being can 'think' for themselves - with rigour, imaginaton, courage and grace. A Thinking Environment is natural, but rare. It has been squeezed out of our lives and organisations by inferior ways of treating each other.

    Thinking environment is based on ten behaviours that generate the finest thinking, and have become known as The Ten Components of a Thinking Environment. These components are

    • Attention,
    • Equality,
    • Ease,
    • Appreciation,
    • Encouragement,
    • Feelings,
    • Information,
    • Diversity,
    • Incisive Questions and
    • Place.

    Each Component is powerful individually, but the presence of all ten working together gives this process its transformative impact.