FRED - Framsticks Visual Editor 
In this section you will find some information about the people involved in the realization of the project.

Who we are...:
Now Fred project is run as a base for 3'rd year students bachelor thesis and this state will continue until May 2002. Fred is likely to be continued afterwards. Currently team consists of nine people. It was expanded with the group of four 3'rd year developers at the beginning of February 2002.

Each member is assigned with particular duties and tasks, which he is responsible for. The customer is represented by Ph.D. Maciej Komosiński. Currently he is the only one person providing us with all domain knowledge. There are two people directly responsible for the project - project manager (Bernard Lange) and chief analyst (Michał Wróblewski). We are the people collecting information, obtaining requirements and preparing documents. We are supported by another two people - quality assurers (Dominik Smogór and Marcin Okoń). Their job is to verify documents we create and carry out the meetings.


FRED Project Stakeholders in details:
Role (Person) Responsibility
SDS Supervisor
(J. Nawrocki)		 Preparing document templates. Resolving high level problems.Coordinating the work of area managers.
Area Manager
(B. Walter)		 Coordinating the work of 4-6 projects. Progress tracking. Resolving external problems at the project level. Evaluating the work of students involved in the projects.
Project Supervisor
(M. Komosiński)		 Taking care of 3rd-year students. Accepting the scope of the project. Accepting the work of 3rd-year students. Evaluating their B.Eng. thesis.
Laboratory Supervisor
(>= M.Eng.)		 Tracking progress of 3rd-year students. Evaluating their work at laboratory classes. Opening and closing the laboratory room.
Client representative
(M. Komosiński)		 Providing the domain knowledge. Working with analysts on the software requirements. Participating in inspections and FAST meetings. Participating in Planning Games at the beginning of each release and increment. Creating (with validation manager) acceptance tests. Evaluating the project outcome.
Project Manager
(4th year)
(B. Lange)		 Preparing project plans. Managing risk. Writing exploration report. Progress tracking. Collecting project and product measures. Writing progress reports and sending them to the area managers and other interested parties. Team building. Creating baselines for each increment and release.
Chief Analyst
(4th year)
(M. Wróblewski)		 Writing (with help of the customer representative) user stories and software requirements specification. During FAST meetings taking on the role of recorder. Creating, with participation of other team members, conceptual design. Preparing presentation for 3rd-year students.
Meeting Facilitator
(5th year)
(M. Okoń)		 Preparing meeting agenda. Obtaining consensus on meeting date, time, and place. Notifying attendees on the meeting place and time. Running the meeting. Coordinating the work of recorder. Telling area manager about any problems concerning the inspection or FAST meetings. Passing improvement proposals to the area manager.
Verification Manager
(5th year)
(D. Smogór)		 Acting as a reviewer in all inspection meetings. Creating, with help of customer representative, acceptance tests. Organizing sessions of acceptance testing with participation of the customer representative. Passing improvement proposals to the area manager. Participating in all inspection and FAST meetings.
Developer 1-4 (3rd year)
(T. Kotwicki,
Ł. Kałek,
Ł. Gientka,
Ł. Krysztofiak)		 Designing, coding, testing, integrating, writing documentation.