Team Roles

There should be nine roles in a successful team, and some team members will play more than two roles. So our team tried to assign each person's role in the team as much as possible according to this theory.

Emerson serves as Manager and is also responsible for User Interface. He is responsible for the progress of the overall project, coordinates the plan with the actual progress, and conducts User Interface's design follow-up programming.

Rasmus serves as Require Analyst, analyzing the feasibility of the web page responsible for understanding and communicating system requirements. It is a core role in the team. It is necessary to fully understand the user's needs for the system and correctly obtain the user's needs from a large amount of information investigated in detail.

Billy serves as System Design and is also responsible for Technology Construction. First, he must complete the technical file to ensure that the work progress is within the plan, and then wait for User Interface be designed then system architecture. Give the most appropriate solution to the common application scene of web pages. Also be able to assess the costs of achieving specific functional requirements for our team.

Icy is responsible for User Construction and User Interface. Documents provided for users of software systems, writing of text, patterns, promotional materials, advertisements, and other inserts on web pages.

Lucy serves as Quality Control, HR, and Programmer. When coordinating within the team, ensure that all aspects of the project are likely to be implemented and participate in programming to personally estimate project quality.

Michael acts as a programmer, enters data, and determines the output requirements of this project. Arrange project requirements to include analysis requirements in the program; Preparation of workflow flow charts and the ability to use computer knowledge, subject matter, programming languages and logical diagrams.