Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

Date

Attendees

Discussion items

ItemWhoTo discussNotes
Review of recent scope, design and content decisions made by Paul and JoTeam

Review feature release proposal

Discuss '3rd party' dependencies and potential risks

Review content for Topic pages

Define content development approach and boundaries

Re-evaluate release plan's timing estimation (both development + content)

Filtering

  • implemented in GSA
  • Squiz queries GSA
  • strengthen the results information
  • would be a different look than the current functionality.
  • time involved - max one sprint for both devs

Content switcher

  • will reuse existing webstruxures api
  • need to redesign how it looks
  • time involved - 1/2 sprint x2

Topic page

https://vuw.sharepoint.com/sites/wipii/_layouts/15/GroupsDocuments.aspx

  • content stored in Squiz
  • stories - could be structured by topics but could also tag it so it can be used in multiple ways. An API would be used to draw in the content to the correct place.
  • could consider how pubs could use this but this could be scope creep so shouldn't have too much time invested in it
  • Paul feels there is too many stories, Anne says Architecture is story rich because there are many subjects under this. So many stories have been included as there aren't images and video to enrich the content.
  • Slideshow of images - Joe feels having a gallery of images is too distracting but for Anne this should be a slideshow.

 

 

 

Sprint planningJane

Sprint planning

 
BlockersAllteam to raise any blockers 
Social MediaJanePossible enhanced to Topic/Degree pages - to discuss briefly and then possibly log as future enhancement. 
Critical PathJaneWe need to look in more detail at the timing of the project to ensure we can complete the MVP (but hopefully more) 
  • No labels