J.E.D.I
Project Team The project team is composed of two sets of groups, namely, developers and end-user.
Developers consist of the project manager, analysts, designers, programmers, and quality assurance members. The end-user group consists of EDP or MIS Staff, user staff,
casuals and consultants. It is a small group of with a leader or manager. They regularly interact to fulfill a goal. It requires team spirit, contribution and coordination.
7.3.1 The Project Team Structure
The team structure can be organized as democratic decentralized, controlled decentralized and controlled centralized.
Democratic Decentralized DD The Democratic Decentralized DD Team Structure has no permanent leader.
Rather, there are task coordinators appointed for a short duration who are replaced later on by others who may need to coordinate other task. Decisions are solved by group
consensus. The communication is highly horizontal.
Controlled Decentralized CD The Controlled Decentralized CD Team Structure has a permanent leader who
primarily coordinates tasks. It has a secondary leader responsible for subtasks. Decisions are solved by group consensus but the implementation is done by subgroups.
The communication during implementation is horizontal but control is vertical.
Controlled Centralized CC The Controlled Centralized CC Team Structure has a team leader responsible for
team coordination and top-level decision-making. The communication between leader and team members is vertical.
The decision on what team structure to employ would depend on the project characteristics. Use Table 33 to determine the team structure to be used for a project.
Software Engineering 309
J.E.D.I
Team Type Project Characteristics
DD CD
CC
Level of Problem Difficulty High
Low X
X X
Size of Software Lines of Code or Function Points Large
Small X
X X
Team Duration Short
Long X
X X
Modularity of the Program: High
Low X
X X
System Reliability Requirement High
Low X
X X
Delivery Date Rigidity Strict
Lax X
X X
Sociability Degree High
Low X
X X
Table 33: Project Characteristics vs Team Structure
7.3.2 Project Responsibility Chart
The Project Responsibility Chart is a matrix consisting of columns of individual or functional departments, and rows of required actions. It supports the need to
communicate expectations and responsibilities among the personnel involved in the development of the software. It avoids problems encountered with communication and
obligations from being neglected. It answers the following questions:
• Who is to do what?
• How long will it take?
• Who is to inform whom of what?
• Whose approval is needed for what?
• Who is responsible for which results?
• What personnel interfaces are required?
• What support is needed form whom and when?
Software Engineering 310
J.E.D.I
A sample project responsibility matrix is shown in Table 34. P
r e
s i
d e
n t
P r
o j
e c
t L
e a
d e
r A
n a
l y
s t
P r
o g
r a
m m
e r
N O
V
5 N
O V
6 N
O V
7 N
O V
8
1. Pre-joint Meeting Task 1.1 Write product request.
R D
1.2 Set pre-joint meeting. R
R D
1.2.1 Set time and date. I
R R
D 1.2.2 Set place.
I R
R D
1.2.3 Identify facilitator and participants.
C I
R O
1.3 Invite participants. R
O 1.4 Distribute product request.
C R
Responsibility Code: R-Responsible I-Inform C-Consult S-Support Task Code: D-Done O-On Track B-Delayed
Table 34: Project Responsibility Matrix
Software Engineering 311
J.E.D.I
7.4 Project Scheduling
