1

Teams

Sriram Mohan/Steve Chenoweth

Importance of team spirit

Effective requirements management can be done only be an effective team

Software Development is a team activity

2

Roles

Contact Client Supervisor

Secretary Librarian Guru Task assigner/monitor

3

Leadership Functions

Communication Coordination Setting goals & objectives Role model Represent group to outside Represent outside to group NOT: Give orders

4

Team member functions

Communication Participation [during meetings] Effort [out of meetings]

5

Meetings

Goal, an agenda and a focus Meetings don’t just happen

Planning Preparation Attention Commitment Effort

6

What to do during a meeting?

Status evaluation Plan Report Analyze Invent Summarize meeting at the end

7

Tasks

Define a task Small in size, must have measurable objectives

Assign a task Who is/are responsible?

Monitor progress Reports/logs

Complete task

8

Conflicts

Issue conflicts Keep it on the issue, don’t make it personal

Performance conflicts Missing tasks, violating standards etc

9

Manager

Monitor meet weekly with team receive status report weekly monitor teams’ role performance Provide feedback to team

Report to me weekly on general status recommend drastic action Mid and End of Quarter reports

Advisor voice of experience critique documents and programs

10

Client Interaction

It is our fault if the project fails because the client fails to communicate clearly, the project fails because the client incorrectly describes the real

problem ….. Other issues(see handouts)

11

Client Interaction

Present yourself professionally appearance organization speaking & writing

Be knowledgeable Clients domain Your expertise

Meet Expectations

12

Team Assignments

Will be announced in class.

13

To be done as a team

Team name Assign roles Swap schedules Contact client(once you have a list of times to meet). Try

and meet as early as possible Contact manager(again have a list of times to meet). Must

meet by the end of the week

14