π Lecture 23 β Introduction to TSP β I
π Overview: This lecture introduces the Team Software Process (TSP), a framework for guiding software engineering teams to achieve extraordinary work. It begins by examining why projects fail, primarily due to people problems rather than technical issues, and explores different team paradigms and the factors that create toxic team environments. The lecture then defines what a team truly is, emphasizing the importance of roles, interdependence, and social support, and concludes by outlining the characteristics of effective teams that TSP aims to foster.
ποΈ Topics Covered
This lecture covers the reasons for project failure, which are seldom technical but often related to people problems and excessive schedule pressure. It then introduces four organizational paradigms for software engineering teams: Closed, Random, Open, and Synchronous. The concept of a "jelled team" is introduced, followed by a discussion of factors that foster a toxic team environment. The lecture then formally introduces the Team Software Process (TSP), its objectives, and its origin at the SEI. The conditions for teamwork are explored through a formal definition of a team, highlighting the necessity of roles and interdependence. Finally, the lecture details the characteristics of effective teams, with a special focus on innovation and the importance of a trusting environment.
π Lecture Summary
Why Projects Fail
Projects seldom fail due to technical reasons. The primary causes are people problems and excessive schedule pressure. The solution lies in fostering good communication, building good teams, and managing pressure effectively. The best team structure depends on the organizationβs management style, the number of people, their skill levels, and the overall problem difficulty. The performance of a team is inversely proportional to the amount of communication that must be conducted, and the length of time the team βlives togetherβ affects team morale.
π Definition β People Problems: Issues related to team dynamics, communication, and morale that are the primary cause of project failure, rather than technical hurdles.
Constantine suggests four organizational paradigms for software engineering teams.
Closed Paradigm
A closed paradigm structures a team along a traditional hierarchy of authority. Such teams can work well when producing software that is quite similar to past efforts, but they will be less likely to be innovative.
Random Paradigm
The random paradigm structures a team loosely and depends on the individual initiative of the team members. When innovation or technological breakthrough is required, teams following the random paradigm will excel. However, such teams may struggle when βorderly performanceβ is required.
Open Paradigm
The open paradigm attempts to structure a team to achieve some of the controls of the closed paradigm but also much of the innovation of the random paradigm. Work is performed collaboratively, with heavy communication and consensus-based decision making. Open paradigm teams are well suited to solving complex problems but may not perform as efficiently as other teams.
Synchronous Paradigm
The synchronous paradigm relies on the natural compartmentalization of a problem and organizes team members to work on pieces of the problem with little active communication. To achieve a high-performance team, team members must have trust, the distribution of skills must be appropriate, and mavericks may have to be excluded to maintain cohesiveness.
π Definition β Jelled Team: A group of people so strongly knit that the whole is greater than the sum of the parts. Once a team begins to jell, the probability of success goes way up, and the team can become unstoppable.
Factors that Foster Toxic Team Environment
Several factors can create a toxic team environment. These include a frenzied work atmosphere where team members waste energy and lose focus. High frustration caused by personal, business, or technological factors causes friction. Fragmented or poorly coordinated procedures or a poorly defined process model can become a roadblock. An unclear definition of roles leads to a lack of accountability and finger-pointing. Finally, continuous and repeated exposure to failure leads to a loss of confidence and lower morale.
Team Software Process (TSP)
The Team Software Process (TSP) is an important step in software process improvement, developed after CMM and PSP at the Software Engineering Institute (SEI). The TSP provides a disciplined context for engineering work. The principal motivator for TSP was the conviction that engineering teams can do extraordinary work, but only if they are properly formed, trained, staffed, and led. The objective of TSP is to build and guide such teams. While some small products can be developed by individuals, the scale and complexity of modern systems requires teamwork. The effectiveness of the team largely determines the quality of the engineering.
π‘ Why this matters: Unlike PSP which focuses on individual discipline, TSP scales these principles to a team level, providing a structured way to manage the complexities of collaborative software development.
Conditions for Teamwork
What is a Team?
A team is a group of people who share a common goal, are committed to it, and have a common working framework. The formal definition of a team includes four key parts:
- A team consists of at least two people.
- The members are working toward a common goal.
- Each person has a specific assigned role.
- Completion of the mission requires some form of dependency (interdependence) among the group members.
Team
All four parts of the definition are important. Roles provide a sense of ownership and belonging, guide team members on how to do their jobs, prevent conflicts and wasted effort, and provide members with a degree of control over their working environment. This sense of control is a fundamental requirement for motivated team members.
Interdependence
Interdependence means that each team member depends to some degree on the performance of the other members. It improves individual performance because members can help and support each other, such as in design teams.
π Definition β Interdependence: A condition where team members rely on each otherβs performance to achieve a common goal, fostering collaboration and support.
Social Support of Membership
Team performance is enhanced by the social support of membership. Because of the social context, members will generally make a special effort to meet their obligations to the rest of the team. Through mutual support and interdependence, teams become more than just the sum of their individual members. To be effective, teams must be properly skilled and work as cohesive units.
Characteristics of Effective Teams
Effective teams have several common characteristics. The members are skilled. The teamβs goal is important, defined, visible, and realistic. The teamβs resources are adequate for the job. The members are motivated and committed to meeting the goal. The members cooperate and support each other. The members are disciplined in their work. Finally, the members are innovative.
Innovation
Innovation is more than just thinking up ideas; it requires creativity and hard work. Innovative teams must have skilled, capable, and highly motivated people who are creative, flexible, and disciplined. They must strive to meet demanding schedules while controlling costs and informing management of their progress. To be innovative, engineering teams must work in a trusting and supportive environment. When managers do not trust their teams, engineers feel antagonized and lose their commitment. While it is appropriate for management to challenge teams with aggressive goals, they must be willing to negotiate realistic commitments that engineers believe they can meet. Few people will work diligently to meet a seemingly hopeless schedule. The TSP is designed to establish the conditions that characterize effective teams.
β Key Takeaways
Project failure is almost always due to people problems, not technical ones, and can be mitigated by building effective teams. Effective teams work within a defined paradigm (Closed, Random, Open, or Synchronous), each suited to different types of tasks, and avoid the factors that create a toxic environment. The Team Software Process (TSP) is a disciplined framework from the SEI designed to form, guide, and lead high-performance engineering teams. A true team is defined by common goals, assigned roles, and member interdependence, which together foster ownership, social support, and enhanced performance. Finally, for an engineering team to be innovative and effective, it must operate in a trusting environment with challenging but realistic goals and schedules.
π§ Quick Revision Questions
- What are the primary reasons projects fail, according to this lecture?
- Name and briefly describe the four organizational paradigms for software engineering teams suggested by Constantine.
- What is a "jelled team," and what is its significance?
- List the four key parts of the formal definition of a "team" as presented in this lecture.
- According to the lecture, what is the principal motivator for the development of the Team Software Process (TSP)?
π Lecture 24 β Introduction to TSP β II
π Overview: This lecture continues the introduction to the Team Software Process (TSP), focusing on the principles of teambuilding and the operational processes needed for effective teamwork. It explains the TSP launch process in detail, covering how teams form, plan, and commit to a project, and it ties together the CMM/CMMI, PSP, and TSP for cohesive process improvement.
ποΈ Topics Covered
The lecture covers TSP teambuilding principles, the importance of defined operational processes, the principle elements of TSP including PSP and CMM/CMMI, the integration of these methods, and the detailed nine-meeting TSP launch process that guides teams from goal setting through to management review and postmortem.
π Lecture Summary
Teambuilding
The lecture begins by outlining the teambuilding principles used in the TSP to establish conditions for effective teams. These principles include establishing common goals and defined roles, developing an agreed-upon strategy, and defining a common process for work. All team members participate in producing the plan and know their personal role. The team negotiates the plan with management, who then reviews and accepts it. Team members do the job as planned, communicate freely, and form a cohesive, cooperative group committed to meeting the goal. Effective team formation requires that members truly understand their tasks, agree on how to do the job, and believe their plan is achievable. These conditions are established by involving engineers in producing their own plans. The TSP provides explicit guidance that organizations need to build effective engineering teams.
Team Operational Processes
To do disciplined work, engineers need what Deming calls operational processes. These are processes that define precisely how the work is to be done, more like a script designed for team members to use. The TSP provides a defined operational process to guide engineers and managers through the team-building steps. Without specific guidance, engineers must work out team-building details themselves, which wastes time and often produces poorly functioning teams. With a defined process and plan, engineers can be highly efficient. The TSP provides the operational processes needed to form engineering teams, establish an effective team environment, and guide teams in doing the work.
Principle Elements of TSP
Before team members can participate on a TSP team, they must know how to do disciplined work. Training in the Personal Software Process (PSP) is required to provide engineers with the knowledge and skills to use the TSP. PSP training includes making detailed plans, gathering and using process data, developing earned value plans, tracking projects, measuring quality, and defining operational processes. Engineers must be trained in these skills before they can follow the TSP process. The Capability Maturity Model (CMM) or Capability Maturity Model Integration (CMMI) provides the overall improvement framework, while the PSP provides the engineering disciplines needed for using a defined, planned, and measured process.
π‘ Why this matters: The TSP is not a standalone method; it requires the foundation of PSP for individual discipline and CMM/CMMI for organizational maturity.
Tying Process Improvement Efforts
The TSP couples the principles of integrated product teams with the PSP and CMM/CMMI methods to produce effective teams. In essence, the CMM/CMMI and PSP provide the context and skills for effective engineering, while the TSP guides engineers in actually doing the work. Thus, the TSP capitalizes on the preparation provided by the PSP and CMM/CMMI, while also providing explicit guidance on how to do the work.
Back to TSP
While there are many ways to build teams, they all require individuals to work together to accomplish a demanding task. In the TSP, this demanding team-building task is a four-day planning process called the team launch. In a launch, all team members develop the strategy, process, and plan for their project. After completing the launch, the team follows its own defined process to do the job.
TSP Process
The TSP process includes launching a team project, development strategy, development plan, design process, implementation process, test plan, and postmortem.
Launching a Team Project
The process of forming and building a team does not happen by accident and it takes time. Teams need to establish working relationships, determine member roles, and agree on goals. The launch is the first step. Defining roles and agreeing on who will handle each role is an essential first step in team formation. In the TSP launch, teams make an overall plan and a detailed plan for about the next three to four months. After the team members complete the next project phase or cycle, they revise the overall plan if needed and make a new detailed plan.
The TSP Launch Process
Teams generally need professional guidance to properly complete the launch process. This guidance is provided by a trained launch coach who leads the team through the launch process. Unless teams are very experienced, they generally need the support of a trained launch coach.
π Definition β Launch Coach: A trained professional who leads the team through the TSP launch process, providing essential guidance for unique team problems and issues.
The launch consists of nine meetings:
- Meeting 1: The team, team leader, and launch coach meet with senior management and marketing representatives. The objective is to inform all team members about the job, describe management's goals for the team, and convince the team members that management is relying on them.
- Meetings 2 through 8: The team, team leader, and coach meet with no observers or visitors. The team is led through steps designed to produce the conditions for effective teamwork.
- Meeting 2: The team documents its goals and selects team member roles. Standard TSP roles include team leader, customer interface manager, design manager, implementation manager, test manager, planning manager, process manager, quality manager, and support manager.
- Meetings 3 and 4: The team makes the overall project strategy and plan. Engineers produce a conceptual design, devise the development strategy, define the detailed process, and determine support tools. A list of products, along with size and time estimates per step, is generated. A schedule is created from these data.
- Meeting 5: Once they have an overall plan, engineers produce quality goals and plans. This defines quality actions and provides a measurable basis for tracking quality. Team members estimate defects injected and removed in each phase, and how many will remain for system test, acceptance testing, and final delivery.
- Meeting 6: Team members make detailed next-phase plans and review the entire workload to distribute tasks evenly. This results in a balanced team plan.
- Meeting 7: Engineers identify major project risks, rank them for likelihood and impact, assign a member to track each risk, and prepare a mitigation plan for the most significant risks.
- Meeting 8: After the plan is completed, the team prepares for the management review.
- Meeting 9: The team conducts the review with management. The team explains the plan, describes how it was produced, and demonstrates that all members agree and are committed. If the plan does not meet management's objectives, the team should present alternate plans showing what could be done with added resources or changes. The principal reason for showing alternate plans is to provide management with options.
At the end of the TSP launch, the team and management should agree on how to proceed. In the final postmortem step, the team reviews the launch process and submits Process Improvement Proposals (PIPs) on suggested improvements. The team also gathers and files launch data and materials for later use.
π Example: If a team's plan for a software project estimates 6 months and management needs it in 5 months, the team might prepare an alternate plan showing that with two additional developers, the schedule can be met. This gives management a concrete option for decision-making.
β Key Takeaways
The TSP teambuilding principles rely on involving all engineers in planning to ensure commitment, strategy, and role definition. The TSP provides operational processesβscripts that guide engineers step-by-stepβto avoid ad-hoc, inefficient team-building. The TSP launch is a structured nine-meeting process led by a coach, where teams establish goals, create a balanced plan, assess quality, identify risks, and negotiate with management. PSP training is required before engineers can use TSP, and TSP works in conjunction with CMM/CMMI to provide a complete improvement framework. The final postmortem and submission of PIPs are crucial for continuous process improvement.
π§ Quick Revision Questions
- What are the three key conditions for effective team formation according to the TSP teambuilding principles?
- Why is a defined operational process important for engineering teams, and what happens without it?
- What is the purpose of the TSP team launch, and how long does it typically last?
- In which TSP launch meeting is the "balanced team plan" created, and what does it ensure?
- What is the purpose of the postmortem step at the end of the TSP launch process?
π Lecture 25 β Introduction to TSP β III
π Overview: This lecture covers the core TSP team working process, focusing on how a team operates after launch. It details the responsibilities of leadership, process discipline, tracking, communication, and quality management, along with guidance on goal-setting, development strategy, planning, and project postmortems. This lecture is critical for understanding how to maintain a disciplined and effective software team throughout a project.
ποΈ Topics Covered
This lecture addresses the TSP team working process, including leading the team, maintaining process discipline, tracking issues, ensuring communication and feedback, rebalancing workload, and relaunching projects. It also covers TSP quality management, goal-setting (team goals, considerations, and steps), the TSP process itself (including development strategy and risk management), the development plan, key TSP design decisions, and the importance of the postmortem.
π Lecture Summary
The TSP Team working Process
Once the TSP team is launched, the principal need is to ensure all team members follow the plan. This includes leading the team, maintaining process discipline, tracking issues, communication, management reporting, maintaining the plan, estimating project completion, rebalancing team workload, relaunching the project, and TSP quality management.
Leading the Team
The team leader is responsible for guiding and motivating team members, handling customer issues, and dealing with management. This includes day-to-day direction, protecting team resources, resolving team issues, conducting meetings, and reporting on work. The leaderβs principal responsibility is to maintain the teamβs motivation and energy and ensure it is fully effective. Productive teamwork requires a combination of specific goals, a supportive working environment, and capable coaching and leadership. TSP provides the supportive environment, and the instructor provides the coaching. Without the precise guidance of the TSP, a team could waste considerable time defining its own practices, methods, and roles.
Process Discipline
One key leadership responsibility is maintaining process discipline, where the team leader ensures engineers do the job the way they planned to do it. Almost every project faces heavy schedule and resource pressure, so there is always a temptation to cut corners. However, when teams stop following their defined processes, they have no way to tell what they are supposed to do or where they stand on the job.
Tracking Issues
Another important team leader responsibility is ensuring that all issues team members identify are managed and tracked. This includes task hours, earned value status, milestone status, and quality status.
Communication and Feedback
Learning is most effective when you follow a defined process and get rapid feedback. The TSP scripts and forms provide a defined, measured, and repeatable framework for team software engineering. TSP provides rapid performance feedback because the team produces the product in several short development cycles and evaluates results after each cycle. The team leader is responsible for maintaining open and effective team communication. When team members do not know the projectβs status, understand what their teammates are doing, or know what challenges lie ahead, it is hard for them to stay motivated. Communication is a key part of maintaining the teamβs energy and drive.
Rebalancing Team Workload
Unbalanced workload can cause a team to be inefficient. This occurs when some engineers have much more work than others.
Re-launching the Project
In TSP, teams periodically replan their work. This is necessary because it is difficult to make detailed plans that run for more than a few months. The relaunch is generally scheduled as part of the project and conducted whenever the team feels it would be helpful.
TSP Quality Management
To manage quality, teams must establish quality measures, set quality goals, establish plans to meet these goals, measure progress against the plans, and take remedial action when goals are not met. The elements of TSP quality management are making a quality plan, identifying quality problems, and finding and preventing quality problems.
TSP Goals and Goal-Setting
Goal setting is an essential step in team formation and should usually be done at the start of each project. Establishing goals is simple in concept but often difficult in practice. Goals should be precisely measured.
Goal-Setting Considerations: Teams should not be measured on whether or not they actually meet their goals. Instead, they should be evaluated on their willingness to set measurable and aggressive goals and on their efforts to meet them. Too much emphasis on meeting goals is counterproductive because it motivates teams to set goals they are sure they can meet.
Goal-Setting Steps:
- Write down the goals you wish to use instead.
- Specify how to measure these goals.
- Describe why you have selected these goals instead of the ones provided by the TSP.
- Give a copy of your revised goals to the team and to the instructor.
- Have a team leader put a copy of your goals in the project notebook.
Goal Setting for TSP: The primary goals are to produce a quality product, run a productive and well-managed project, and finish on time.
TSP Process
This includes launching a team project, development strategy, development plan, design process, implementation process, test plan, and postmortem.
The Development Strategy
One principal problem in software development is figuring out how to build big systems. The steps in developing a strategy are:
- Define the strategy criteria.
- Determine the possible alternative strategies.
- Identify the risks and benefits of each alternative strategy.
- Make a comparative evaluation of these alternatives.
- Make the strategic decision.
- Document the selected strategy.
To develop a strategy, ask four questions:
- Based on what I know, how would I build this product?
- What are the principal components I will need to build this product?
- What functions must these components provide?
- How big do I think these components will be?
Some Risks: You may encounter functions you donβt know how to design, run into support system problems, have a product too defective for testing, lose control of the product, or have a team that cannot work effectively.
Managing Risks:
- Too large a product: Start with a small kernel product and add functions in later cycles.
- Difficult or complex functions: Prototype these functions at the beginning of the project.
- Support system problems: Build an early prototype to ensure you know how the system works.
- Testing time: If you consistently follow TSP and PSP methods, your product will have few defects.
- Product control: TSP addresses configuration management at the beginning of the project.
- Teamwork problems: Discuss problems openly; if they persist, get help from the instructor.
The Development Plan
This section covers why to make plans, creating balanced plans, tracking progress against the plan, planning in detail, handling unplanned tasks, estimating levels, and implementation planning.
The TSP Design Decisions
TSP design decisions are to 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, use role and team evaluations, require process discipline, and provide guidance on teamwork.
The Postmortem
The postmortem is a critical part of the process. It addresses why we need a postmortem, what a postmortem can do for you, and the process improvement proposal.
β Key Takeaways
The most critical points from this lecture are that a successful TSP team requires a leader who actively maintains motivation, process discipline, and open communication. Effective goal-setting focuses on setting aggressive, measurable goals rather than strictly achieving them. To manage risks like size and complexity, teams should use incremental development and prototyping. Finally, the postmortem is essential for continuous process improvement, as it allows the team to learn from its experiences and propose changes for future projects.
π§ Quick Revision Questions
- What are the three principal responsibilities of a TSP team leader?
- Why is it counterproductive to evaluate a team solely on whether it meets its stated goals?
- What is the primary risk associated with a "too large product" and what is the recommended TSP strategy to manage it?
- What four questions should a team ask when developing its development strategy?
- Why is a postmortem an essential part of the TSP process?
π Lecture 26 β TSP Body of Knowledge
π Overview: This lecture introduces the Team Software Process (TSP) Body of Knowledge (BOK) developed by the SEI. It defines the fundamental knowledge and skills that distinguish TSP-trained professionals and provides a structured framework for practitioners, employers, and academic institutions. The lecture systematically covers the six core competency areas and their associated knowledge areas that form the foundation of TSP mastery.
ποΈ Topics Covered
The lecture begins by defining key terminology related to the body of knowledge, including competency area, knowledge area, concept, and skill. It then introduces the six TSP BOK competency areas: TSP Foundations and Fundamentals, Team Foundations, Project Planning with TSP, Project Implementation and Tracking with TSP, Gathering and Using TSP Data, and Scaling Up the TSP. Each competency area is broken down into its constituent knowledge areas with detailed explanations of their content and purpose.
π Lecture Summary
TSP Body of Knowledge
The SEI has drafted the Team Software Process Body of Knowledge (TSP BOK) document, which defines the fundamental knowledge and skills that set TSP-trained individuals apart from other software professionals. It helps individual practitioners 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. The TSP body of knowledge is composed of six competency areas, each with several knowledge areas.
π Definition β Competency Area: A group of closely-related knowledge areas that a practitioner is well qualified to perform intellectually or physically. π Definition β Knowledge Area: 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. π Definition β Concept: An explanatory principle applicable to a specific instance or occurrence within a particular knowledge area. π Definition β Skill: Proficiency, facility, or dexterity of performance that is acquired or developed through training or experience in a particular knowledge area.
TSP BOK Competence Areas
The six TSP BOK competency areas are: TSP Foundations and Fundamentals, Team Foundations, Project Planning with TSP, Project Implementation and Tracking with TSP, Gathering and Using TSP Data, and Scaling Up the TSP. These six areas collectively define the full scope of knowledge required for TSP mastery.
TSP Foundations and Fundamentals
This competency area outlines the foundational knowledge on which TSP is built and describes the fundamental concepts that a TSP practitioner must understand to successfully implement and practice the TSP methodology.
The knowledge areas composing this competency area are:
- Knowledge Work: PSP and TSP are practices designed to facilitate and improve both the process and the outputs of knowledge work, which is the interpretation, development, and implementation of information by skilled professionals within a specific subject area. This knowledge area discusses the nature of knowledge work and the team and workplace characteristics required for such work.
- TSP Prerequisite Knowledge: This outlines the fundamental concepts and skills that individuals must master before implementing the TSP methodology as a member of a TSP team. Although this area calls out some of the specific Knowledge Areas of the PSP BOK, the PSP BOK in its entirety is considered to be prerequisite knowledge for implementing the TSP in practice.
- TSP Principles: This outlines the basic 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 systems.
- TSP Process Elements and Measures: This describes the process elements and measures used in the TSP. Where applicable, overlaps with or differences from PSP process elements and measures are noted.
- TSP Quality Practices: This describes the specific quality practices added in the TSP to build on the individual quality practices used by PSP practitioners.
Team Foundations
A team consists of a group of people who act in cooperation to achieve a common purpose. When teams are effective in achieving their goals, it is because they are composed of members with complementary skills that work together to create a synergistic effort; effective teams achieve a kind of gestalt, in which the members' strengths are maximized and the weaknesses minimized so that the team as a whole becomes greater than the sum of its parts. Teams are especially appropriate for doing work of a highly complex nature (such as knowledge work) and for accomplishing large-scale tasks with many interdependent subtasks.
The knowledge areas are:
- Teams and Teambuilding: This describes the characteristics of teams and explains concepts for building high-performing project teams.
- Team Types, Styles, and Dynamics: This describes some of the models of team types, team styles, and team dynamics that provide a foundational understanding of team work in the TSP.
- Team Formation and Membership: This describes important parameters that should be considered when forming and populating TSP teams.
- Team Member Responsibilities: This describes the team's specific responsibilities for helping teams to be fully effective.
- Team Member Roles: This discusses the types of roles on TSP teams and delineates the responsibilities required of the various team member roles.
- Team Leader Role: This lists the roles that a TSP team leader must fulfill and discusses some of the tasks and responsibilities that accompany the various roles.
- Coach Role: This describes the general roles and responsibilities of the TSP coach.
Project Planning with TSP
Project planning with TSP begins when an organization makes the decision to implement the new technology using one or more small pilot projects. The organization works with a certified TSP coach to choose pilot teams and to provide them with training in PSP or process improvement techniques and in TSP project planning and tracking methodologies. Once trained, the team plans the project work by participating in a TSP launch.
The TSP launch process is actually a series of teambuilding activities that are organized into ten meetings. The TSP coach works with the team's members, leader, and managers to form an understanding of the project requirements, determine team goals, select team member roles, and make plans for producing the product. The team presents its plan to management and after receiving management acceptance for the plan, or an alternative plan, begins to work on the project. The knowledge areas in this competency area describe the requirements, activities, and guideposts for implementing pilot TSP projects and launching TSP teams.
The knowledge areas are:
- Change Management Fundamentals: This describes some of the fundamental concepts of change management and technology introduction that can help to facilitate the introduction of new technologies, processes, and practices into an organization.
- Piloting TSP in an Organization: This describes the general requirements and guidelines for initiating and conducting TSP pilot projects.
- Preparing Management and Teams for TSP Implementation: This describes the training and pre-launch preparations required to prepare executives, managers, team leaders, and team members for effective participation in TSP implementations.
- The TSP Launch Meetings: This provides an overview of the TSP launch and a description of each of the meetings that make up a TSP launch.
- The TSP Relaunch: The team relaunch is nearly the same as the launch except that it is done by a team that has already completed an initial launch of the same project. This knowledge area describes how the relaunch differs from the launch, explains when and how to conduct a relaunch, and delineates the inputs and outputs for the relaunch.
Project Implementation and Tracking with TSP
Following a TSP team launch or relaunch, the team members must work to implement their plan by completing the tasks which they have been assigned. The TSP does not mandate the use of any particular approach to project implementation; rather, it stipulates that team members should all use PSP (for engineering work) or best professional practices (for other types of work done in support of the project) to enable team members to produce high-quality product components or project elements.
TSP principles also require the team members to observe process discipline by following the processes and strategies that the team agreed to use; by requiring that the team members all record their data accurately, honestly, and in real time; and that the team members individually and collectively maintain a constant focus on quality. Faithful and precise data collection enables teams to monitor their progress against the plan. Up-to-date and accurate data can be analyzed to enable team members to identify potential problems with project schedule or product quality earlier in the process, rather than later. This allows teams to address these issues, fix the problems, or seek help before small problems become big problems that can derail the project. Using data for status tracking also provides the information necessary to generate reports for its stakeholders on the team's progress, and to advise management of potential problems so that they can provide assistance or additional resources to put the team back on track.
The knowledge areas are:
- Weekly Meetings: The weekly team meeting is one of the elements that differentiates TSP from typical software projects. It keeps the team members focused on the project work and allows regular opportunities for teamworking and team building.
- Checkpoints: Checkpoints are a series of meetings between the team leader, team members, and coach that allow everyone to discuss issues or problems such as process implementation, data gathering, or data analysis, and to generate solutions for any identified problems.
- Communicating with Stakeholders: Management is the primary stakeholder of the TSP team, although there may also be internal customers, external customers, or both. In addition, the team members themselves are stakeholders in the process and its outcome. Whoever the stakeholders may be, it is important that the TSP team communicates frequently with them and reports useful and timely information about status, schedule, and product quality.
- Replanning: Plans are subject to frequent change, particularly on new or inexperienced TSP teams. When plans change frequently it is easy for the team members to lose track of the overall team plan or their personal roles in meeting the plan.
- Phase, Cycle, and Project Postmortems: To ensure that the team stays on track and maintains its motivation, it may be desirable to hold periodic short replanning meetings, in which the team leader reviews the current management priorities, and the team members summarize their status and adjust their individual and team plans as needed to address those priorities. The postmortem analyzes the collected data on schedule, task hours, estimation, quality, and process. The results are used to provide personal, team and organizational planning data for use in an upcoming launch or relaunch and to identify improvements to process elements. The focus is on using data for planning and process improvement.
Gathering and Using TSP Data
In the same way that PSP relies on individual data, the TSP methods rely on data collection and analysis to enable teams to understand what they do and how they do it, thereby enabling teams to identify effective procedures that should continue to be used and to pinpoint those areas in which improvements are needed. Data provide a baseline for making estimates and plans, tracking progress against the plan, and measuring the effects of changes implemented as part of a process improvement effort. Therefore, it is critical to the successful implementation of TSP that teams collect data as they work, for use in later analyses and estimations.
The knowledge areas are:
- Data Recording: Data are used to provide teams with a baseline for making estimates and plans, tracking progress against the plan, and measuring the effects of changes implemented as part of a process improvement effort. Therefore, it is critical to the successful implementation of TSP that teams collect data accurately and in a timely manner as the project work progresses.
- Gathering and Using Size Data: Size and time are often correlated, and when they are, size estimates can be used to estimate effort and then create plans based on the size and effort estimates. Size data are also useful for tracking development effort and assessing product quality (when defect data are normalized based on size).
- Gathering and Using Schedule Data: Schedule data are used to predict the project's likely completion date and to track actual progress against the planned schedule.
- Gathering and Using Quality Data: The primary focus of the TSP is producing a high quality product, and it is required to learn the principles, measures, tools, and techniques for using data to manage quality.
- Gathering and Analyzing Postmortem Data: The postmortem provides the team with an opportunity to learn from its work to improve their product quality, design practices, planning and tracking, and teamwork.
By gathering, compiling, and analyzing the available data at the end of a phase, cycle or project when it can most economically, rapidly, and accurately be obtained, the team members can learn from their strengths and weaknesses and capitalize on this learning when they start another phase, cycle or project. 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.
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. 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 organization-wide implementation will be successful.
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. This is particularly true if the TSP project team requires more than 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. 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.
The knowledge areas are:
- Organizational Implementation: This describes the process of scaling the TSP implementation up from use on a few pilot projects to full introduction of TSP across the organization.
- 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. A functional team is one that has a continuing mission responsibility. Additional variations in team type are due to team size or physical location. 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).
- Large-scale TSP Teams: This describes the characteristics and considerations unique to large-scale TSP teams.
β Key Takeaways
The TSP Body of Knowledge is structured into six distinct competency areas, each containing several knowledge areas that define the complete skill set required for TSP practitioners. The foundation begins with understanding the nature of knowledge work, TSP principles, quality practices, and mastering PSP as prerequisite knowledge. Team dynamics are critical, as effective teams achieve a gestalt where collective strengths are maximized and weaknesses minimized through proper formation, roles, and leadership. Data collection and analysis are fundamental to TSP success, enabling accurate planning, tracking, quality management, and postmortem learning. The scaling of TSP from small pilot projects to organization-wide implementation requires careful change management and process variations (TSPf, TSPI, TSPd, TSPm, TSP+, TSPi) to accommodate different team sizes, types, and locations.
π§ Quick Revision Questions
- What are the six competency areas that compose the TSP Body of Knowledge?
- How does the TSP define a competency area and how does it differ from a knowledge area?
- What is the role of pilot projects in the TSP implementation process, and how do they relate to scaling up the TSP?
- What is a team gestalt and why is it important for effective TSP teams?
- What are the five main process variations of TSP (TSPf, TSPI, TSPd, TSPm, TSP+) and what type of team does each serve?