Scribd
Upload
53 views

TMP3413 Software Engineering Lab: Launching A Team Project

This document describes the Team Software Process (TSP) for launching a team project. It discusses dividing projects into cycles with a launch and postmortem for each cycle. The team launch establishes roles, goals, meetings, and data requirements. It is important for setting expectations and building the team. The document outlines the steps in the TSP launch script, including reviewing objectives, assigning roles and goals, and establishing meetings and reporting. The launch prepares the team to start work on the project with clear responsibilities and expectations.

Uploaded by

Nurfauza Jali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
53 views

TMP3413 Software Engineering Lab: Launching A Team Project

This document describes the Team Software Process (TSP) for launching a team project. It discusses dividing projects into cycles with a launch and postmortem for each cycle. The team launch establishes roles, goals, meetings, and data requirements. It is important for setting expectations and building the team. The document outlines the steps in the TSP launch script, including reviewing objectives, assigning roles and goals, and establishing meetings and reporting. The launch prepares the team to start work on the project with clear responsibilities and expectations.

Uploaded by

Nurfauza Jali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
You are on page 1/ 32

TMP3413

Software
Engineering Lab

Lecture 03:
Launching a
Team Project
TSP Process Structure
 TSP projects are divided
into cycles.

 Each cycle starts with a


launch or relaunch and
ends with a
postmortem.

 Cycle content is
determined by the
team.

 Any lifecycle model can


be supported.

 TSP projects can start on


any lifecycle phase.
 The team launch is designed to begin the team
building process.

 This is when the managers and teams discuss the


roles, goals, the team meeting, and data
requirements. A team plan is then produced.

 During execution or implementation phase, the


developers will track planned and actual effort,
schedule and defects. Regular meetings (usually
weekly) are held to report status and revise plans.

 The cycle ends with a postmortem to assess


performance, revise planning parameters, and
capture lessons learned for process improvement.
Why Conduct a Team Launch?

 Teams need to establish their working


relationships, determine member roles and
agree on goals.

 Defining the roles and agreeing on how will


handle each role is an essential first step in
team formation.

 The instructor makes the initial role assignments,


but in subsequent development cycles you
may be asked for a role preference.
 Goal setting is an essential step in team
formation and should usually be done at the
start of every project.

 Goals establish the framework for the strategy


and the plan.

 With agreed-on goals, you have the basis for


evaluating strategies and settling issues.

 Without defined goals, there is no orderly way


to settle arguments, negotiate strategies or
plan the work.
Goal-Setting Considerations
 Primary objective of most projects is to attain
superior performance, something that is most
likely when people strive to meet challenging
goals.

 Set specific and measured goals and then work


to meet them.

 Teams should not be measured on whether or


not they actually meet their goals, but they
should be evaluated on their willingness to set
measurable and aggressive goals and on their
efforts to meet the objectives as well.
Setting Team Goals
 It is not easy to establish goals.

 Thisis because effective teamwork requires


that you have goals to guide your work,
TSP starts by defining standard team goals.

 When you have data and want to modify


the goals, you should follow five goal-
setting steps.
Five Goal-Setting Steps
1. Write down the goals you wish to use
instead
2. Specify how to measure these goals
3. Describe why you have selected these
goals instead of the ones provided by the
TSP
4. Give a copy of your revised goals to the
team and to the instructor
5. Have the team leader put a copy of your
goals in the project notebook.
Goal Setting for TSP
 The general guideline for setting goals is to
first consider what would be a superior
result in the eyes of your customer. In this
case, the instructor is your customer.

 For TSP, there are three basic goals:

 Team Goal 1: Produce a quality product


 Team Goal 2: Run a productive and well-managed project
 Team Goal 3: Finish on time
Goal Setting for TSP … cont
 If basic goals are added with concrete measurements will
produce clear goals:

 Team goal 1: Produce quality product


 Percent of defects found before 1st compile: 80%
 Number of defects found in system test: 0
 Requirements functions included at project completion: 100%

 Team goal 2: Run a productive and well-managed project


 Error in estimated product size: < 20%
 Error in estimated development hours: < 20%
 Percent of data recorded and entered in project notebook: 100%

 Team goal 3: Finish on time


 Days early or late in completing the development cycle: <4
Team Member Goals
 All team members need specific and
measurable goals.

 The first goal is to work cooperatively with the


entire team.

 The team’s success depends on all team


members contributing their personal best
efforts, supporting other team members and
working cooperatively to resolve issues and
disagreements.
Team Member Goals … cont
 Examples of team member goals:

 Be a cooperative and effective team


