Notice (8): Undefined index: Client [APP/View/Article/landing.ctp, line 97]"
Notice (8): Undefined index: Client [APP/View/Article/landing.ctp, line 97]
style="display:none;left:100%;">
Notice (8): Undefined index: Client [APP/View/Article/landing.ctp, line 106]
Notice (8): Undefined index: Client [APP/View/Article/landing.ctp, line 310]">
  • Notice (8): Undefined index: Client [APP/View/Article/landing.ctp, line 354]
    Notice (8): Undefined index: Client [APP/View/Article/landing.ctp, line 364]
    Notice (8): Undefined index: Client [APP/View/Article/landing.ctp, line 374]
Smashing Magazine
Maximizing The Design Sprint
0:00 02:04

A sprint refers to a variety of processes like a development sprint which is a set period of time for software development work and review, a design sprint which is a set period of time for a design team to create functional designs ahead of the development spring and a Google design sprint which a 5 day process used to understand if an idea maps to customer needs or opportunity without having to launch a minimal product. Following the process developed by Google Venture’s website, the author participated in a sprint that had the goal to use their pre-built kit to build an app in five days or less down from 6 months. On Monday, they set goals and targets and learning about potential users from customer experts. On Tuesday they drew from inspiration and sketched solutions. On Wednesday they chose the winning sketch and made it into a storyboard. On Thursday they prototyped and on Friday they tested the prototype with customers. The prototype illustrated their main value propositions. The features were only available through their kit and the speed with which it would be possible to have a fully functional app was through their kit. However, these value propositions didn’t really resonate with customers. The kit didn’t let developers have the level of customization the needed to satisfy customers but it wasn’t a waste of time because the power of the sprint is being able to avoid wrong turns letting major decisions be made while sidestepping business paralysis. A sprint however doesn’t just happen, it take preparation before during and after. The three weeks before are important. The first week is used to confirm the sprint with stakeholders and participants and inform them of the rules and schedule. The second week is to follow up on interviews and the third is to gather supplies, schedule interviews and send reminder emails to participants. After the sprint it’s important to decide what’s the M.M.P., and if the prototype reflects the critical features, then test it for usability.