An Exciting journey from Raw Idea to High fidelity concepts – Let's Discover, Design and Explore !!

In today’s hyper-competitive global economy, customer satisfaction is increasingly being driven by software. If we compare the past of software development from today's world It is definitely not the same. Customers is impatient because of available choice of ideas with better quality and reliability is important piece with the innovative faster time to market.

The session is all about how we can transverse from a Raw idea to high fidelity concept in different phases keeping the market condition and aggressive customer in mind but at the same time our vision for organization is intact and future looking.

Any simple or however complex it is , solutions and data tend to change over time. Intrinsic human needs do not. People, therefore, are the most constant variables in the design equation. By empathizing with your users and understanding what they need upfront, you can build products they’ll love to use — because your products will be both useful and usable.

We will uncover that - An Idea is not just what it looks like and feels like. It is all about how it works. At its core, any idea is about solving problems. Efficiently,Effectively, And elegantly.

This practical session offers a clear framework for you, your team, and your stakeholders to solve complex connectivity design problems — together.

 
2 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Workshop

In a hands on setup.

- We will set the stage to help people understand how Great products solve real problems for regular people.

- In the first phase of Session, our priority is getting to know your users — with empathy.

- Second is The Core Phases -

- These three phases are the heart of the session - Discover Phase, Define Phase , Explore Pahse

* Phase 1: Discover - Talk to users to discover your opportunity

Why - Our priority is getting to know users — with empathy. By empathizing with users and truly understanding their core needs, current frustrations, and related pain points, you can uncover the valuable opportunities that drive true innovation.

How - 1. Gather user data, 2. Synthesize insights, 3. Validate your findings, 4. Make the big opportunity

* Phase 2: Define - Define the problems to be solved for your users

Why - Once you have discovered your opportunity, you and your team will likely identify many problems that will need to be solved. But which ones matter most to your users? goal in this phase is to prioritize three — or fewer — clearly articulated problems that your solution will address on behalf of your users.

How - 1. Craft How Might We statements, 2. Ideate and align, 3. Role play and create a storyboard, 4. Define the problems to be solved

* Phase 3: Explore - Explore creative possibilities to solve user problems

Why - The key to the Explore phase is to ensure that the solutions developed explicitly solve the prioritized problems documented in the Define phase.

How - 1. Brainstorm creative solutions, 2. Sketch low-fidelity concepts, 3. Create interactive prototypes, 4. Validate with users

The Last phase will drive the conversation o hidden phases of Execute and Practise.

Learning Outcome

Together we will learn proven techniques for approaching user challenges with empathy. We'll learn how to identify and explore novel solutions. We'll learn how to use a variety of tools to get to your best ideas faster. And, along the way, you’ll learn to innovate more effectively than ever before.

We will learn how to prioritizes solving problems for end users to ensure their experience is the best — and most delightful — it can possibly be.

Target Audience

Business Leaders, Agile Coaches, Scrum Masters, Innovators, developers, design thinkers, Designers

Prerequisites for Attendees

- Keep in mind that end users are often different than customers.

- Come with an open learning mind

- Ask questions with focus on discovery and learning

- Participate fully in activities

- Let's Share and learn together

