1 / 19

SOFTWARE PROCESS IMPROVEMENT

SOFTWARE PROCESS IMPROVEMENT. SHARATH CHANDAR REDDY ALETI CSC 532 TERM PAPER. Introduction. Software Process can be defined as a set of activities, methods, transformations and practices that people use to develop and maintain software and the associated products.

michaelbryant
Download Presentation

SOFTWARE PROCESS IMPROVEMENT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SOFTWARE PROCESS IMPROVEMENT SHARATH CHANDAR REDDY ALETI CSC 532 TERM PAPER

  2. Introduction • Software Process can be defined as a set of activities, methods, transformations and practices that people use to develop and maintain software and the associated products. • software process improvement encompasses process assessment, process refinement (traditional SPI), and process innovation (introducing major process changes).

  3. Software Process: Objectives schedule (delivery date) functionality (features) quality (defects)

  4. Software Process Improvement • Are analyses of errors conducted to determine their process related causes? • Is a mechanism used for ensuring compliance to software engineering standards?

  5. ..Contd Resources may be invested on software process improvement to account for • shorter project duration • fewer developers using fewer labor months • less time spent testing, debugging, and fixing errors • less maintenance support • higher return on training and automated tools investment • greater predictability of project results

  6. The Process of getting Software Process Improvement started • Motivation • Expectation Setting • Visioning • Business Objectives • Software Process Improvement Infrastructure • Selecting the Process Improvement Participants • Managing Change • Determining the priority for the Process Improvement Implementation • Action Planning

  7. Business Motivation for Process Improvement • cycle time reduction • quality improvements in the delivered products • improved schedule performance because of more realistic estimates and reduced feature creep • reduced internal rework and wasted effort • reduced staff turnover and increased morale • the ability to facilitate movement of people from one project to another because of common software development practices.

  8. Guiding Principles for Software Project Improvement • The SPI initiative is intended to address business, technical, project management, and quality of life issues that are worth improving. The organization should be able to explain to stakeholders why a proposed activity or deliverable is important. • Process oriented work products must be concise, must add value, and must be usable. There is no intent to produce reams of documentation.

  9. ..Contd • The appropriate mindset for process change is to understand “what’s in it for us” as a project team, an organization, or a company and its customers, not just what’s in it for any individual. • The initiative will emphasize the importance of leveraging existing examples and templates. The organization must avoid the “not invented here” syndrome, choosing instead to borrow, buy, or adapt appropriate artifacts that already exist.

  10. IDEAL MODEL The ideal model assumed depicts five phases for SPI initiative • The Initializing Phase • The Diagnosing Phase • The Establishing Phase • The Acting Phase • The Leveraging Phase

  11. Figure showing the phases of IDEAL Model

  12. Process Improvement Goals • Short-Term Goals Define the SPI goals for the next 6-12 months, in terms of the areas to be worked on, the improvement objectives desired, and the ways in which progress toward these goals will be measured and determined

  13. ..Contd • Long-Term Goals Describe the long-term objectives of the SPI activity, over a span of 2 to 3 years. These may be motherhood statements, but the more they can be related to business objectives and correcting known shortcomings in the current business, the more plausible they will be. Keep goals few, concise, unambiguous, and measurable.

  14. Manage the Software Process Improvement program • Setting the stage for SPI program • Organizing the SPI program • Planning the SPI program • Staffing the SPI program • Monitoring the SPI program • Directing the SPI program

  15. Not all Processes are successful Reasons for SPI failures • Lack of executive level sponsorship • Lack of middle and first line management commitment • Organizational culture unwilling to change • Lack of commitment to continuous SPI improvement • Lack of successful resources in SPI effort

  16. Conclusion • Is software process improvement worth the investment? • Can a mature process really pay for itself?

  17. Answer YES! • Data from many software companies demonstrate a positive return on investment for software process improvement • Measurements include • expenditures • productivity • quality • customer satisfaction

  18. References • The Process of Getting Software Process Improvement Started. Tim Kasse. • A User’s Guide for Software Process Improvement. Bob Mc Feeley. • https://www.software.org/catalog/listing.asp?idCapability=2 • http://www.softwarems.com/consulting/proimprov.shtml

  19. THANK YOU

More Related