CSTE第三章的内容
第3章Managing the Test Project
This chapter is divided into four parts:
1) Test Administration: What is needed to be available to test?
2) Test Supervision: Direction and oversight of test tasks
3) Test Leadership: 1/2 manager 1/2 leader
4) Managing Changes: Plans, CM
Test Administration:
Test project administration include four tasks: Plan, Schedule, Budget and Process
1) Test Plan:
For test planning is a major component of software testing and it is covered in next chapter, I will
discuss this task in next phase.
2) Schedule: A WBS helps to define the activities. Normally, Project Manager use WBS to define
theproject plan and assign tasks to team members.
Following are some advantages:
a. Identify roles and tasks
b. facilitates tracking
c. help management to take corrective action
Following are some points:
a. A WBS is define the total project, not only for testing
b. It is created during the proposal stage.
c. This is a misconception that WBS should be broken down to the smallest level.
3) Budget: There is no one correct way for budgeting. You can use judgment and experience, maybe
automated estimating tools.
a. Some factors influence estimation: requirements, past data, culture, experience, resources
andtools
b. The objective of testing is to achieve a testing goal, so we need to define SMART goals.
Specific - Clear to each team members
Measurable - % complete
Agree upon - All stakeholders should agree these goals
Realistic - resources, time and knowledge
Time Frame – enough time to achieve the goal
c. Budgeting techniques:
1. Top-Down Estimation: based on similar projects and used at the initial stages of the project.
The size is a primary factor when estimate cost:
A. Cost Models - LOC
B. Constraint Models – SLIM Model (software lifecycle model)
C. FP
D. COCOMOII Model
2. Expert Judgment: Just experience….
3. Bottom-Up Estimation: only be used after WBS be defined and scope is clear.
4) Test Process: Customization of the test process
a. Release cycle: yours VS mine, new VS exist
b. Development methodology: Unix, .Net, offshore..
c. User schedules: Delivery date, important date
d. PSR
e. Interfacing with other projects: you need to consider the influence of other projects
f. Interfacing with enterprise-wide databases
g. Naming convention: change the name of project.
－－－－－－－－－－－－－－－－－－－－－－－－
总结：测试项目管理包括4个主要任务：测试计划，时间，预算和测试流程。时间主要是依据WBS，这也是项目管理要的；预算主要介绍了Estimation，有一些因素是我们做estimation时候需要考虑的，这里还包括我们在项目开始需要定义个测试的目标（SMART Goal），最后还介绍了一些做预算的或者叫估计的技术（我觉得其实很多方法在我们实际做估计的过程中没有用到或者是不了解如何使用，更多的还是靠的experience。。）；最后是根据项目情况来自定义测试流程，列举了一些自定义测试流程所需要的影响。
