Team Software Process.ppt

Team Software Process By: Bryan Peterson Presentation Topics History Brief overview of the Team Software Process (TSP) TSP Team Launch Team-working Conclusion History Watts S. Humphrey Introduced the Capability Maturity Model (CMM) in the 1980’s Personal Software Process individual level Team Software Process TSP Overview The Team Software Process (TSP) is a defined process for a group of students or software professionals to develop quality software on time and within budget It is based on a sequential incremental model that divides development effort into a set of development cycles where each cycle involves producing software that satisfies some subset of the software requirements TSP builds upon the Personal Software Process (PSP) The Launch Day 1 Meeting 1 Marketing and management meet with the team to discuss the group’s objective Meeting 2 Team defines its goals and each member’s individual roles are identified and recorded Meeting 3 Conceptual design Development strategy Multiple-build strategy Define development process to be used Support tools Define products to be produced Day 2 Meeting 4 Develop team plan Estimate product sizes Identify project tasks Estimate effort Produce schedule of team’s availability Alternative plans Meeting 5 Quality plan can be used in parallel with the project development stages to assess the quality of the work as progress is being made Peer reviews Meeting 6 Balance team plan Track progress against plan Day 3 Meeting 7 Risk assessment Meeting 8 Prepare launch report for management Day 4 Meeting 9 Hold management review Launch Postmortem Review team’s work Provides a structured way to learn and improve Look at what you did compared to what you planned to do Look for improvement opportunities and decide how to change your practices for the next cycle or the next project TSP Structure and Flow Team Working Consists of following and maintaining the plan Tracking progress Conclusion TSP provides a development framework to produ