me
Re: Design-stream call 14/03/2014
by Sven Laux - Saturday, 15 March 2014, 2:11 AM
 

Attendees:

  • Petra, Sven, Paul, Daryl, Al, Dan

Thanks for the productive call.

Notes below:

  • Progress update well received. It is felt the designers are making swift progress and have managed to start informing the authoring development stream. We expect that the next sprint will see us get ahead of the development efforts.
  • Sven has been leading the overall design effort and Petra has been supporting. Daryl has been concentrating on leading the development of the authoring tool frontend as well as the work on version 1.0.1 of the framework, which went out for BETA testing today. Tony has been unable to spend time on the project since producing an initial set of wireframes. 
  • We agreed on the proposed process and use of systems as above.
  • Mockflow stability and scalability was discussed. We have run into several issues (conflicts), which has caused loss of work for Petra on several occasions. While the work was recovered, this has been a setback and we no longer regard the tool as suitable for collaboration of multiple designers on a single project. To tackle this going forward, we have:
    • Decided to split the projects up into several sub-projects with a single owner/designer each. Unfortunately, this breaks the live view of the work for the community (apologies everyone!)
    • Created a 'project template', which will be replicated for each new system section (Action: Sven, done)
    • Set up a separate design project for 'Course structure', 'Login and profile' and 'Page editing' (Action: Sven; done)
  • Sven has also written to Produle (the makers of Mockflow) to log the issues and asked for them to get fixed. (Always the optimist!)
  • The specific design issue discussed was 'menus vs sections'. We agreed:
    • That each course would only have a single menu rendering engine (plug-in).
    • That in the course structure, we therefore aren't editing menus as such but rather sections or folders. The designs produced need updating. (Action: Sven; done)
  • Resource and sprint planning for the next design sprint: The next design sprint will start on Monday, 17th March and run until end of day Weds, 26th March. During this time, we have the following time available for design work: Sven: 3 days, Petra: 4 days, Paul: 3 days. This means we should aim for a burndown of around 20 points.
  • We agreed to divvy out the priorities as follows:
    • Paul: Page editing
    • Petra: Login and Profile
    • Sven: Component editing
  • The current sprint needs to be closed and the new sprint needs to be set up in JIRA. (Action: Sven, done)

 

Thanks
Sven