comp90082-eportfolio-team03

1. Project Introduction

Project Background

E-portfolio is a web application that allows users to record and share their personal information and works in digital form. In general, those information can be input text, electronic files, graphics, multimedia and other forms of content. At the same time, it is also an important platform for the display of users’ capabilities and self-expression.

• For students, E-portfolio, like traditional portfolios, can help them reflect on their learning and allow students to have a better understanding of learning strategies and learning needs. The E-portfolio no longer need the learners to keep the paper evidence collected, instead it stores them in a more secure server.
• For mentors, appraisers, managers, and even employers, they can remotely access to these information to check the progress of learners and evaluate students’ learning profiles, while finding interested employees. Through E-portfolio, the communication with students are strengthened, and it reduces the cost of assessment and quality assurance.

Project Goal

The rational and effective use of E-portfolio is particularly important for every student. Our group aims at developing a user-friendly E-portfolio website for both the staffs and students in the University of Melbourne. This E-portfolio website would provide a platform for users to maintain their personal photos, history works, resumes, etc. which would not only facilitate the students but also those faculty and employers.

2. Client Information

3. Supervisor Information

4. Team Information

• Our team consists of six students from Master of Information Technology. With a strong and active team, we actively engaged in finding out solutions for our clients and we keep our minds in supporting the clients’ needs all the time.

• In our scrum team, there are three roles — Scrum master Quality Manager and Scrum Team Member.

  1. Considering the size and composition of our team, some responsibilities such as defining requirements and risk management are assigned to the whole team rather than determined by Scrum Master.

  2. As a student team without professional developers, our Scrum Master and Quality Manager also participate in designing and developing the website.

  3. The Quality Manager is not the only person responsible for testing, but needs to check the quality of the overall development.

  4. We do not distinguish between front-end and back-end developers, each member plays a cross-functional role (the roles include designer, programmer, tester and risk manager), which will make the most of everyone’s capacity and improve the efficiency to the maximum extent.