MoodleNet/Design Sprint

Revision as of 10:44, 14 June 2018 by Doug Belshaw (talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

<< Back to MoodleNet index


CC BY-ND Bryan Mathers

MoodleNet Design Sprint (May 2018)

Overview

Moodle worked with Outlandish, 21st-25th May 2018 on a design sprint for the MoodleNet project. A prototype overview video is available along with all of the photos capturing the work we did!

Aim(s)

  • Martin Dougiamas: "For me, it's a visual prototype that is good enough for anyone to quickly understand what MoodleNet does and how it could look and feel."

Agenda

Outlandish's overview of the Design Sprint: File:MoodleNet Design Sprint.pdf

Martin Dougiamas at the Design Sprint

Monday

Focus: Collect

Morning

  • Introduced ourselves and defined roles
  • Got up to speed on sociocracy
  • Outcome focused session
  • Identify risks and mitigations

Afternoon

  • Data gathering and analysis
  • Process / journey mapping
  • Target User work
  • Plot the user scenario
  • Create the user Point-of-View statement


Outcomes

Wireframing ideas at the Design Sprint

Tuesday

Focus: Explore

Morning

  • Worst possible idea
  • How might we...?

Afternoon

  • Crazy eights
  • Idea generation
  • Decision time
The very first user test of MoodleNet

Wednesday

Focus: Prototype

Morning

  • Wireframe user journey
  • Sitemap creation
  • Wireframe screens
  • Outlandish designer creates a low-fi prototype with team

Afternoon

  • Content and UX writing
  • User testing script & prep
Setting up a day of user testing

Thursday

Focus: User test

Morning

  • User testing
  • Rolling retrospectives

Afternoon

  • User testing
  • Rolling retrospectives
  • Gather our user testing evidence and pool our observations
The MoodleNet design sprint team (Moodle and Outlandish)

Friday

Focus: Iterate

Today has flexibility, but in short it’s about iterating the wireframe. At the end of today Moodle will walk away with a prototype that’s been tested AND iterated, so there is some evidence-based confidence in it as a solution.

Morning

  • Prioritised existing feedback
  • Captured rest of the feedback to inform MVP
  • Wireframed UX solutions, based on user testing

Afternoon

  • Producing the expanded and improved-upon clickable XD prototype
  • Created screencast overview of the prototype

Walked away with a prototype and evidence-based confidence in taking it forward as a product.

Data

The following contains sensitive data, so shared on a need-to-know only basis. Please ask for access if required and appropriate.

Useful links

A dumping ground for things on this wiki and elsewhere that may be useful during the week. Unordered.