Software Engineering Process Group

A Software Engineering Process Group (SEPG) is an organization's focal point for software process improvement activities. These individuals perform assessments of organizational capability, develop plans to implement needed improvements, coordinate the implementation of those plans, and measure the effectiveness of these efforts. Successful SEPGs require specialized skills and knowledge of many areas outside traditional software engineering.[1]

Following are ongoing activities of the process group:[1]

  • Obtains and maintains the support of all levels of management.
  • Facilitates software process assessments.
  • Works with line managers whose projects are affected by changes in software engineering practice, providing a broad perspective of the improvement effort and helping them set expectations.
  • Maintains collaborative working relationships with software engineers, especially to obtain, plan for, and install new practices and technologies.
  • Arranges for any training or continuing education related to process improvements.
  • Tracks, monitors, and reports on the status of particular improvement efforts.
  • Facilitates the creation and maintenance of process definitions, in collaboration with managers and engineering staff.
  • Maintains a process database.
  • Provides process consultation to development projects and management.

Sorts of SEPGs

Every SEPG has a different approach and mission. Some of the flavors include:

  • "Working" SEPGs that actually develop and deploy process as a type of internal consulting team.
  • "Oversight" SEPGs that oversee the process architecture, approve it, manage changes, and prioritize it (sort of a process CCB)
  • "Deliberative" SEPGs that debate the process approach and develop strategy for a process architecture and deployment
  • "Virtual" SEPGs that are made up of representatives from throughout the organization that dedicate a certain amount of time to the effort and are responsible for deploying and training everyone else in the organization[2]

See also

References

  1. ^ a b Fowler, Priscilla; Rifkin, Stanley (1990). "Software Engineering Process Group Guide". CMU/SEI-90-TR-024. Carnegie Mellon University. Retrieved 2009-09-05.
  2. ^ From the writings of Jeff Dalton, the author of "Agile CMMI"

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.