2015-12-02 Team meeting notes

Date

Attendees

Discussion items

ItemWhoTo discussNotes
Sprint planningJane

Sprint planning

 
Topic page contentAnneI'd like to have a follow-up conversation about the issue Joe raised. It would be useful to have an approach agreed asap, given the large amount of content work that is happening in this space at the moment.
  • Feedback from Joe was too much content and didn't fit the current wireframe.
  • Anne thinks we need to look at it another way of find ways to minimise it without losing the content.
    1. have a separate mobile interface
      • Nathan says that it is a no-no to give different audiences different information depending on their device. 
      • Paul - It could be that there are ways to have a more minimal first look but they still need to be able to drill down to all of the information.
      • Everyone agrees that it needs a lighter first interface and still retain the more detailed information.
        • to do this we don't have the design or content to deliver this.
    2. set parameters for maximum amount of content.
DegreeworksPaulTalk about feedback on approach from outside of team
  • Paul doesn't think using Degreeworks as the single source of content is going to work.
  • What we need on the website is something the uninitiated can understand not a staff member. 
  • The information the uninitiated is different they don't need the deep content or all of the details for every scenario.
  • It will take too long to get this sorted it is really an entirely different project that should be led by a different team. Heather etc. will look at what Paul has done and stay open to what could happen in the future.
  • Maintenance is going to be challenging as we won't have a source of how we have designed the content. Paul is going to look at writing style guidelines for how information should be displayed. It would be hard to maintain this centrally as we will never be the experts.
  • Could use our style for GUS as well. This information has the same audience.
RAID logJane

WIP II RAID - review of risks, actions, issues and decisions

 

BlockersAll team to raise any blockers not already covered from RAID review 
WIPII Wish ListJane

WIP II Wish List - review of wish list

 
Project CommsJaneDiscuss the possibility of having a mini website which tells people where we are at e.g. high level timing, our approach to different things, what they can look forward to, where they can contribute.