me
Design-stream call 25/04/2014
by Sven Laux - Friday, 25 April 2014, 4:34 PM
 

Hi,

Attendees:

  • Michael, Petra, Paul, Tony, Sven

Thanks for a very productive call / screenshare!

Notes:

Progress report

  • Sven
    • Focused on coordinating design tasks since our discussion at the end of last week.
    • Detailed walk through of Mike's work and given some feedback.
    • Given very high level briefing to Petra to tackle Asset Management (priority for the authoring tool developers).
    • Overdue on planning the next sprint.
    • No blockers.
    • Next tasks:
      • Work with Petra on Asset Management in more detail
      • Plan next sprint in JIRA
  • Petra
    • Made a start on engaging with asset management requirements.
    • Gathered several questions, (some of) which we talked through on the call
    • Started by looking at the asset upload process.
    • Blocker:
      • Question over where to get started (Course assets or asset management); has been addressed and the call and will be overcome by working together with Sven next week.
    • Next tasks:
      • Start with page designs for browsing asset library, asset display, selection and actions
  • Michael
    • Updated courses dashboard and worked in feedback from review sessions
    • Started with a wider design review across course structure, page structure and actions menu
    • Developed designs with floating actions menu and consistent menu 'trigger'
    • Developed new approach to course structure viewing / editing
    • Tackled issue of multiple select / actions on multiple items in the new design approach
    • Blocker:
      • No access to page structure design project (resolved as part of the call)
    • Next tasks:
      • Develop design for 'selected page' panel in course structure 
      • Develop design for folder/section actions menu (and trigger), incl. multi-select
      • Consider how the new design approach could flow into the page structure
  • Paul
    • No further work on authoring tool design tasks since last sprint
    • Awaiting next sprint definition
    • Has given Petra high-level brief on Open Input component
    • No blockers
    • Next tasks:
      • Tackle design of component configuration (2-3 examples) on the basis of real configuration data (i.e. JSON schemas)
  • Tony
    • Input on actions menu and top bar to save screen real-estate
    • Hoping to get time for a design review next week
 
Reply