Question

Difference between personal process model and team process model

Answer 1

Personal software process is focussed on individuals to improve their performance.

PSP process consists of methods, forms and tricks to guide software engineers in doing their development work.

Team software process depends on a group of individuals and aimed at improving the performance of the team.

TSP process consists of programming strategies which will help a software engineering team to build better quality products.

Answer 2

Answer -:Planning. This activity isolates requirements and develops both size and resource estimates.

In addition, a defect estimate is made. All metrics are recorded on worksheets or templates.

Finally, development tasks are identified and a project schedule is created.

High-level design. External specifications for each component to be constructed are

developed and a component design is created. Prototypes are built when uncertainty exists.

All issues are recorded and tracked.

High-level design review. Formal verification methods (Chapter 21) are applied to uncover

errors in the design. Metrics are maintained for all important tasks and work results.

Development. The component-level design is refined and reviewed. Code is generated,

reviewed, compiled, and tested. Metrics are maintained for all important tasks and work

results.

Postmortem. Using the measures and metrics collected, the effectiveness of the process is

determined. Measures and metrics should provide guidance for modifying the process to

improve its effectiveness.

2. Team Software Process (TSP): The goal of TSP is to build a ―self directed‖ project team

that organizes itself to produce high-quality software. TSP objectives are,

• Build self-directed teams that plan and track their work, establish goals, and own their

processes and plans. These can be pure software teams or integrated product teams (IPTs)

of 3 to about 20 engineers.

• Show managers how to coach and motivate their teams and how to help them sustain peak

performance.

• Accelerate software process improvement by making CMM23 Level 5 behavior normal and

expected.

• Provide improvement guidance to high-maturity organizations.

• Facilitate university teaching of industrial-grade team skills.