<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Agile Team - Medium]]></title>
        <description><![CDATA[Tech-enthusiast team finding solutions using the latest technologies - Medium]]></description>
        <link>https://medium.com/agile-team?source=rss----e5543c32a851---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Agile Team - Medium</title>
            <link>https://medium.com/agile-team?source=rss----e5543c32a851---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:46:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/agile-team" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[prototyping in Design Sprint]]></title>
            <link>https://medium.com/agile-team/prototyping-in-design-sprint-be42cfc143c3?source=rss----e5543c32a851---4</link>
            <guid isPermaLink="false">https://medium.com/p/be42cfc143c3</guid>
            <category><![CDATA[testin]]></category>
            <category><![CDATA[protoyping]]></category>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[tools]]></category>
            <dc:creator><![CDATA[Nini Kapanadze]]></dc:creator>
            <pubDate>Thu, 08 Oct 2020 13:43:51 GMT</pubDate>
            <atom:updated>2020-10-08T13:37:02.281Z</atom:updated>
            <content:encoded><![CDATA[<h3>Prototyping In Design Sprint</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*K4BKYLzv7jpUrMptj6EAtQ.jpeg" /></figure><p><strong>What would be the best way to learn about customers needs? </strong>well, you could do research, analyze different kind of data etc. But, best way to learn about someone is directly from them right? easy as that. Problem is, if you just ask people what they like/dislike, you ask them to hypothesize about situations and the answer may or may not be realistic. Also when asking people their opinion about the product or service etc. they may give you the answers they think you want to hear, or ones that makes them look more smart.</p><p>When psychologists try to get realistic reactions, they try to have as realistic environments as possible, to observe how people would react on the variable they are researching. This way the feedback is more sincere and real. This is the approach we are trying to use when working with Design sprint.</p><p>Design Sprint is 5 day process, where each day has it’s unique purpose. The goal of design Sprint is to have realistic feedbacks about features and targeted problems in just 5 days, directly from potential users.</p><p><em>during 5 days you would:</em></p><p>day 1 — learn about problem and choose target;</p><p>day 2 — ideate and create solution sketches</p><p>day 3 — choose from ideas and decide what the prototype would look like</p><p>day 4 — build prototype</p><p>day 5 — test prototype and gather feedback</p><p>Each day is really important to get the results, but having <strong>prototype</strong> which is result of well chosen target, good understanding of problem, proper research and ideation and also is enabler for proper testing session on 5th day is a must have.</p><p>So, after you did all the ideation, sketching, discussed everyone&#39;s solutions and chose the final idea for the prototype, teams goal would be to make as realistic prototype as possible. But <strong>what is realistic enough</strong> and how you do this?</p><p>Well, prototype building day is all bout illusion. By this time you have the idea for solution and instead of building real thing, which could take months and lots of resources, you try to fake it and build the façade. As <a href="https://www.thesprintbook.com/">Design Sprint Book</a> Suggests, building façade can give you 90 percent accuracy and show if idea is worth building.</p><p>Doing it in one day may be challenging, but this has its pros:</p><ol><li>If you take longer for building the prototype, it may be more perfect but it will slow down the learning process. If the idea is not a winner, the sooner we find out the better.</li><li>Longer you spend working on somethin, more attached you become to the solution, so, less likely you’ll be to take negative feedbacks.</li></ol><p>To build the façade team needs to have <strong>prototype mindset</strong>, which means to temporarily change your approaches: instead of building something perfect, build just enough, temporary solution, which gives ability to test exactly what you are trying to test.</p><p><strong>So the features of good prototypes include:</strong></p><ol><li>They are just enough to learn, not more. good prototype needs to be focused</li><li>Prototypes must appear real</li></ol><p>So before choosing the tool the main concept to understand is what is <strong>real enough?</strong></p><p>Best answer would be: when testing you need to create illusion so you get the reactions and not suggestions from users. suggestions doesn’t bring any value in this situation, while reactions give you insights about the idea. So as long as prototype gives you ability to keep illusion going, it is realistic enough.</p><p>Prototyping day includes following:</p><ol><li>choose a right tool</li><li>Divide and conquer — team is divided to work on different aspects simultaneously</li><li>Stich it together — prototype is stitched together and is ready to be tested</li><li>Do the test run .</li></ol><p><strong>Choosing a right tool </strong>is really important. Decision depends on what you need to build and what are you testing. Remember, you need to stay focused on problem. use the tools which will give you ability to build just enough, not the perfect full product.</p><p>In our case we tried different prototyping tools. From standard prototyping tools we used <a href="https://www.adobe.com/products/xd.html">Adobe Xd</a> to build prototype for online bookstore <a href="http://lit.ge/">lit.ge</a>. This was the final<a href="https://xd.adobe.com/view/6c07f1ab-537f-4fac-a621-58ec5d2fc60b-3954/?fbclid=IwAR3yONJr4RtilAMjoCfoPNNgd51119B2NZ_-ZoOtwq_odM9QgBuEL7cijy4&amp;fullscreen&amp;hints=off"> result</a>.</p><p>Adobe Xd gives you ability to give users realistic feeling as if they are browsing real website. So we were able to observe their reactions. Using this tool you are able to Build brilliant visuals and make them act like real website, but if the logic of actions from user’s side is too complicated, building process becomes longer.</p><p>Besides this tool, we tried to build real application in one day using <a href="https://www.appsheet.com/">Appsheet</a>. This tool uses sheets you create, to display data in real application, which can be downloaded and installed on smartphones. Advantage is that if you are trying to have real app in just one day and test it, this tool gives you ability for that. But you are restricted in complexity and also visually it’s hard to implement the exact layouts you have in mind.</p><p>in conclusion, as mentioned before, solution for tools depends on situations and what you want to achieve.</p><p>Another important part of prototyping day is a <strong>trial run</strong>. The best time to do it is in the middle of the day so you still have time to fix mistakes. During trial run you also get one last time to check if you are on the right track, if everything goes according to plan and to prepare for interview.</p><p>At the end of the day team is ready to do realistic testing, observe the patterns and plan next steps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be42cfc143c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agile-team/prototyping-in-design-sprint-be42cfc143c3">prototyping in Design Sprint</a> was originally published in <a href="https://medium.com/agile-team">Agile Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Testing in Design Sprint]]></title>
            <link>https://medium.com/agile-team/user-testing-in-design-sprint-5205c24b8441?source=rss----e5543c32a851---4</link>
            <guid isPermaLink="false">https://medium.com/p/5205c24b8441</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[google-design-sprint]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[leanagile]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Nino Kodzakhidze]]></dc:creator>
            <pubDate>Thu, 24 Sep 2020 14:32:13 GMT</pubDate>
            <atom:updated>2020-09-24T14:32:13.421Z</atom:updated>
            <content:encoded><![CDATA[<p>,,Test hundred times and launch only once” — as a Georgian proverb sounds in modern days</p><p>let’s try to answer key questions:</p><ol><li><strong>Why is testing critical?</strong></li></ol><p>User testing is the most valuable action in product/service management success and a solid pillar for google design sprint.</p><p><em>“You’ll need to work extra hard to engage your customer, put her at ease, and encourage her to think aloud.”</em> (page 256) — says GV’s Michael Margolis while writing <a href="https://amzn.to/2xdb6MM"><em>Sprint</em></a><em>, </em>he has run hundreds of interviews over video.</p><p><strong>2. What are practical challenges?</strong></p><p>How to find the perfect user tester? What The test scenario should look like? You either use a scorecard or just notes during test interviews…</p><p>Selecting test persons is a tough one as well. We had a situation when Decider invited someone who has also business interest in product and more was a business side than actual test person. It made it hard to follow the design sprint testing session and we doubted about the outcomes: “should we count this test result or just drop it”. Test persons should be representatives of the main segment of the product/prototype. If a team already has exact Persona(s) from design thinking, then test users should look at it as well. Although besides key similar characteristics which all 5 testers should have, they also better to be somehow different from each other to gain more insights. For example, one might be more critical, more skeptical than a favored person. Team might prepare a questionnaire about the user testers section on the first or second day of the design sprint.</p><h4>3. How do we manage the challenges?</h4><p>To gain valuable testing results and not just people saying amusing things to us, a good approach is to differentiate key features and functionalities in a prototype. To do so, the team with decider should emphasize key parts of the product/prototype and offer two or three different solutions to testers. In that way they pick their real favorite once, who they will actually use later on (when they will be left alone with the product). People tend to favor each other’s work and naturally they aren’t too critical when involved in testing interviews, they like to say exciting stuff about novelty and innovation, however, when they are alone they prefer more convenient, traditional products and services rather than using new breakthrough features.</p><p>We had real examples when people gave us stunning feedback while testing prototypes with us and later, they tend to be lazy for novelty and innovation. For example, for online shopping most of users prefer amazon style huge product catalog rather than smart chatbot assistance, when you say to system several your preferences and afterwards receive exact product suggestions. They say that they have no time for shopping but at the same time they are amused just scrolling left or right of the product when they are alone.</p><h4>4. What is our recommendation? A combo of our approach and standard</h4><p>Users should feel s/he is part of great things and isn’t tested by him/herself. Interviewer might make a short inspiring intro to make the user excited about the process and novel product development.</p><p>Team members should be invisible to make sure they do not interrupt and make the user uncomfortable.</p><p>Instead of using sticky notes on the wall, a more convenient way to track the answers to key questions might be to make it in the spreadsheet. Although it makes it easier to see patterns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*JA3Sv66fykUhPNCx" /></figure><p>We recommend <a href="https://voltagecontrol.com/blog/the-voltage-control-design-sprint-scorecard/">scorecard by Voltage Control</a> as it is a crowd favorite — sprint facilitators love how it allows individuals to capture scores and automatically aggregate them.</p><p>However, if you want to stick with the sticky-note method, use this board from Mural template to keep everything in one place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*zVGaurBkoklKOWte" /></figure><p>We used both: sticky notes by each case and scorecard the same time to gain most value from testing results.</p><h4>5. How Sum Up top findings?</h4><p>As our actual practice showed <strong>The Five-Act Interview</strong> really works and make great process for all participants: the interviewer, respondent and the team:</p><ol><li>A friendly welcome makes test users feel stressed out and melts ice. We found that the user tester needs to know about the process and the quick summary for design sprint but explained as fewer specific wording as possible. Also, the user’s expectation is that s/he should test the whole product and the explanation about the map and focusing only one spot for the prototype is essential.</li><li>Open-ended context questions about the customer even more opens test users to feel, think and talk open and cozy.</li><li>Introduction to the prototype is crucial for a person to get more intro and insights about what s/he is dealing with.</li><li>Detailed tasks to get customers reacting to the prototype is a good way to easily navigate users and proceed with the prototype.</li><li>A quick debrief nourishes to capture customer’s live thoughts and impressions.</li></ol><p>You can go through it with an amazing <a href="https://www.youtube.com/watch?v=U9ZG19XTbd4">video</a> from ‘Sprint’: The Five-Act Interview.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5205c24b8441" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agile-team/user-testing-in-design-sprint-5205c24b8441">User Testing in Design Sprint</a> was originally published in <a href="https://medium.com/agile-team">Agile Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>