1 / 19

Software Process Improvement in Small Organizations

Software Process Improvement in Small Organizations. Ardalan Yousefi. Outline. Overview Benefits of SPI Why not use well-known SPI models? Competisoft ISO 29110 for VSEs. Overview. 85% of all software organizations are small companies Less than 50 employees

bond
Download Presentation

Software Process Improvement in Small Organizations

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 in Small Organizations Ardalan Yousefi

  2. Outline • Overview • Benefits of SPI • Why not use well-known SPI models? • Competisoft • ISO 29110 for VSEs

  3. Overview • 85% of all software organizations are small companies • Less than 50 employees • Not just a scaled-down version of large firms • Different business goals • Extremely responsive and flexible • Flat structure • Encourage entrepreneurship and innovation • Focus on a specific market niche

  4. Benefits of SPI • Is software process improvement really necessary in small software companies? • Greater software product quality • Decreased development risk • Increased competitiveness • Facilitation of marketing • Higher potential to export

  5. Prominent SPI Models • Well-known SPI standards not applicable to small companies • Difficult and bureaucratic • Inadequate guidance and support • Too costly for small enterprises

  6. Competisoft • A software process improvement and certification framework developed by researchers and companies from 11 Latin American countries plus Spain and Portugal

  7. Process Reference Model • Specifically designed for small companies • Contains guidelines and examples

  8. Evaluation Model • A set of measures for estimating the capability and performance of software processes • Capability measures • Performance measures • Based on purpose, description, work products, and activities from the Competisoft Reference Model

  9. Improvement Model • A lightweight process for economically running improvement programs in small organizations • Iterative and incremental • Composed of one or more improvement cycles • Initiating the cycle • Diagnosing the process • Formulating improvements • Executing improvements • Revising the cycle Influenced by XP and Scrum Influenced by IDEAL

  10. ISO 29110 • Published in 2010 by ISO • A subset of ISO/IEC 12207 and MoProSoft applicable to VSEs • Tailored to fit VSE needs

  11. ISO 29110 Guides • Assessment Guide • ISO/IEC 29110-3 • Management and Engineering Guide • ISO/IEC 29110-5-1-2 • Single application, single project team • Provides guidance on Project Management and Software Implementation Processes

  12. Software Implementation Process

  13. Deployment Packages • Deployment Packages • A set of artifacts facilitating the implementation of a set of practices, of the selected framework, in a VSE.

  14. Deployment Package Contents • Technical Description Purpose of this document Why this Topic is important? • Definitions • Relationships with ISO/IEC 29110 • Overview of Processes, Activities, Tasks, Roles and Products • Description of Processes, Activities, Tasks, Steps, Roles and Products  Role Description Product Description Artifact Description • Template • Example • Checklist • Tool • References to Other Standards and Models • References • Evaluation Form

  15. Summary • SPI standards such as CMMI or ISO/IEC 15504 not suitable for small organizations • Several research groups are developing SPI models specifically designed for small companies • Most of these models are very new • Evidence of success?

  16. References • I. Richardson and C. Gresse von Wangenheim, “Why are small software organizations different?,” Software, IEEE, vol. 24, no. 1, pp. 18-22, 2007. • C. Y. Laporte, S. Alexandre and R. V. O'Connor, "A Software Engineering Lifecycle Standard for Very Small Enterprises," Communications in Computer and Information Science, vol. 16, pp. 129-141, 2008. • H. Oktaba, F. Garcia, M. Piattini, F. Ruiz, F. J. Pino and C. Alquicira, "Software Process Improvement: The Competisoft Project," Computer, vol. 40, no. 10, pp. 21-28, October 2007.

  17. References (contd.) • B. McFeeley, "IDEAL: A Users Guide for Software Process Improvement" February 1996. [Online]. Available: http://www.sei.cmu.edu/reports/96hb001.pdf • S. Garcia, “Thoughts on Applying CMMI in Small Settings" 2005. [Online]. Available: http://www.sei.cmu.edu/library/assets/garcia-thoughts1.pdf • S. Garcia, S. Cepeda, M. J. Staley and G. Miluk “Lessons Learned from Adopting CMMI for Small Organizations" 2005. [Online]. Available: http://www.sei.cmu.edu/library/assets/garcia-cepeda.pdf

  18. References (contd.) • ISO/IEC 29110-5-1-2 http://standards.iso.org/ittf/PubliclyAvailableStandards/c051153_ISO_IEC_29110-5-1-2_2011.zip • “Deployment Packages for the Generic Profile Group for VSEs Developing Systems and/or Software”. [Online]. Available: http://profs.etsmtl.ca/claporte/english/VSE/VSE-packages.html

  19. Thank You!

More Related