TMP3413

Software
Engineering Lab

Lecture 05:
The Development
Plan
 Why Make Plans?

Can work more efficiently know what to do and

when to do the tasks

More likely to meet the commitments and

perform better work

Can increase or reduce the amount of work we

plan to do
 Balanced Plans
A plan is balanced when all the engineers
complete their planned tasks in the proper
order and at roughly the same time.

 With a balanced plan, no one needs to

wait for anyone else and everyone is fully
utilized.
A detailed plan helps us to track and
manage our work.

 With TSP, the principal project-tracking

measures are planned value (PV) and
earned value (EV). These measures provide
a way to determine the schedule
contribution of each task.
Tracking Progress Against the Plan …
cont

Planned Value Earned Value

(PV) (EV)
o The approved value o The value of the work
of the work to be actually completed to
completed in a given date.
time period.
o E.g: The value of the
o E.g: The money that project that you have
you should have spent earned so far.
as per the schedule.
 Tracking Progress Against the Plan …
cont

 Table 5.1 shows the planned-value

calculations for cycle 1 of a project to
develop the change counter software tool
(to count program size).

 Bytracking earned value against planned

value, we can see where we are on a
project. This knowledge helps us to manage
our work precisely and also helps us to meet
the schedule.
 Estimating Level
 With the TSP, engineers estimate programs
by first identifying the objects of functions
they contain and then estimating the sizes
of these objects and functions.

 Forthe programs developed for this course,

there are typically only three levels:
1. the system,
2. the modules or system components, and
3. the module’s objects or functions.
 The TSP Planning Process … cont
1. In the strategy phase, as described in
Lecture 4, we produced the conceptual
design. We will use this conceptual design
throughout the planning process.

2. During the strategy phase, we estimated

the sizes of the various parts of the
conceptual design, decided which parts to
develop in each cycle and entered the
information on the STRAT form.
 The TSP Planning Process … cont
3. Now, during the planning phase, we enter on
the SUMS form the names and estimated sizes
of the components we will develop in cycle 1.
We also identify any other products we will
need to develop for cycle 1, such as test plans
or requirements specifications and enter these
items and their estimated sizes on the SUMS
form.

4. List the tasks required to build the products

identified in step 3, estimate how long each
task will take and enter this information on the
TASK form.
 The TSP Planning Process … cont
5. Make the quality plan, SUMQ. Again, we use
the TSP support tool to do this.

6. Make copies of the team TASK and SCHEDULE

forms for each engineer and have each
engineer produce personal TASK and
SCHEDULE forms.

7. Use the TSP tool to generate individual TASK

and SCHEDULE forms that show the PV and
completion times for each of our personal
tasks. Every team member should do this.
 The TSP Planning Process … cont
8. With the TASK and SCHEDULE forms for every
engineer, we have the data to balance the
team workload. Do this by identifying those
engineers who will complete tasks later than
desired and reassigning some of their work to
other team members.

9. Use the TSP tool to roll up the individual

engineer plans to produce the final team
plan. Also generate final copies of the team
and engineer TASK and SCHEDULE form as
well as copies of the SUMP and SUMQ forms
for the total project.
Entry Criteria

 The team has a development strategy

and conceptual design.
The Development Plan Scripts
… cont
Step 1: Planning Overview

 The instructor describes the planning

process.
 The task and schedule plans and how they
are produced.
 The quality plan and how it is produced.
The Development Plan Scripts
… cont
Step 2: Enter the Size Estimates in Form STRAT

 Starting
with the conceptual design and
STRAT form produced in the strategy
phase, the planning manager leads the
team:
 Identifying any other products to be
produced and their size.
 Recording the STRAT form and other size
data in SUMS.
The Development Plan Scripts
… cont
Step 3: Produce the Task Plan

 The planning manager leads the team

through:
 Producing a task list with team and engineer
time estimates.
 Entering these data in the TASK form.
The Development Plan Scripts
… cont
Step 4: Produce the Schedule Plan

 The planning manager obtains the estimated

number of hours each team member plans to
spend on the project each week and;
 Enters the weekly hours in the SCHEDULE form.
 Produces the team TASK and SCHEDULE forms.
 Reworks the plan if the hours are inadequate.
The Development Plan Scripts
… cont
Step 5: Produce the Quality Plan

 The quality/process manager leads the team

through:
 Reviewing the team’s quality objectives.
 Estimating the defects injected and defect-
removal yields.
 Generating and assessing trial SUMP and SUMQ
plans.
 Making needed process adjustments to get a
satisfactory plan.
The Development Plan Scripts
… cont
Step 6: Produce the Individual Engineer Plans

 The planning manager helps the engineer

make personal plans.
 Allocating the tasks among team members.
 Estimating the time to perform each task.
 Entering the data in the TASK and SCHEDULE
forms.
 Producing the planned-value schedule and task
completion dates.
The Development Plan Scripts
… cont
Step 7: Balance Team Workload

 The planning manager leads the team

through:
 Identifying workload imbalances.
 Reallocating tasks to minimize the schedule.
 Producing balanced engineer plans.
 Producing the consolidation team plan
(TASK, SCHEDULE, SUMP, and SUMQ forms).
The Development Plan Scripts
… cont
Exit Criteria

 Completed team and engineer TASK and

SCHEDULE forms.
 Completed SUMP, SUMQ, and SUMS forms.
 Updated project notebook.
TSP Task and Schedule Planning:
TASK & SCHEDULE
Purpose:

 Tocalculate the planned value and how

to determine the dates when you will
complete each task.

 Two forms to complete:

1. TASK form - sample
2. SCHEDULE form - sample
 The Program Plan Summary:
SUMP
Purpose:

 To summarize the teams’ and each engineers’

work.
 Provide overall view of each teams’ results
and are the best reference for assessing a
team’s or engineer’s data.

 One form to complete:

 SUMP form - sample
 The Quality Plan:
SUMQ
Purpose:

 To provide overall picture of the quality of the

teams’ and each engineer’s work.
 Provides the data to determine how faithfully
the engineers are following the TSP process.

 One form to complete:

 SUMQ form - sample
 The Size Summary:
SUMS
Purpose:

 To summarize the data for product size.

 One form to complete:

 SUMS form - sample
 To determine the status and quality of the
work.

 In order to track the work, the students

need the following:
 A defined process or plan to follow.
 A time tracking log or tool for recording the
time.
 Some way to tell time.
 Work to do while tracking their time.
Tracking the Work … cont
Project Tracking Step 1
 Record time in the time recording log
(LOGT).

Project Tracking Step 2

 Enter the week when tasks are
completed.

Project Tracking Step 3

 Generate the TASK and SCHEDULE data.
Project Planning Step 4
 Enter defects in the defect recording log
(LOGD).

Project Planning Step 5

 Enter size by component.

Project Planning Step 6

 Update the SUMP form.

Project Planning Step 7

 Generate the SUMQ form.
 The Time Recording Log:
LOGT
Purpose:

 Forengineers to track all the time they

work on the project and that they properly
report this time against the process phases
and the product component.

 One form to complete:

 LOGT form - sample
 The Defect Recording Log:
LOGD
Purpose:

 Torecord defects in the system in order to

track the quality of the product.

 One form to complete:

 LOGD form - sample