Lecture Software process improvement: Lesson 26 provide students with knowledge about: TSP body of knowledge; competency area; knowledge area; TSP BOK competence areas; TSP foundations and fundamentals; team foundations; project planning with TSP;... Please refer to the detailed content of the lecture!
TSP Body of Knowledge Lecture # 26 11 TSP Body of Knowledge • SEI has drafted the Team Software Process Body of Knowledge (TSP BOK) document, which defines the fundamental knowledge and skills that set TSPtrained individuals apart from other software professionals 22 TSP Body of Knowledge • It helps individual practitioners to assess and improve their own skills, provides employers with an objective baseline for assessing the process improvement skills and capabilities of their development team members, and guides academic institutions that want to incorporate TSP into their software engineering curriculum 33 TSP Body of Knowledge • The TSP body of knowledge is composed of six competency areas, each with several knowledge areas • We’ll talk about these in a little while, but let’s talk about some basic terminologies associated with the body of knowledge 44 Competency Area • A competence area is a group of closely related knowledge areas that a practitioner is well qualified to perform intellectually or physically 55 Knowledge Area • A knowledge area is the sum or range of specific understanding and ability gained through study of a set of concepts or through experience with a set of skills 66 Concept • An explanatory principle applicable to a specific instance or occurrence within a particular knowledge area 77 Skill • Proficiency, facility, or dexterity of performance that is acquired or developed through training or experience in a particular knowledge area 88 Following slide to be inserted TSP BOK Competence Areas 99 TSP BOK Competence Areas • • • • TSP Foundations and Fundamentals Team Foundations Project Planning with TSP Project Implementation and Tracking with TSP • Gathering and Using TSP Data • Scaling Up the TSP 10 10 Gathering and Analyzing Postmortem Data • This knowledge area discusses the types of data that are gathered and analyzed, identifies the various team member responsibilities for gathering and preparing data for the postmortem, explains how data are used in the postmortem meeting to identify strengths and areas for improvement, and lists the data that should be captured in the postmortem report 67 67 Scaling Up the TSP 68 68 Scaling Up the TSP • Successful introduction of TSP into an organization begins with one or two small scale pilot projects • Pilot projects provide the management support and compelling evidence needed to convince the organization’s general population that the TSP methods are effective and will be beneficial to the organization 69 69 Scaling Up the TSP • If the pilot projects are successful, management often decides to implement TSP in one or more divisions or organizations • As with the introduction of the pilot projects, special considerations must be addressed to increase the likelihood that organizationwide implementation will be successful 70 70 Scaling Up the TSP • Whether or not organizations choose to implement TSP throughout the company, they all have unique needs that may require some tailoring of the TSP applications 71 71 Scaling Up the TSP • This is particularly true if the TSP project team requires more 15 to 20 members, if the members of the team have different professional capabilities or specialties that must work together to produce the product, or if some of the team members work at locations apart from most of the team 72 72 Scaling Up the TSP • The knowledge areas in this competency area describe the activities of scaling up the TSP for entire organizations or very large TSP project teams, and the adaptations to the basic TSP process that may be needed to address the needs of specialized TSP teams 73 73 Scaling Up the TSP • Knowledge areas in this competence area are – Organizational Implementation – TSP Process Variations – Largescale TSP Teams 74 74 Organizational Implementation • This knowledge area describes the process of scaling the TSP implementation up from use on a few pilot projects to full introduction of TSP across the organization 75 75 TSP Process Variations • In development work, teams typically are classified as either project teams or functional teams • A project team is one that is formed to accomplish a specific project objective and, when that objective has been completed, the team is either disbanded or given another project assignment 76 76 TSP Process Variations • A functional team is one that has a continuing mission responsibility • Additional variations in team type are due to team size or physical location 77 77 TSP Process Variations • TSP can be adapted to fit the needs of functional teams (TSPf), integrated project teams (TSPI), distributed teams (TSPd), multiple TSP teams working in tandem (TSPm), TSP teams that also use CMMI (TSP+), and academic (student) teams (TSPi) 78 78 Largescale TSP Teams • This knowledge area describes the characteristics and considerations unique to largescale TSP teams 79 79 Summary 80 80 References • TSP BOK, SEI, July 2010 81 81 ... principles underlying the Team? ?Software? ? Process • The key concepts identify the elements that are common to and required for successful outcomes of work done by teams to produce software? ?products and/or? ?software? ?intensive ... SEI has drafted the Team? ?Software? ?Process? ? Body of Knowledge (TSP BOK) document, which defines the fundamental knowledge and skills that set TSPtrained individuals apart from other? ?software? ?professionals... TSP? ?Process? ?Elements and Measures • This knowledge area describes the? ?process? ? elements and measures that are used in the TSP. (Where applicable, overlaps with or differences from PSP? ?process? ?elements and