Page Comparison

COO wireframe development

• Joe (1 day - subject to meeting 23/09)
  • development tweaks
  • feedback to users

• Topic and programme release plan - Chrissi
• Release 1 of taxonomy - All
• Release 2 - scope of second taxonomy release - Chrissi, Paul, Joe
• Topics test planning - Joe & Paul
• Next round of changes to the wireframe - Joe
• Topic page build in Squiz - Andrew
• Testing design for programme and topics (spike test) - Andrew
• Programmes - consultation with just CSP group
  • Review of group feedback - Paul & Joe
  • More internal consultation with web team (Nathan)
  • Priorities for release - Chrissi

Topics taxonomy

• Changes to the taxonomy - Paul

Staff profiles

• Review of Fronde feedback - Nathan, Andrew, Chrissi, Paul
• Meet with ITS - Nathan, Andrew, Chrissi, Paul

Events

• Review of Pauls stories - Nathan, Andrew, Chrissi

Content

• Topics writing - Anne and Sam
• Meetings with HoS's - Anne and Sam

Analysis

• Library - Paul (discuss with Nigel Friday 25th)
• Events feedback - Paul
• Staff profiles - Paul
• Disciplines - Paul

Project management/other

• Continued comms & consultation planning - Chrissi
• F&S planning
  • Consultation - Chrissi
  • Web publishing model - Chrissi and Nigel
• Terminology - Chrissi/Nigel/Madeleine
• Freeze topic and subject grouping for remaining content development

Taxonomy release 1

Second taxonomy release

Finalise topic design

Topics release plan

• Second release for taxonomy (subject to scope agreements in sprint 21) - Joe and Andrew
  • Search implementation - Andrew/Nathan
• Wireframe testing - Paul and Joe
• Initial review of GA and mouseflow for taxonomy and subjects a-z (present back to PMO) - Andrew and Chrissi
• Survey results - Chrissi and Paul
• Spike test work continued - Andrew
• Content - interview and writing for topics - Anne and Sam
• Topics release plan - Chrissi and Paul
• Staff profiles - tbc
• Second round of developments for programmes (based on agreed priorities and feedback)
  • Priorities and releases need to be documented and agreed
• Topic API breakdown - Joe and Andrew
• Review of topic and programme builds - Nathan, Joe, Andrew, Paul, Chrissi (week 2)

• Second round of developments for programmes (based on agreed priorities and feedback) continued
• Content - interview and writing for topics

• Topic build & programme build
• Content - interview and writing for topics
  

• Topic build & programme build
• Content - interview and writing for topics
  

• Topic build & programme build
• Testing
• Content - interview and writing for topics

• Staff profiles 
• Further staff profiles analysis - subject to Ian availability and gaining an understanding of ITS plans for this area
• Prioritisation of requirements

Other WIPII epics

Write up embedded media and images

F&S structure & purpose

F&S order recommendations

F&S development/release approach

All faculties preparatory work (review of content etc.)

News & events

Features (Anne)

Changing domain names of schools (moving away from acronyms).

1. Create list of alternative domain names.
2. Test with users if necessary
3. Finalise list
4. Later: implement changes

• Do we want user stories for f&s (as per programmes)?
• Any further demographics work required? Discuss at a team story time

• build - Andrew and Joe
  • API Design
• Staff profiles - Fronde
• Topic testing plan
• Topic content
  
  • editing existing Topic pages and sending for SME approval
  • interviews with academics
  • writing up content
  • sending topic pages for SME approval
• UG Degree content
  • Degree examples - Paul
  • Degree content - Gabe and Alida
  • Apply process - Gabe and Alida
• Alternative search terms - Paul
• PG programmes page - Tash
• Project Content on Intranet - Jane, Paul, Alida and Gabe

• Topic build
  • Design - Joe
  • Build - Nathan
  • API and Squiz - Andrew
• Topic test
  • planning - Jane & Paul
  • execution - Andrew and Planit
• Topic content
  • editing existing Topic pages and sending for SME approval
  • interviews with academics
  • writing up content
  • sending topic pages for SME approval
  • Loading content
• Presentations of F&S approach to Schools - Jane

• Topic build - Andrew and Joe
• Topic testing - ?
• Topic content
  • interviews with academics
  • writing up content
  • sending topic pages for SME approval
  • Loading content

• Topic build - Andrew and Joe
• Topic testing - ?
• Topic content
  • interviews with academics
  • writing up content
  • sending topic pages for SME approval
  • Loading content

• Staff profiles 
• Further staff profiles analysis - subject to Ian availability and gaining an understanding of ITS plans for this area
• Prioritisation of requirements

Other WIPII epics

Write up embedded media and images

