01 November 2011

Project Proposal

My project proposal has officially been accepted by the University and I am registered for INF 388L for the spring 2012 semester.  Below is the working outline:

This project will give the student an opportunity to work with a user experience design team at a large corporation, helping to improve the experience of customers using OpenText software.  The student will be creating a prototype (and other information architecture-related deliverables such as wireframes) that translates business requirements for a new version of an enterprise software product (OpenText Web Experience Management 8.2) into a graphical user interface.  The student will be working within the context of established corporate UX guidelines, ensuring compatibility of interface labels, considering the impact of user flows through the system and evaluating feedback from the development team and software users.

The student will work on site at the OpenText corporate offices within the Development – R&D group as an extension of her current employment responsibilities in the IT department, which has been negotiated with her manager and agreed upon by her Field Supervisor.  The student will apply 125 hours to this project, approximately 9 hours per week for 14 weeks.  The project is scheduled to run from January 16-April 27, 2012 but could start as early as December 2011 due to changes in project planning and availability.

The Field Supervisor will meet with the student weekly to evaluate the status of the project by receiving updates on the progress of deliverables including any rework requested.  Development is expected to occur within an Agile environment utilizing Scrum methodologies, such as short daily meetings with stakeholders and work sprints.  The Faculty Advisor will meet with the student and the Field Supervisor at least once on site to monitor project status.

The culminating product will be a prototype of a UI which will be used by Engineering to develop release 8.2 of OpenText Web Experience Management.

No comments:

Post a Comment