Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

MoodleNet/Design Sprint: Difference between revisions

From MoodleDocs
No edit summary
No edit summary
Line 32: Line 32:


'''Morning'''
'''Morning'''
* Introduce ourselves and define roles
* Introduced ourselves and defined roles
* Got up to speed on sociocracy
* Outcome focused session
* Identify risks and mitigations
 
'''Afternoon'''
* Data gathering and analysis
* Data gathering and analysis
* Exercises:
Process / journey mapping
** a) Activity analysis
** b) Process / journey mapping
* Target User work
* Target User work
* Plot the user scenario
* Plot the user scenario
* Create the user Point-of-View statement
* Create the user Point-of-View statement


'''Afternoon'''
* Outcome focused session
* Identify risks and mitigations


'''Outcomes'''
'''Outcomes'''
Line 55: Line 55:


'''Morning'''
'''Morning'''
* Idea generation
* Worst possible idea
** Worst possible idea
* How might we...?
** How might we...?


'''Afternoon'''
'''Afternoon'''
* Challenging assumptions
* Crazy eights
* Idea generation
* Decision time
* Decision time


Line 72: Line 72:
* Sitemap creation
* Sitemap creation
* Wireframe screens
* Wireframe screens
* Outlandish designer creates a low-fi prototype with team


'''Afternoon'''
'''Afternoon'''
* Outlandish designer creates a low-fi prototype with team
* Content and UX writing
* Content and UX writing
* User testing script & prep
* User testing script & prep
* Decision on whether or not we will focus on a more developed build on Frida


[[File:user-testing-moodlenet.jpg|Setting up a day of user testing|thumb]]
[[File:user-testing-moodlenet.jpg|Setting up a day of user testing|thumb]]
Line 85: Line 84:


'''Morning'''
'''Morning'''
* User test
* User testing
** User testing with five teachers and the team observes
* Rolling retrospectives
** User testing with technical architect
** A tech review to identify technologies that could be used, opportunities for best development
** Creation of a user testing report, based on:
*** Behaviours
*** Expressed likes
*** Usability issues and failed tasks
*** Feature requests from users
*** Questions


'''Afternoon'''
'''Afternoon'''
 
* User testing
Gather our user testing evidence and pool our observations
* Rolling retrospectives
* Gather our user testing evidence and pool our observations


'''User test participants'''
'''User test participants'''
Line 112: Line 104:
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.
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.


Today involves:
'''Morning'''
* Wireframing UX solutions, based on user testing
* Prioritised existing feedback
* Wireframing new functionality, screens etc, as needed or requested by user test subjects
* Captured rest of the feedback to inform MVP
* Detailed content writing
* Wireframed UX solutions, based on user testing
 
'''Afternoon'''
* Producing the expanded and improved-upon clickable XD prototype
* Producing the expanded and improved-upon clickable XD prototype
* Created screencast overview of the prototype


At the day’s close Moodle will walk away with a prototype and evidence-based confidence
Walked away with a prototype and evidence-based confidence in taking it forward as a product.
in taking it forward as a product.


=== Data ===
=== Data ===

Revision as of 14:00, 25 May 2018

<< Back to MoodleNet index


CC BY-ND Bryan Mathers

MoodleNet Design Sprint (May 2018)

Overview

A place to curate everything related to the MoodleNet Design Sprint at the offices of Outlandish, 21st-25th May 2018, from 10:00 - 17:00. More coming very soon!

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."

Location

3rd Floor
149 Fonthill Road
Finsbury Park
London
N4 3HF

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

User test participants

  • 10:00 - Mary Cooch
  • 11:00 - Andrew Field
  • 12:00 - Miles Berry
  • 15:00 - Christian Turton
  • 16:00 - Jess Gramp

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.