A Gap Analysis Methodology for the <br />Team Software Process (TSP)<br />Luís Amaral, João Pascoal Faria<br />Porto, Sept...
Agenda<br />Context and motivation<br />Objectives<br />Methodology<br />TSP, CMMI and ISO/IEC 15504 and their evaluation ...
Context and motivation<br />Software is more and more used by organizations to make sure its businesses run smoothly.<br /...
Objectives<br />Analyze the TSP as well as the most well known software process improvement methodologies and their assess...
Methodology<br />Analysis of the existing models and their evaluation methodologies<br />TSP and its assessment framework<...
TSP<br />TSP<br />Process that focus on people and teams, promotes quantitative and disciplined practices for software dev...
CMMI and SCAMPI<br />CMMI<br />Software process improvement approach focusing on 4 areas: project management, engineering,...
ISO/IEC 15504 and its evaluation framework<br />ISO/IEC 15504<br />Also know as SPICE and likewise CMMI, this ISO standard...
The TSP gap analysis methodology<br />
The TSP gap analysis methodologyPlanning: phases and activities<br />
The TSP gap analysis methodologyDeliverables<br />Deliverables<br />
The TSP gap analysis methodologyAnalysis dimensions<br />
The TSP gap analysis methodologyTools<br />Questionnaires<br />Developed to help the team to guide the interviews<br />Bas...
The TSP gap analysis methodologyReport template (1): Index<br />Executive Summary<br />Objectives<br />Methodology<br />TS...
The TSP gap analysis methodologyReport template (2): Gap analysis<br />Large benefit<br />Medium benefit<br />Small benefi...
The TSP gap analysis methodologyReport template (3): Performance analysis<br />Performance analysis is one key element in ...
Practical implementation<br />Implementation of the methodology in a well known Portuguese organization<br />Methodology a...
ConclusionsGoal satisfaction<br />The TSP methodology has been analyzed<br />The main models for software process improvem...
ConclusionsFuture work<br />Continuous experimentation of the methodology in organizations that want to implement TSP and ...
Contact<br />Strongstep - Innovationin software quality<br />Luís Amaral<br />luis.amaral@strongstep.pt<br />+351 93 910 5...
Upcoming SlideShare
Loading in...5
×

A gap analysis methodology for the Team Software Process (TSP) - QUATIC2010

2,871

Published on

A gap analysis methodology for the Team Software Process (TSP) presented at QUATIC 2010

Published in: Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,871
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