F&S structure & purpose

F&S order recommendations

F&S development/release approach

All faculties preparatory work (review of content etc.)

News & events

Features (Anne)

Changing domain names of schools (moving away from acronyms).

1. Create list of alternative domain names.
2. Test with users if necessary
3. Finalise list
4. Later: implement changes

• Do we want user stories for f&s (as per programmes)?
• Any further demographics work required? Discuss at a team story time

Law workshop

Business workshop

Arch and Design workshop

Science workshop

Education workshop

Engineering workshop

Prep for CSP reference group on 15 June

CSP UG and PG options

Potentially scheduling of next steps from F&S workshops

Ethics application and submission

Staff profiles

Further Library analysis

FHSS workshop

Workshop next steps - content and functional next steps (including epics working groups)

User testing (subject to approval) - as a minimum test planning (Sam, Anne, Paul, Joe)

CSP reference group meeting - subject focussed

Centres, institutes and chairs next steps/approach, content approach - Paul/Anne

Staff profiles continued

Prepare for FM meeting - finalise approach?

Finalise personas - review from Joe, gaps with Marketing

Development areas - still to be discussed

Videos - Sam

Content management

Subjects sorting

F&S approach

F&S's:

User research

Straw person(s) development

FM meeting - workshop updates and web analytics. Site purpose?

Initial functional requirements groups

Channels (carried over from S13)

Staff profiles survey and analysis

Scope "challenging issues" for new staff profiles

CSP:

Finalise our subject taxonomy

Draft alternative search terms for topics and subjects

Programme template

Topic page design

Other:

Write up thoughts on metadata and tagging

F&S usability testing

CSP

F&S's:

User research (AN & PS)

Develop final proposal

CSP:

Topics - testing of proposed taxonomy, and some terms/labels (PS and SM)

Topic prototype development

Programme page - consult with selected stakeholder review group (incl. Jane, Charlotte, Sofia) (PS) - this will rollover to Sprint 16 and could potentially take longer depending on what comes out of these meetings.

Other:

Tagging in Squiz

Info pages - AB - this will roll over until Sprint 16

Functional testing

Events and News (PS) - this will roll over until Sprint 16 as we are waiting on feedback.

Write user stories for images and embedded media (PS)

FYI: Chrissi a/l

Complete testing on topics taxonomy

First prototype/wireframe for topic page

Draft of programme page

Proposed solution for consultation

F&S usability testing (part 2)

CSP

F&S's:

• Confirm and communicate that FHSS is first cab
• Planning the presentation of Faculty and Schools approach (AN)
• Socialise F&S proposal (AN)

CSP:

• Topics and subjects
  • Elicit feedback on subject groupings from faculties and schools (PS)
  • Test Topic Page content to see if what it needs to achieve matches the proposed technical solution - Anne Nelson (Unlicensed) and Sam Motion (Unlicensed)
• Programme
  • Scoping Programme requirements - (PS) and (AN)
  • Programme prototype/wireframe (JL) - requirements won't be finalised until the end of the first week of sprint.
• Mapping relationships between subjects/topics/programmes/courses Sam Motion (Unlicensed)
• Identify alternative search terms for subjects and topics (PS)

User research

• Complete current students and document (AN) - also Tash
• Scoping international (AN)

Other

• Personas: Overlay current student goals and behaviours on a small number of the current personas. Anne and Sam to help select best match (PS)
• Functional testing (JL)
• Continue to nurture events and news (PS)
• Testing the development site and tweaking as required (AB)

FYI: Chrissi a/l

CSP and F&S wrap up

Milestone decisions

F&S's:

• Approach feedback v2 (AN)
• Delivery/order (CD)
  • Content mapping and further analysis to support decisions, delivery approach etc. (PS)

CSP

• Reference group (CD)
• Topics and subjects
  • Elicit feedback on subject groupings from faculties and schools (PS & SM)
  • Approval/sign off on groupings (CD/PS)
  • Prototype/wireframe development (JL)
  • Topic page example writings (SM)
  • Planning for content writing (SM)
• Programme (UG focus)
  • Scoping Programme requirements - (PS) and (JL)
  • Content strategy (AN)
  • Content outline (AN)
  • Programme prototype/wireframe (JL)

User research

• 2 additional new students (SM)
• Testing planning (PS)

Dev/technical work

• Tagging (AB)
• Info pages (AB)
• Test site in Squiz (AB)

Other

• Staff profiles - discussion with ITS (CD)
• Demographics - analysis of reports (AN)
• Final work on personas
  • Future (PS)
  • Current (SM)
• Comms - plan from Kim and specific focus on F&S communication and sign off. Presentation for SLT (CD)
• Resourcing (CD)
• Channels summary (SM)
• Relative sizing (CD) - S, P and F&S

