JOIN-E7005 IDBM Industry Project, FiTech

Topic outline

• 5.4. Design sprint 1 documentation (ASSIGNMENT)
  TASK

  What is a design sprint?

  As taught in the Project planning workshop (27.11.), design sprint is a flexible framework that helps you to maximize the chances of designing something useful for your client. There are many ways to utilize design sprints based on your projects’ needs and stage. For example, you can use design sprint to come up with initial concept ideas, expand on an existing concept, or explore new ways to use the concept. 

  The basic steps of a design sprint are the following, but you can modify this flexible process to fit your needs:

  1.       Understand – draw ideas from your research data

  2.       Ideate – brainstorm lots of ideas

  3.       Decide – Rank solutions, pick one

  4.       Prototype – Create different types of prototypes based on what do you want to test

  5.       Validate – Test and observe what is effective for users

  Design sprint documentation

  After completing a design sprint, it’s time to reflect on the entire sprint and learn from it. The purpose is to create some kind of a capture document as an artifact to show your supervisor, client, and course faculty what worked, what didn’t, and how to move forward. 

  The style and structure of each IDBM team’s sprint summary document may vary widely depending on the project and your client. Some projects may produce a detailed document that are several pages long while others may use an executive summary style. 

  To create an informative design sprint document, you may want to incorporate photos or videos of your sprint activities, including whiteboards, Post-it notes, prototypes, discussion notes, and anything else that was created during the sprint. As an example, your document may look like a photo album with pictures and notes that clarify the visual artifacts that were created. You may also want to include questions or notes of the identified gaps in your knowledge that need to be answered with further research. Then, iterate with another design sprint to get them resolved.

  INSTRUCTIONS SUMMARIZED

  In the documentation, the following topics should be answered in one way or another (however, the purpose of the list is not to function as headers to your document)

  • Why – What is the relevance of what you did this sprint to your project overall? What did you aim to learn?
    
  • How – What did you actually do during this sprint? How did you gather information? What methods did you use to learn more about your critical unknowns?
    
  • Results – What is the data from your sprint?
    
  • Insights – What are your key learnings from the sprint?
    
  • Implications – Returning back to relevance: what do the insights mean for your project overall? What questions could you address in the next steps of your project?

  
  

  EVALUATION

  Pass/fail

  DEADLINE 5.4.

  Submission form in "ASSIGNMENTS"