Presentation on theme: "1 Focusing on users: Gathering users requirements Sarah Agarwal Consultant Web development Project Manager and Usability Engineer Internet Development."— Presentation transcript:
1 Focusing on users: Gathering users requirements Sarah Agarwal Consultant Web development Project Manager and Usability Engineer Internet Development group Institute for Learning and Research Technology University of Bristol
7 JISC funded national Portal Requirements Analysis project - Both the news and the weather… form popular - near-ubiquitous in the case of the weather – portal features, yet they formed the lowest rated features over all…. …Laughter was a frequent response to the inclusion of a weather channel in the portal Liz Pearce, Ariadne, March/April 2003
9 How to do the work? Unmeasurable objectives for the portal Project length – 2-3 months Literature review – virtually nothing! Visits and/or discussions with three universities in UK Analysing the LSE offering
10 Start of analysis Identify (define) target audience –Staff – primarily teaching –Students – postgrads and under-grads Key potential content areas identified from –LSE list of content –List of content from an existing internal specification –Any other suggested by people –No duplication with Blackboard
11 Content areas – staff: Room booking Personal data Calendaring / timetabling Programme / Unit information Staff info Financial data Personal web page Research (IRIS) Past exam papers Message boards Student info Programme admin Information services / libraries + 8 more Content areas – students: Contact students / staff Personal details Programme / Unit information Student info Timetabling Online document store Staff info Information services / libraries Past exam papers Financial data Assessment (student view) Find accommodation Students Union channel + 6 more
12 Content areas: issues Staff vs students Was the content identified what was actually required? Definition of individual bits of content Too much of it
13 Interviews Aim - to find out any additional content requirements (qualitative) - to prioritise requirements (quantitative) - to discover major issues and themes that could significantly affect the portal development (qualitative)
14 Interviews Interview subjects Staff x minute interviews Students x 12 - Postgrads and undergrads - 25 minute interviews
15 Interview method 1.Task analysis 2.Open questions and carefully meandering discussions 3.Card sorting (prioritisation) 4.Content identification … all in 25 – 60 minutes!
16 Did it work? probably! Good signs: 4 of the 10 most highly ranked content areas were originally identified by interviewees catalyst for clearer definition of business drivers technical development has started on implementing 4 of the top ten content areas identified issues raised are being taken seriously development more practical than aspirational
17 Ranked in Top 5 by: Content areaStaffPostgraduatesUndergrads Online document store Access via portal Contact staff / students Calendaring / timetabling Programme information Information services / libraries Notify Past exam papers Personal data Student information Top ten content areas
18 Ranked in Top 5 by: Content areaStaffPostgraduatesUndergrads Online document store Access via portal Contact staff / students Calendaring / timetabling Programme information Information services / libraries Notify Past exam papers Personal data Student information Top ten content areas
19 JISC funded national Portal Requirements Analysis project -
23 Internet Development (ID) 6 web developers 1 graphic designer 1.5 usability engineers 1.5 project managers 22 current projects, including…
27 References ID: CROS: 234car:http://www.234car.com/http://www.234car.com/ REDwww.bristol.ac.uk/researchwww.bristol.ac.uk/research University of Michigan cancels a closely watched portal project. Chronicle of Higher Education. April 11 th, University of Hull PORTAL project - "Apart from the weather, I think its a good idea by Liz Pearce, in Ariadne April Full Bristol portal requirements report at Planning and implementing user-centred design. Nigel Bevan and Ian Curson.