Lecture Software process improvement: Lesson 25 provide students with knowledge about: introduction to team software process (TSP); The TSP teamworking process; management reporting; maintaining the plan; estimating project completion; rebalancing team workload; relaunching the project; TSP quality management;... Please refer to the detailed content of the lecture!
Introduction to TSP – III Lecture # 25 11 The TSP Teamworking Process 22 Continues on next slide The TSP Teamworking Process • Once the TSP team is launched, the principal need is to ensure that all team members follow the plan. This includes the following major topics • Leading the team • Process discipline • Tracking issues • Communication 33 The TSP Teamworking Process • • • • • • Management reporting Maintaining the plan Estimating project completion Rebalancing team workload Relaunching the project TSP quality management 44 Leading the Team • The team leader is responsible for guiding and motivating the team members, handling customer issues, and dealing with management • This includes the daytoday direction of the work, protecting team resources, resolving team issues, conducting team meetings, and reporting on the work 55 • The team leader’s principal responsibility is to maintain the team’s motivation and energy and to ensure that it is fully effective in doing its work 66 • Productive teamwork requires a combination of specific goals, a supportive working environment, and capable coaching and leadership. The project goal is to build a working product • TSP provides the supportive environment, one of your team members will be the team leader, and the instructor provides the coaching 77 • When you have struggled with actual project problems and have been guided to effective solutions, you will appreciate the benefits of sound development practices. Without the precise guidance of the TSP, however, you could waste considerable time in defining your own practices, methods, and roles 88 • Instruction is most effective when it builds on the available body of prior knowledge. There has been a great deal of experience with software teams and software team courses. TSP builds on this foundation 99 Process Discipline • One key leadership responsibility is maintaining process discipline. Here, the team leader ensures that the engineers do the job the way they had planned to do it • Almost every project faces heavy schedule and resource pressure, so there is always a temptation to cut corners 10 10 Managing Risks 1 • Too large a product – Start with a small kernel product and then add functions in later development cycles • Difficult or complex functions – Prototype these functions at the beginning of the project, when you have time to consider alternatives 33 33 Managing Risks 2 • Support system problems – Build an early prototype or small product version to make sure that you know how the support system works • Testing time – If you consistently follow the TSP and use disciplined PSP methods, your product will have few defects and testing will not be a problem 34 34 Managing Risks 3 • Product control – It is easy for teams to lose control of their products. This is why TSP addresses configuration management at the beginning of the project • Teamwork problems – If your team is having trouble working together, discuss the problems openly to see whether you can resolve them. If the problems 35 35 persist, get help from the instructor A Reuse Strategy 36 36 The Development Plan 37 37 The Development Plan • • • • • • • Why make plans? Balanced plans Tracking progress against the plan Planning in detail Handling unplanned tasks Estimating level Implementation planning 38 38 Design Process 39 39 The TSP Design Decisions 1 • Provide a simple framework that builds on the foundation of the Personal Software Process (PSP) • Develop products in several cycles • Establish standard measures for quality and performance • Provide precise measures for teams and students 40 40 The TSP Design Decisions 2 • Use role and team evaluations • Require process discipline • Provide guidance on teamwork 41 41 Implementation Process 42 42 Testing Process 43 43 The Postmortem 44 44 The Postmortem • Why we need a postmortem • What a postmortem can do for you • The process improvement proposal 45 45 Summary 46 46 References • SEI website: www.sei.cmu.edu • Introduction to the Team Software Process by Watts Humphrey (Chapters Ch 12, 3.1 3.4, 4.14.5,5.1, 10.110.3) • The Team Software Process by Watts Humphrey, SEI Technical Report 0023, November 2000 47 47 ... Run a productive and wellmanaged project • Finish on time 25 25 TSP? ?Process • • • • • • • Launching a team project (already discussed) Development strategy Development plan Design? ?process Implementation? ?process Test plan Postmortem ... There has been a great deal of experience with? ?software? ?teams and? ?software? ?team courses. TSP builds on this foundation 99 Process? ?Discipline • One key leadership responsibility is maintaining? ?process? ?discipline. Here, the ... Implementation planning 38 38 Design? ?Process 39 39 The TSP Design Decisions 1 • Provide a simple framework that builds on the foundation of the Personal? ?Software? ? Process? ?(PSP) • Develop products in several cycles