2015-10-23 Dev Planning Meeting notes

Owned by Jane Young (Unlicensed)
Last updated: Nov 11, 2015Version comment
2 min read

Date

Attendees

Goals

  • Decide on approach for Topic page development
  • Confirm tasks for next sprint

Discussion items

ItemWhoNotes
Topics and programmes approach approved 

 

Using third party systemAndrew
  • Andrew Bredenkampto record in Confluence why we are not recommending that Squiz is used for building a content API for the topic or programme pages

 

Advantages of using Squiz as a content API
  • already established CMS with know within in the team and Web editors
  • no further set up of new platform or systems
  • sprint spike has partially completed the work
Disadvantages of using Squiz as a content API
  • testing suggests that the final solution will be brittle
  • to get it to work we are effectively creating a unique solution which could be complex to maintain and possibly not supported by the vendor
Advantages of third party system to provide content API
  • can choose a solution which fits the problem
  • could be used as a way of trialling a new system to replace the current CMS
Disadvantages of third party system
  • another system to be learnt and maintained by core web team - the core team will be managing the topic pages.
  • if web publishers in the faculties are maintaining programme pages this would mean them learning a new system.
  • potentially delays in getting approach approved for lack of requirements gathering
  • another platform which needs to be set up and configured in an ITS platform

Development processNathan

Nathan would like the designs to be coded directly into the system rather than being first developed in photoshop. He feels overall this will reduce time taken to delivery.

Joe feels this would stifle the design process as it would be slower to do and can make you more reluctant to adjust the design. He feels by coding the design once the final result will be cleaner as there won't be reworking.

Division of labourNathan

Nathan would like Joe to do the front end design for both COO and Topic pages. Nathan would then take on developing the SASS for both.

This is a more efficient way to work as it will help keep the development work consistent. The additional WIPII time spent on COO would be balanced by not needing to develop the SASS.

Jane Young (Unlicensed) agreed to approach.