Point 3 Organization structure in project team

1. We consider two main aspects when creating a project team:

a) Role assigning

b) Communication between team members

2. Team project structure

Description: The team members are hierarchal divided into particular groups and each team has got his own hierarchy. Our project team will be divided into following groups:

.

a) Center group

1. Project manager

2. Control manager

3. Planning and tracking manager

Tasks:

• Elaborate propositions concerning the way of creating a project

• Project calculation

• Planning and schedule making

• Monitoring and controlling realization of project

• Selection and marks concerning staff

• Elaborate and presentation making to the client

Role	Responsibilities
Maciek Uberna - Project manager	Responsible for successful business outcome of the project staffing, acquiring resources for the project, personnel issues, top level work assignments, and client interaction. He is a top decision maker on the project, but normally defers technical decisions to the appropriate technical lead. Resolves disputes between project participants.
Krzysztof Golinski - Control manager	Controls information flow, communication in the team and finished tasks. He makes reports about progress and gives it to the Project manager
Jan Kowalski - Planning and tracking manager	Direct overall flow of technical work on the project. Directly responsible for project planning and overseeing the execution of work breakdown, estimation, scheduling and tracking.
Franek Bugacki - Requirements Manager	In charge of defining, maintaining and tracing product requirement. Ensures proper end user documentation is developed from the requirements.

b) Implementation group

Role	Responsibility
Leon Gruszka - Implementation chief	Responsible for construction, integration, product builds, development environment and deployment
Pioterk Kwiatkowski - Development Engineer	Responsible for construction and verification of source code and related documentation
Leon Zawodowiec - Development Engineer	Responsible for creating a databases tables Fill database with data Creating users Adding privileges Database tuning Making basic tests and corrections
Adam Ciota - Development Engineer	- Creating Project modules
Piotr Peja - Development Engineer	- Certification management
Zenon Strzalka - Development Engineer	- Payment management

c) Administration group

Tomek Juranek - Administration manager	Hardware and software installation Moving software Customer training Administrators training Databases fill Supervision system using Privileges giving Permissions giving
Zbyslaw Tomyn - Conservator	improvement modifications better modifications adjusting modifications System stabilization defining Hardware and software defining
Pawel Nowacki - Administrator	Configuring Security Maintaining Servers and Data Administrating consoles Making backup files Maintaining and restoring database
Robert Wiech - Administrator	Create a new Database Create simple passwords for every team members Editing the context Search file

d) Quality control group

Role	Responsibility
Zbigniew Bombka - quality control chief	Certification of systems before sending it to the client Forcing standards of gathering and data processing Elaborate standards concerning system architecture and implementation practices Testing new or modified software Elaborate disposition order Training He is also in charge of planning and directing all QA activities including reviews and testing
Gabriel Turek - QA Engineer	Checks if project is well organized, with appropriate life cycle If Problems are registered and reaction on these problems is properly
Hans Klos - QA Engineer	- Checks if members of the team have got their tasks and responsibilities defined - If staff is well trained according to the project
Rafal Sosna - QA Engineer	- Checks Plans among the documentation are implemented
Mariusz Domanski - QA Engineer	- Checks if documentation contains everything what is necessary
Michal Pruszkowski - QA Engineer	- Checks if documentation and coding standards are observe
Andrzej Wiecicki - QA Engineer	Checks if standards, conventions and practices are observe If software is stored in controlled bibliotheca If software is stored in protected places with safe way If software from outside suppliers have proper standards.
Andrzej Wroblewski - QA Engineer	Checks if tests are rigorous observe If projects uses suitable methods, techniques and tools
Bartek Dytkowski - QA Engineer	Checks if Data measurement is gathered and uses to improve processes and products
Czarek Magier - QA Engineer	- Checks if inspections and audits are carry through and properly organized

e) Documentation group

Role	Responsibility
Dominik Kloskowski - Documentation Chief	Coordinates and controls the process of creating the technical, user and administrator documentation
Dariusz Michalczewski - Technical Documentation Engineer	Prepares the technical documentation
Rene Ruso - User Documentation Engineer	Prepares the user manual
Waclaw Hawel - Administrator Documentation Engineer	Prepares the administrator manual

f) Interface group

Role	Responsibility
Adam Malysz - Interface chief	Supervision of subordinates Creates overall interface design
Robert Mateja - Interface Engineer	GUI development

g) Maintained group

Role	Responsibility
Grzegorz Wiercicki - Maintance Chief	Supervision of subordinates Calculates the maintance costs Prepares orders
Ronald Kuman- Maintance Engineer	Executes orders

j) Testing group

Role	Responsibility
Alek Romek - Testing Chief	Supervision of subordinates Preparing testing plans Scheduling testing tasks Assigns testing tasks
Witek Karalow -Testing Engineers	Performing tests of various modules Preparing reports

k) Analysis group

Role	Responsibility
Stasiek Andraszek - Analysis chief	Responsible for customer relations Supervises the work of his subordinates Reports confirmation
Rafal Siutek - Analysis Engineer	Setting up requirements for particular actors Defining Data storage mechanism Defining data management procedures Report preparation
Adam Baka - Analysis Engineer	Handling and preparing payment documents Payroll management Project overheads Report preparation
Krzysztof Rydzki - Analysis Engineer	Course management Conference management Report preparation
Edward Norton - Analysis Engineer	Product requirements Process requirements External requirements Creating a dictionary

---