schedule Submitted 7 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Jeremy Kriegel
    By Jeremy Kriegel  ~  6 months ago
    reply Reply

    User empathy is key, but how long are these phases? Starts to sound like big upfront design.

    • Ashish Kumar
      By Ashish Kumar  ~  6 months ago
      reply Reply

      Totally Agree with you on putting the thought and agreeing to the fact that User empathy is key.

      Coming to the question part that how long is this phase.

      The two main activities in Discovery phase where Empathy plays the key role are data collection and insights synthesis.
      Try to meet with at least five to six users to begin to see a clear picture of what your user population needs. Once you gather information from these people, you can begin piecing your observations together in a way that starts to explain their behavior. Through user data, you can develop a clarifying narrative about your actual users and their everyday challenges.
      The Outcome of this phase is to identify the big opportunity which in turn will also ground and guide your decisions throughout , helping you stay on course from end-to-end.

      I would like to hear more from your prespective as what do you think more of the same..


  • Liked Ashish Kumar
    keyboard_arrow_down

    Ashish Kumar / Manjunatha M S Rao / Shijo Paul - Creating Purposeful Scrum Teams via Awesome Backlog

    90 Mins
    Workshop
    Intermediate
    Scrum is a practical framework to build products, provided you identified in advance what to build. However, even after a successful product discovery phase, you may struggle to make the right thing in the right way if your product backlog is not up to the job. Garbage in, garbage out — as the saying goes.
    Managing the product backlog is a full-time and continuous evolution. In this session, we will share Simple techniques that can help change what can be an overwhelming, time-consuming process to an interactive, iterative process that effectively engages team members, customers, and stakeholders. It is essential, therefore, to learn solid techniques to help you build, prioritize, and maintain your product backlog.
  • Liked Ashish Kumar
    keyboard_arrow_down

    Ashish Kumar - A Confused tester in Agile World- QA a liability or an asset !!

    Ashish Kumar
    Ashish Kumar
    Agile & Lean Coach
    Siemens
    schedule 7 months ago
    Sold Out!
    45 Mins
    Case Study
    Intermediate

    A QA Perspective on Agility and Scrum.Focus is mainly on QA role in Scrum,Challenges & Implementation of correct QA process in Scrum.

    This case study is to break the shackles of misconception or a myth that agile development places less emphasis on testing.
    Some QA professionals believe that the quality of software is compromised due to the shortened periods allotted for testing, which results in releasing software that has been only partially tested.
    Some think that with complete automation and continuous integration, the software testing job will become obsolete.
    Contrary to the synchronous activities of a traditional Waterfall project, Scrum expects development activities to be performed in the order they are needed – i.e. asynchronously.
    This break from tradition raises a common question by many of the clients, developers, and business stakeholders new to Agile – “How can testing professionals engage effectively during a sprint before anything has been built?”
    This article focuses on explaining how the QA role performs agile testing and the place of importance they hold on a Scrum team.
    Many think that maybe testers are not at all required and are a liability in the Agile process.

    This study was an attempt to find the truth and myth.

    This is an effort to look into agility and scrum from a perspective of QA. Which is although not a defined but very integral part of an agile team. I have tried to touch upon many bases as QA roles, Process, Challenges and benefits realized. How the different stages of QA contribute to Continuous Integration and Development and enables a Quality product delivery. I have a strong
    belief of learning with Sharing.


    This Study was executed based on survey as well contains some relevant questionnaire based on the topic. It was not limited to following questionnaire.

    1. Is the team cross functional and independent to deliver functional software (story) within a sprint?
    2. Do you have a setup to handle continuous integration and delivery to maintain the pace of delivery?
    3. Are you using Automation to optimize effort and to improve product quality?
    4. Is the deliverable at the end of the sprint / iteration ready to be shipped? (Is there a separate testing phase or deliverable from each sprint is ready to Ship?)
    5. Do you adapt techniques like Mocking Objects, Simulators, and Stubs etc. to take care of dependencies within Sprint instead of waiting for delivery from other team?

    6. In case of distributed team, are there a handshake / stand-up meeting daily with business partner team located remotely?
    7. Are the QA activities part of DOD and are there enough time for it?
    8. What is the ratio of QA to Programmers in Development team?


    For all the above survey questions response, recommendation and suggestions were requested.
    Based on the same model of above questionnaire set this study accumulated some real time data which helped to understand derive data on QA Practices, roles and challenges in Agile organization.
    The study further helps to understand the general QA practise being followed in agile teams and tester’s mind to understand how Scrum enables complex development practices such as CI and CD, and how it influences day-to-day approaches to software development.
    With this case study I would like to share with fellow learners how QA/ tester as individual and practice plays a very important role for successful delivery of Software development and what are the challenges involved.