Topic page

Programme page

F&S approach

Sizing/estimating

Release options/breakdown

Programmes

• Present draft programme content strategy at CSP reference group - Anne
  
  • Create table of content (from plan) with sources. Suggested includes the following columns - Section, content area, source, new content (Y/N) - Anne
• Continue wireframe development - Joe
• Map programmes back to topics or megatopics - Paul
  

Topics

• Circulate final topic content strategy to CSP reference group
  • Create table of content (from plan) with sources. Suggested includes the following columns - Section, content area, source, new content (Y/N) - Anne and Sam
• Finalise wireframe development - Joe
• Touch bases with Careers Team for final confirmation of careers content approach - Anne
• Review of options for CSP delivery - Anne & Paul
• Plan for initial engagement with faculties and schools (ensure done in conjunction with Chrissi, and presented as investigation - nothing finalised yet)
  • Assumes starts with FHSS but to confirm - will need to discuss with K M-G
  • Plan workshops/interview questions
  • Run initial workshop
• Finalise topics and subjects groupings - Paul

Faculties and Schools

• Review delivery approach options - Paul What order to we approach each content area?
• Prepare presentation/consultation on F&S approach - Chrissi
• Do we want user stories for f&s (as per programmes)? I believe they are valuable, necessary even - Paul
  

Staff profiles

• Unpack the interface and overlap between ITS and us - Paul

Development planning

• Templates - investigate what information is required to ensure that templates existing are sufficient, or what other 'elements' are required - Andrew?
• Test site development - Andrew?

PM work

• Resourcing - Chrissi
• Sizing in association with CSP delivery task above - Chrissi
• Comms continued - Chrissi
• Prioritisation continued - Chrissi

Analysis work

• Trace sources of content and where it surfaces - Paul
• Initial interviews to plan/prepare for PG user research - Paul
• Do you want user stories written for any other epics at this stage? - Paul

Other/overlap from sprint 17....

• Test planning?
• Channel summary
• Info pages
• Tagging
• Orientation for Ben (Engagement BA) - Paul & Chrissi

Priorities

1. Topic feedback from CSP reference group and sign off from PMO
2. Topics content - sources and writing
3. Programme development
4. F&S approach presentation/consultation

Content

• Planning
• Topics
  • FAD interviews
  • Estimate on how long to get all FAD topics drafted
  • Metadata - Sam
• Careers
  
  • Societies and History (7 topics) - Anne
  • Languages and cultures, Creative (- music) (7 topics) Sam

Dev & other tools

• Programme wireframes - Joe 50%
• Course wireframes - Joe 50%
• Squiz API - Andrew
• Brainstorming post discussion with Fronde - Andrew & Nathan
  • Staff profiles - Nathan & Andrew
    • Discussion with Fronde (28.08.15)
    • Next meeting with ITS (including Edwin and someone from Banner team) - Andrew & Nathan

Analysis

• Topic and programme consultation - Chrissi & Paul
• PG testing/user research - Paul
• Events - further analysis - Paul
• Staff profiles - Paul

Project managment/other

• Comms planning
• Consultation planning
• 2015 plan and review of delivery approaches

Revised delivery for CSP to be reviewed

F&S delivery approach to be discussed

CSP writing continues

Programme template continues

Topic template to PMO (meeting cancelled last sprint)

COO work commences (Joe)

Tools to be investigated (dev and analysis)

Content

• Topics
  • FAD interviews - Sam and Anne
  • Estimate on how long to get all FAD topics drafted
• Careers
  • (x topics) - Anne

Dev & other tools

• Programme & Topic wireframes - Joe 70%
• Course wireframes - Joe 30%
• Squiz API - Andrew
• Brainstorming post discussion with Fronde - Andrew & Nathan
  • Staff profiles - Nathan & Andrew
    • Discussion with Fronde (15.09.15)
    • Next meeting with ITS (including Edwin and someone from Banner team) - Andrew & Nathan

Analysis

• Topic and programme consultation - Chrissi & Paul
• PG testing/user research - Paul
• Events - further analysis - Paul
• Staff profiles - Paul

Project managment/other

• Comms planning
• Consultation planning
• 2015 plan and review of delivery approaches

Taxonomy release prep

• required - Andrew?
• Test site development - Andrew?

PM work

• Resourcing - Chrissi
• Sizing in association with CSP delivery task above - Chrissi
• Comms continued - Chrissi
• Prioritisation continued - Chrissi

Analysis work

• Trace sources of content and where it surfaces - Paul
• Initial interviews to plan/prepare for PG user research - Paul
• Do you want user stories written for any other epics at this stage? - Paul

