Team Software Process

1
Team Software Process
CSEM01 SE Evolution ManagementAnne
ComerHelen Edwards
2
Objectives

• To describe the Team Software Process
• To place the TSP within the SEIs CMMI programme
• To overview Software Process Improvement -
  under CMMI - and show the position of Software
  Measurement in the TSP.

3
Topics covered

• The CMMI, TSP and PSP relationship
• TSP activities
• TSP - using the TSP (iteration)
• TSP -launch and relaunch

4
The SEI process maturity model

5
SEI CMMI model

• It focuses on project management, process, and
  product development.
• It incorporates risk analysis as a management
  acitivity.
• It integrates initiatives in the areas of team,
  and personal, management ( CMM-I ).

6
The TSP
Capability MaturityModel - Integrated
Team SoftwareProcess
Personal SoftwareProcess
7
TSP activities

• Leading the Team
• Communication
• Maintaining the Plan
• Rebalancing Team Workload
• Relaunching the Project and Team
• Quality Management

8
Leading the Team

• Daily direction of the work and the team, and
  regular communication with the Customer, and
  senior management.
• Maintaining the process discipline the agreed
  process.
• Problem (issue) identification, tracking and
  management.

9
Communication

• Within the Team
• With the Customer
• With senior management
• Weekly team meetings
• Factual reporting

10
Maintaining the Plan

• Teams create the plan at the start of their
  phase.
• The plan guides the work, is the yardstick for
  measuring progress, and for identifying problems
  for the schedule.
• Progress is tracked, weekly, against earned value
  (task hours x 100)/project hours.
• Doesnt address dependencies or priorities.

11
Rebalancing Team Workload

• Many tasks take longer, or shorter, than planned.
• Unbalanced workload is inefficient.
• Should review the plan, at the weekly meeting, to
  rebalance the workload.
• Team members individual plans are essential
  input to this activity.
• When a plan stops helping the team relaunch the
  project, and team.

12
Using the TSP Structure
13
Relaunching the Project and Team

• The TSP breaks projects into phases.
• Teams restructure and relaunch at each phase or
  when the plan no longer helps.
• A team launch/relaunch is nine meetings over four
  days
• Objectives
• a common view of the work the approach to it,
• a detailed plan to guide the work,
• senior management support for the plan

14
Meetings

1. Product requirements - question, review, define.
2. Team goals, structure and roles for the phase
   ahead.
3. Development strategy - including process and
   products.
4. Team plan - estimating size of products,
   schedule, availabilities - through to completion.
5. Quality Plan - measuring quality via defects
   found and fixed.
6. Individual plans - development, comparison,
   balancing.
7. Risk Identification assessment, management
   (mitigation, contingency planning,
   documentation, tracking)
8. Management Presentation Development
9. Presentation to Management -for approval.

15
TSP measurement

• Quantitative process data.
• Consolidates individual data into team data.
• Data by product, phase, task, week, defects.
• Storing data to build a historical database.
• Analysing data, to improve planning, management
  and quality.
• Size, time, start/finish dates, defects.

16
Key points

• Software processes are the activities involved in
  producing and evolving a software system - models
  are abstract representations of these processes.
• The SEIs CMMI programme integrates a Capability
  Maturity Model, a Team Software Process, and a
  Personal Software Process.
• All are interlinked you cannot conform to CMMI
  without the other two, you cannot achieve a TSP
  without PSP - trained people.

17
Key points

• TSP focuses on planning, management, quality,
  factual communication, balanced workload, and
  iteration.
• Teams restructure and relaunch at each phase or
  when the plan no longer helps.
• The launch/relaunch is structured, and detailed,
  arriving at a common view of the work the
  approach to it.
• Measurement can be used to answer specific
  questions about the project and product.