A gap analysis methodology for the Team Software Process (TSP) - QUATIC2010

  1. 1. A Gap Analysis Methodology for the <br />Team Software Process (TSP)<br />Luís Amaral, João Pascoal Faria<br />Porto, September 29th, 2010<br />
  2. 2. Agenda<br />Context and motivation<br />Objectives<br />Methodology<br />TSP, CMMI and ISO/IEC 15504 and their evaluation methodologies<br />The TSP gap analysis methodology<br />Practical implementation<br />Conclusions and future wok<br />
  3. 3. Context and motivation<br />Software is more and more used by organizations to make sure its businesses run smoothly.<br />There is a high percentage of <br />challenged and failed projects in one<br />or more of their control variables: <br />scope, cost and shcedule.<br />The TSP methodology has been<br />developed to address these problems<br />as well as quality.<br />Organizations feel that these methodologies are useful however they would like to know where they are in respect to some proposed referential before embracing a project of this nature.<br />Success<br />Challenged<br />Cancelled<br />StandishGroup: ChaosReport 2008<br />
  4. 4. Objectives<br />Analyze the TSP as well as the most well known software process improvement methodologies and their assessment frameworks<br />Provide a methodology and tools that facilitate taking a decision about the adoption of TSP and preparing for its implementation<br />Validate the methodology by applying the process to an organization<br />
  5. 5. Methodology<br />Analysis of the existing models and their evaluation methodologies<br />TSP and its assessment framework<br />CMMI and SCAMPI<br />ISO 15504 and its evaluation framework<br />Definition of the gap analysis methodology<br />Validation<br />Implementation in one Portuguese organization<br />
  6. 6. TSP<br />TSP<br />Process that focus on people and teams, promotes quantitative and disciplined practices for software development<br />Ensures high quality, on-time and on-budget software products as well as processes in the organization<br />Certifying software organizations in TSP<br />SEI is piloting a certification methodologyfor organizations that use TSP (1 organization piloted so far)<br />Full focus on 3 perspectives: individuals, <br />processes and products<br />
  7. 7. CMMI and SCAMPI<br />CMMI<br />Software process improvement approach focusing on 4 areas: project management, engineering, support and process management<br />Most widely known model for software process improvement<br />SCAMPI<br />The only ARC (Appraisal requirements for CMMI) compliant methodology for evaluating organizations against the CMMI practices<br />Strong focus on evidence gathering by evidence observation and affirmations<br />
  8. 8. ISO/IEC 15504 and its evaluation framework<br />ISO/IEC 15504<br />Also know as SPICE and likewise CMMI, this ISO standard goal is to help organizations improving the way they develop software.<br />Derived from the software process lifecycle standard ISO 12207<br />ISO/IEC 15504 evaluation framework<br />The evaluation framework is described in parts 2 and 3 or this standard: “Performing an Assessment” and “Guidance on performing an assessment”<br />The focus regarding information gathering is similar to CMMI advocating the use of interviews and artifacts collection<br />
  9. 9. The TSP gap analysis methodology<br />
  10. 10. The TSP gap analysis methodologyPlanning: phases and activities<br />
  11. 11. The TSP gap analysis methodologyDeliverables<br />Deliverables<br />
  12. 12. The TSP gap analysis methodologyAnalysis dimensions<br />
  13. 13. The TSP gap analysis methodologyTools<br />Questionnaires<br />Developed to help the team to guide the interviews<br />Based on 3 main roles: project manager, developer and tester<br />Updated after the execution of the interviews<br />Performance benchmark<br />Basic framework developed and adaptable for each organization<br />Based on main project metrics (many times unavailable): schedule, effort, size and defects<br />
  14. 14. The TSP gap analysis methodologyReport template (1): Index<br />Executive Summary<br />Objectives<br />Methodology<br />TSP<br />The Organization<br />Gap Analysis<br />Performance Analysis<br />Plan for implementation <br />Critical success factors<br />Conclusion<br />
  15. 15. The TSP gap analysis methodologyReport template (2): Gap analysis<br />Large benefit<br />Medium benefit<br />Small benefit<br />
  16. 16. The TSP gap analysis methodologyReport template (3): Performance analysis<br />Performance analysis is one key element in the methodology as it will show the company quantifiable benefits it can get by implementing TSP<br />For performing the analysis it is necessary to gather relevant data about one or more projects of the organization<br />Base measures used: schedule, effort, size and defects<br />
  17. 17. Practical implementation<br />Implementation of the methodology in a well known Portuguese organization<br />Methodology applied and lessons learned incorporated<br />Questionnaires improvement<br />Delivery of the final report prior to the final presentation<br />Support and validation of the SEI during the implementation<br />Praised results by the organization stating that the picture taken was very good and accurate<br />Praised results by the SEI <br />
  18. 18. ConclusionsGoal satisfaction<br />The TSP methodology has been analyzed<br />The main models for software process improvement together with their assessment frameworks have been analyzed (CMMI and ISO/IEC 15504)<br />A gap analysis methodology for the TSP has been defined and tools have been developed to help the implementation<br />Fast to implement<br />Inexpensive (when compared with other analyzed methodologies)<br />The methodology has been implemented and results validated by the organization and by the SEI<br />
  19. 19. ConclusionsFuture work<br />Continuous experimentation of the methodology in organizations that want to implement TSP and need an initial gap analysis<br />Continuous improvement of the methodology <br />Lessons learned from its application<br />More formality<br />Tailorable<br />Continuous awareness of other evaluation methodologies<br />New produced knowledge<br />
  20. 20. Contact<br />Strongstep - Innovationin software quality<br />Luís Amaral<br />luis.amaral@strongstep.pt<br />+351 93 910 5060<br />Web: www.strongstep.pt<br />Phone: + 351 22 030 15 85<br />Rua actor Ferreira da Silva, UPTEC<br />4200-298 Porto, Portugal<br />

×