Other/overlap from sprint 17....

• Test planning?
• Channel summary
• Info pages
• Tagging
• Orientation for Ben (Engagement BA) - Paul & Chrissi

Priorities

1. Topic feedback from CSP reference group and sign off from PMO
2. Topics content - sources and writing
3. Programme development
4. F&S approach presentation/consultation

Content

• Planning
• Topics
  • FAD interviews
  • Estimate on how long to get all FAD topics drafted
  • Metadata - Sam
• Careers
  
  • Societies and History (7 topics) - Anne
  • Languages and cultures, Creative (- music) (7 topics) Sam

Dev & other tools

• Programme wireframes - Joe 50%
• Course wireframes - Joe 50%
• Squiz API - Andrew
• Brainstorming post discussion with Fronde - Andrew & Nathan
  • Staff profiles - Nathan & Andrew
    • Discussion with Fronde (28.08.15)
    • Next meeting with ITS (including Edwin and someone from Banner team) - Andrew & Nathan

Analysis

• Topic and programme consultation - Chrissi & Paul
• PG testing/user research - Paul
• Events - further analysis - Paul
• Staff profiles - Paul

Project managment/other

• Comms planning
• Consultation planning
• 2015 plan and review of delivery approaches

Revised delivery for CSP to be reviewed

F&S delivery approach to be discussed

CSP writing continues

Programme template continues

Topic template to PMO (meeting cancelled last sprint)

COO work commences (Joe)

Tools to be investigated (dev and analysis)

Content

• Topics
  • FAD interviews - Sam and Anne
  • Estimate on how long to get all FAD topics drafted
• Careers
  • (x topics) - Anne

Dev & other tools

• Programme & Topic wireframes - Joe 70%
• Course wireframes - Joe 30%
• Squiz API - Andrew
• Brainstorming post discussion with Fronde - Andrew & Nathan
  • Staff profiles - Nathan & Andrew
    • Discussion with Fronde (15.09.15)
    • Next meeting with ITS (including Edwin and someone from Banner team) - Andrew & Nathan

Analysis

• Topic and programme consultation - Chrissi & Paul
• PG testing/user research - Paul
• Events - further analysis - Paul
• Staff profiles - Paul

Project managment/other

• Comms planning
• Consultation planning
• 2015 plan and review of delivery approaches

Taxonomy release prep

Content interviews with schools

COO wireframe development

• Joe (1 day - subject to meeting 23/09)
  • development tweaks
  • feedback to users

Topics and programmes

• Topic and programme release plan - Chrissi
• Release 1 of taxonomy - All
• Release 2 - scope of second taxonomy release - Chrissi, Paul, Joe
• Topics test planning - Joe & Paul
• Next round of changes to the wireframe - Joe
• Topic page build in Squiz - Andrew
• Testing design for programme and topics (spike test) - Andrew
• Programmes - consultation with just CSP group
  • Review of group feedback - Paul & Joe
  • More internal consultation with web team (Nathan)
  • Priorities for release - Chrissi

Topics taxonomy

• Changes to the taxonomy - Paul

Staff profiles

• Review of Fronde feedback - Nathan, Andrew, Chrissi, Paul
• Meet with ITS - Nathan, Andrew, Chrissi, Paul

Events

• Review of Pauls stories - Nathan, Andrew, Chrissi

Content

• Topics writing - Anne and Sam
• Meetings with HoS's - Anne and Sam

Analysis

• Library - Paul (discuss with Nigel Friday 25th)
• Events feedback - Paul
• Staff profiles - Paul
• Disciplines - Paul

Project management/other

• Continued comms & consultation planning - Chrissi
• F&S planning
  • Consultation - Chrissi
  • Web publishing model - Chrissi and Nigel
• Terminology - Chrissi/Nigel/Madeleine
• Freeze topic and subject grouping for remaining content development

Second release build

Finalise topic design

Topics release plan

Testing

• Second release for taxonomy - Joe and Andrew
  • Search implementation - Andrew/Nathan
• Wireframe testing - Paul and Joe
• Initial review of GA and mouseflow for taxonomy and subjects a-z (present back to PMO) - Andrew and Chrissi
• Survey results - Chrissi and Paul
• Spike test work continued - Andrew PRIORITY
• Content - interview and writing for topics - Anne and Sam
• Topics release plan - Chrissi and Paul
• Staff profiles - tbc
• Second round of developments for programmes (based on agreed priorities and feedback)
  • Priorities and releases need to be documented and agreed
• Topic API breakdown - Joe and Andrew
• Review of topic and programme builds - Nathan, Joe, Andrew, Paul, Chrissi (week 2)
• Content review approach - Tash