Fundamental of Software Project Management

1. Fundamental of Software Project Management Team Assignment 1 – K15T2 – Team 07

2. What is a Software Development Process? A software development process, also known as a software development life cycle, is a set of activities, methods, and practices that are used in the development of software. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process. It helps us build and deliver high quality software to satisfy customers/ market demands.

3. Software development activities

4. What is software development model? To develop software products, software engineers must establish a strategy consisting of the process, methods and tools, organizing them into a structure that guides the development called “Software Development Model”. Several models exist to streamline the development process. Each one has its pros and cons, and it's up to the development team to adopt the most appropriate one for the project. Sometimes a combination of the models may be more suitable.

5. Waterfall Model is a tradition model, linear, sequential, this model is very risky. It just have followed sequential a thorough process, so if the previous phases have mistakes then the project is failure.

6. Spiral Model

7. How the TSP was developed? • In 1996, Watts Humphrey developed the initial version of the TSP process. His objective was to provide an operation process to help engineers consistently do quality work.

8. Summary • Part 1: How the TSP was developed? • Part 2: What is Team Software Process? Part 3:Why focus on teams? Part 4 : TSP Development Process Part 5: The TSP Team working Process Part 6: TSP Quality Management Part 7: Advantages and Disadvantages Part 8: Who is using TSP?

9. How the TSP was developed? • In 1996, Watts Humphrey developed the initial version of the TSP process. His objective was to provide an operation process to help engineers consistently do quality work.

10. How the TSP was developed? 1. Engineer Team work 2. The Conditions for Teamwork 3. Effective Teams 4. Building Effective Teams

11. Summary • Part 1: How the TSP was developed? • Part 2: What is Team Software Process? Part 3:Why focus on teams? Part 4 : TSP Development Process Part 5: The TSP Team working Process Part 6: TSP Quality Management Part 7: Advantages and Disadvantages Part 8: Who is using TSP?

12. What is Team Software Process? Team Software Process (TSP) guides engineering teams that are developing software-intensive products. Using TSP helps organizations establish a mature and disciplined engineering practice that produces secure, reliable software in less time and at lower costs TSP is a process that is specifically designed for software teams. It’s purpose is to build high performance teams and help them : • plan their work • negotiate their commitments with management • manage and track projects to a successful conclusion • produce quality products in less time • achieve their best performance without the “death march” ending

13. Summary • Part 1: How the TSP was developed? • Part 2: What is Team Software Process? Part 3:Why focus on teams? Part 4 : TSP Development Process Part 5: The TSP Team working Process Part 6: TSP Quality Management Part 7: Advantages and Disadvantages Part 8: Who is using TSP?

14. Why focus on teams?

15. Launching a TSP team

16. Launching a TSP team

17. Summary • Part 1: How the TSP was developed? • Part 2: What is Team Software Process? Part 3:Why focus on teams? Part 4 : TSP Development Process Part 5: The TSP Team working Process Part 6: TSP Quality Management Part 7: Advantages and Disadvantages Part 8: Who is using TSP?

18. TSP Development Process

19. TSP Development Process

20. Summary • Part 1: How the TSP was developed? • Part 2: What is Team Software Process? Part 3:Why focus on teams? Part 4 : TSP Development Process Part 5: The TSP Team working Process Part 6: TSP Quality Management Part 7: Advantages and Disadvantages Part 8: Who is using TSP?

21. The TSP Team working Process Once the TSP team is launched, the principal need is to ensure that all team members follow the plan. This includes major topics: • Leading the team • Process discipline • Issue tracking • Communication • Management reporting • Maintaining the plan • Estimating project completion • Rebalancing team workload • Relaunching the project • TSP quality management

22. Summary • Part 1: How the TSP was developed? • Part 2: What is Team Software Process? Part 3:Why focus on teams? Part 4 : TSP Development Process Part 5: The TSP Team working Process Part 6: TSP Quality Management Part 7: Advantages and Disadvantages Part 8: Who is using TSP?

23. TSP Quality Management Planning for quality • TSP quality planning estimates the number of defects injected and removed at each phase based on historical injection rates and phase yields. • Removal rates, review rates, phase time ratios, defect densities, and other quality indicators are then calculated by the tools.

24. TSP Quality Management Measuring and tracking quality • Developers track every defect found and fixed. • Quality is reviewed weekly by the quality manager and the team.

25. TSP Quality Management Defect removal filters • Every activity that finds and removes defects can be thought of as a defect removal filter • TSP has many such filters. Capture/Recapture • TSP uses capture/recapture to estimate the defects missed in inspections. Defect prevention • Every defect found in system test or later is analyzed to prevent future escapes. • Every defective module is re-inspected.

26. Summary • Part 1: How the TSP was developed? • Part 2: What is Team Software Process? Part 3:Why focus on teams? Part 4 : TSP Development Process Part 5: The TSP Team working Process Part 6: TSP Quality Management Part 7: Advantages and Disadvantages Part 8: Who is using TSP?

27. Advantages of TSP Model • Members of the team can support each other. • Reductions in cost and schedule variance to less than +/- 10% • Self-directed teams: develop their own plans, negotiate commitments, track their work, keep management informed of project status and risks. • Productivity improvements of 25% or more. TSP have to planning for quality: estimates the number of defects injected and removed at each phase. It also measure and track quality: Developers track every defect found and fixed. Quality is reviewed weekly by the quality manager and the team.

28. Advantages of TSP Model • TSP schedule, time granularity is in hours, not days, weeks, or months. Time is a measure of time on task. Minus interruption time. TSP team members record their time as they work, not at the end of the day, week, or month.

29. Disadvantages of TSP Model • Training problem: It will take a lot of cost and time to training all the team. • TSP model is suitable for big project with high risk because it is a complicated. TSP projects are divided into cycles. Each cycle starts with a launch or relaunch and ends with a postmortem.

30. Summary • Part 1: How the TSP was developed? • Part 2: What is Team Software Process? Part 3:Why focus on teams? Part 4 : TSP Development Process Part 5: The TSP Team working Process Part 6: TSP Quality Management Part 7: Advantages and Disadvantages Part 8: Who is using TSP?

31. Who is using TSP? • Teradyne • Hill Air Force Base, near Salt Lake City, Utah, is the first U.S. government organization to be rated at CMM Level 5 • Boeing

32. Thanks for your listening !