member
 Average PEER eval. for helpfulness and support: >
3
 Average PEER eval. for overall contribution: > 3

 Produce quality products


 Defect density at compile: < 10/KLOC
 Defect density at test: < 5/KLOC
 Defects found after unit test: 0
 In addition to the team member goals,
you will have goals for the role you are
assigned.

 Although the goals of each individual role


are important, it is also important to
remember that each role represents a
single facet of the overall team’s activities
Team Leader Goals
Goal 1 Build and maintain an effective team

Motivate all team members to work aggressively on


Goal 2
the project

Goal 3 Resolve all the issues team members bring to you

Keep the instructor fully informed about the team’s


Goal 4
progress

Perform effectively as the team’s meeting


Goal 5
facilitator
Development Manager Goals

Goal 1 Produce a superior product

Goal 2 Fully use the team member’s skills and abilities


Quality/Process Manager
Goals

All team members accurately report and properly


Goal 1
use TSP process data

The team faithfully follows the TSP and produces a


Goal 2
quality data

All team inspections are properly moderated and


Goal 3
reported

All team meetings are accurately reported and the


Goal 4
reports are put in the project notebook
Support Manager Goals

The team has suitable tools and methods to


Goal 1
support its work

No unauthorized changes are made to baseline


Goal 2
products

All the team’s risks and issues are recorded in the


Goal 3
issue-tracking system and reported each week

The team meets its reuse goals for the


Goal 4
development cycle
The TSP Launch Scripts

 TSP launch scripts provide essential


guidance to properly complete the
launch process.

 To start teams on a development cycle.


The TSP Launch Scripts

Entry Criteria:

 All the students have revise and understood


the PSP concepts.
The TSP Launch Scripts

Step 1: Course Overview

 The instructor describes the TSP team course


objectives:
 What the students are expected to accomplish.
 How their work will be graded and evaluated.
 The basic principles of teamwork.
 The TSP process.
The TSP Launch Scripts

Step 2: Student Information

 The instructor explains the criteria for making


team projects:
 The information needed to make proper
project.
 The team roles, responsibilities and
qualifications.
 Read books, materials, references on the roles
that interest the students.
The TSP Launch Scripts

Step 3: Product Objectives

 The instructor describes the product to be


built:
 TSP Cycle 1 Team Launch
 TSP Cycle n Team Launch
 TSP Student Information Sheet
 TSP Student Information Sheet Instructions
Form Info
The TSP Launch Scripts

Step 4: Team Assignments

 The instructor makes the team and role


assignments.
 As teams develop effective working
relationships, they get more efficient and the
work is more fun.
 Generally, when teamwork problems become
serious, changes should be made
immediately, even in the middle of a cycle.
The TSP Launch Scripts

Step 5: Team Goals

 The instructor reviews the goal setting process


and the TSP goals:
 Why goals are needed and typical team
and role goals.
The TSP Launch Scripts

Step 6: Team Meetings

 The instructor explains the team meeting, its


purpose, and conduct:
 The meeting purpose, scheduling and
reporting.
 Weekly data requirements.
The TSP Launch Scripts
Step 7: The First Team Meeting

 The team leader holds the first meeting of


his/her team:
 Discusses the team members’ roles.
 Discusses and agrees on Cycle 1 goals.
 Establishes a standard time for the weekly
team meeting.
 Agrees on a specific time each week when
all team members will provide their weekly
data to the planning manager.
The TSP Launch Scripts

Step 8: Data Requirements

 The planning manager reviews for the team:


 Data required from every team member
every week.
 Reports to be generated and provided the
team from these data.
The TSP Launch Scripts

Step 9: Project Start

 The launch process has been completed and


the team is ready to start on the project.
The TSP Launch Scripts

Exit Criteria:

 Each student has completed and submitted any


required form.
 The development teams are formed and roles
assigned.
 The instructor has described the overall product
objectives.
 The instructor has reviewed and discussed the TSP
and the team’s and role goals.
 The team has agreed on cycle 1 goals, weekly
meeting times, and the weekly data to report.
The Project Notebook

 TSPcalls for teams to establish and


maintain a project notebook.

 The project leader is responsible for


establishing and maintaining the project
notebook and all team members are
responsible for providing the needed
materials for the notebook.
TSP Support Tool

 The TSP has a support tool to assist your


planning, data entry and tracking work.

 If you use this tool to record the data on all


your activities, it will automatically complete
the project summary forms for you.

 To do this, however, you must be sure to enter


all the (plan and actual) time, size and defect
data for everything you do.

You might also like