Psp Tsp Agile 3 1 En
•Transferir como PPT, PDF•
4 gostaram•1,772 visualizações
The document discusses how the Personal Software Process (PSP) and Team Software Process (TSP) can be used to implement aspects of both Agile development and the Capability Maturity Model Integration (CMMI). PSP focuses on individual skills and discipline, while TSP builds on PSP to develop efficient, self-organizing teams. TSP/PSP teams can adapt Agile practices like iterative development and value delivery while achieving CMMI goals like defined processes and continuous improvement. Case studies show TSP/PSP reducing defects, rework, and improving productivity, quality, and maturity levels.
![[object Object],[object Object],[object Object],[object Object],# + Confidential | © Alcyonix / SQLI 2007 PSP/TSP in concert with process improvement activities will accelerate organization maturity. John D. Vu, The Boeing Company, 2001 Used TSP to cut defects in half and establish data baseline to improve future planning efforts Jim Sartain Over 20,300 major defects found prior to Test through TSP ; unit test defects dropped from 25 per KLOC to 7 per KLOC Jeffrey Smith (Coach TSP Microsoft IT) Agenda + +](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Psp Tsp Agile 3 1 En
Semelhante a Psp Tsp Agile 3 1 En (20)
Mais de Frederick Lussier
Último
Último (20)
Psp Tsp Agile 3 1 En
- 1. # Confidential | © Alcyonix / SQLI 2007 tm Personal Software Process, PSP and Team Software Process, TSP are service marks of Carnegie Mellon University ® Capability Maturity Model, Capability Maturity Modeling, Carnegie Mellon, CMM, and CMMI are registered in the U.S. Patent and Trademark Office by Carnegie Mellon University CMMI ® Agile Process Personal Software Process tm / Team Software Process tm + + 03 / 08 / 2011 V. 04 +
- 15. Agile adaptation Test Integration, non regression and functional test execution Confidential | © Alcyonix / SQLI 2007 # Plan Tests & Design Design Review & Inspection Code Code Review & Inspection Code Analysis Tests Execution PostMortem PSP Guide Requirements & Spec. Customer requirements, Technical requirements, Story, Acceptance Test, Priorized ‘Backlog’ High level architecture & design Conceptual design , Interfaces, Scenario, Use case, ... Release 1 Rel. 2 Rel. n Iteration1 Iteration 2 ... ... Regular project status meeting Validation Acceptance test Continuous integration Implementation Preparation, Demonstration and installation Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Cycle Daily standup meeting Environment War room, Servers, Continuous integration, development tools, Tests environment, Processes, Standards, Training, ... Iteration 3 Architecture Team vision Iteration0 Coach
- 16. Report example – Earn value Confidential | © Alcyonix / SQLI 2007 # Actual graphs obtained by running the PSP/TSP tools provided; based on anonymous data here.
- 17. Report example – Defects Confidential | © Alcyonix / SQLI 2007 # Actual graphs obtained by running the PSP/TSP tools provided; based on anonymous data here.
- 18. Report example – Process Performance Confidential | © Alcyonix / SQLI 2007 # Actual graphs obtained by running the PSP/TSP tools provided; based on anonymous data here.
- 19. Report example Confidential | © Alcyonix / SQLI 2007 # Actual graphs obtained by running the PSP/TSP tools provided; based on anonymous data here.
- 20. They use it Confidential | © Alcyonix / SQLI 2007 #
- 23. Results Confidential | © Alcyonix / SQLI 2007 # The Team Software Process (TSP) in Practice: A Summary of Recent Results CMU/SEI-2003-TR-014 and CMU/SEI-2000-TR-015 We developed a 450 KLOC business operating system in 55 000 hours. We delivered it on time. The customer reported 17 bugs for a total defect density of 0.038 bugs/KLOC. Gerardo López, Towa, CEO & President TSP Symposium 2008 1/3 project has no defects Measures With TSP Average Min – Max Typical Project System test defects (defects/KLOC) 0.4 0 to 0.9 15 Released defects (defects/KLOC) 0.06 0 to 0.2 7.5 System test effort (% of total effort) 4% 2% to 7% 40% System test schedule (% of total duration) 18% 8% to25% 40% Duration of system test (days/KLOC) 0.5 0.2 to 0.8 5 1 to 7.7 Unit Test - cost of quality 17% 4% to 38% 50% Project schedule error 6% -20% to 27% 180% Measures Average Productivity improvement 78%
- 24. Results # Microsoft Corporation 2006 Saved 1150 hours due to lower development costs. Saved 427 hours due to improved productivity. Saved 1047 hours and 90,783.00$us due to fewer defects in acceptance & production. Confidential | © Alcyonix / SQLI 2007 Opportunity after 4 projects: 2624 hours + 90,783.00 $
- 25. Results Confidential | © Alcyonix / SQLI 2007 # Intuit has also recently reported a savings of $20M from a reduction in customer support calls on QuickBooks 2007. Savings Reqts Design Implement Test Actually TSP Team Reqts Design Implement Test
Notas do Editor
- “… That is, while there is value in the items on the right, we value the items on the left more.” Agile is not successful when: lack of processes, lack of discipline, absent a role for plans or planning. The guiding principals mention: priority, most, primary, sustainable, excellence, and continuous… no absolutes! SCRUM, XP, DSDM, TDD, Orange, FDD