2016-03-23 Team meeting notes

36 Topics Underway

11 being drafted

12 With SME

11 Back from SME / Ready for loading

2 Loaded

Review of Decision log

Date: 13 April - please block this out in your diary, particularly devs

First Topics - when content work is being done these should be prioritised:

• Biomedical Sciences
• Tourism Management
• Law
• Engineering x4 topics

What needs to be in place by deployment:

• Bugs fixed - all highest and high
• Content approved by SME in situ
• People images in place
• Content checked and corrections made or a decision by Jane that they don't need to be made for release
• Proofread
• Process for demoting old content and promoting new content
• Comms plan
• Deployment plan

Before a SME checks:

• • • Content loaded in Squiz
    • Rich media included - stories, slideshows, video
    • Content correct - Jane to make a call on any outstanding items on the corrections page
    • Tool tips in place or if they aren't an explanation
    • Design doesn't have to be perfect across all devices and browsers - we will recommend Firefox, IE11 or Chrome all on either a desktop or laptop.
    • Any bugs that aren't fixed Jane will let the SME know about

• Andrew Bredenkamp to load Law and Engineering 24 Mar 2016 
• Nathan Irwin to build a plain contents page 24 Mar 2016 
• Jane Young (Unlicensed) to ask ITS if they want us to go through their change process 24 Mar 2016 

Timing: I recommend we don't handover until release 1.1 is done as things may stay in flux. We will then need to take over making changes probably under early May.

What do we need to know to decide this? Potentially it would be good to run a 'training' session with BAU so they can make a call on who is capable. That way we can decide:

• who will edit topics and what is the workflow
• who will edit programme and what is the workflow

Once that is decided we can start pulling together the training material.

Look at a way to corral feedback:

• Possibly do a 'got a minute' solution
• When do we ask for feedback - if it is too soon then they haven't used the tool.
• FAD will get an email this/next week so they can review it and give feedback.
• Start and intranet page for the project and give more context

• Paul Seiler (Unlicensed) to provide survey questions to Nathan so he can build something 24 Mar 2016 

Discuss the possibility of writers being able to directly make simple content tweaks rather than note them all. Noting them can take longer than just changing them.

• Is it easy to understand how and where to do these edits?
• Who would train them?

• Andrew thinks this could be difficult for someone who knows nothing about Squiz.
• We will wait and see if the levels and changes decreases significantly.
• The project support people will be able to take over this work.

Team to raise any blockers not already covered\

WIP II Wish List - review of wish list