2015-04-16 Team meeting notes

• Layout of 317
• No issues
• Pinboard/white board requests will follow

• Ongoing recruitment for UI role
• 2 candidates identified for initial discussion
• Tester - currently reviewing options
• May want to review how we feel about testing for content

• Currently have these with the core team - for personal development and issues
• Will have one per month
• Chrissi has scheduled a fornightly approach

• Referred to the following Confluence page > A proposal on where we start development
• Proposed select one faculty and a school within - address courses, programmes and subjects for this area
  • Noting would need to understand high level for PG and research
• Two views for how we do this
  1. Trial one faculty and school, and learn lessons to refine and move forward to other faculties and schools
  2. Create a core structure/template/IA and sell to all faculties and schools before commencing. A core to be used for all with some flexibility as required,
• Publications content aligned with web content

The summary below was discussed in meeting.

Definitions of stakeholders/users/customers were discussed. Some clarity is needed here. Chrissi Dean (Unlicensed) to pick up.

• PMO
  • Present proposed delivery approach on Tuesday
    • Need visual for discussion
• Meeting with Faculty Managers (end April/early May)
  • Agree what is to be presented - core common structure of faculty and school? Content strategy of faculty and school? Anything on Course and Subject Information (CSI)? Agreed: Content Strategy
  • Plan for follow up workshops within faculties and schools (Just FHSS first, or speak to all at high level then focus?): One Faculty at a time. Tash to feed in thoughts of who.
• Stakeholder engagement/user research (e.g.)
  • Preparation
    • Breakdown of agenda for each meeting/workshop - inputs and outputs
    • Review list of key artifacts (as noted by Chrissi) and priority, inputs for these etc.
  1. Meet with Faculty Managers Groups (as above)
  2. Meet with one (FHSS?) or all (separately or individually - potential issues on too many people, logistics, availability etc.)
     • Using approaches already documented
  3. Workshops with users - students and academic staff (not covered in the above)?
     • Using approaches already documented - potentially one user group covering demographic across all faculties. Users identified will be wider that just students and meetings with Faculties and Schools will support identification of these.
     • Card sorts? - later in process
  4. CSI
     • Meet with reference groups - reviewing proposed approach
     • Further analysis needed across courses, subjects and programmes
• JIRA structure
  • Chrissi to review with Paul in creating backlog for the above, reviewing > Agile with JIRA during the high level analysis phase
• Project plan
  • Detailed plan for above tasks in next few sprints - with resources and estimates
  • High level plan for overall delivery approach - resources and proposed order (if known), no timescales (at this stage)
• Other business case and project management tasks (as in list)