Difference between revisions of "Enabling Teams"

From SEBoK
Jump to navigation Jump to search
m (Text replacement - "<center>'''SEBoK v. 2.5, released 15 October 2021'''</center>" to "<center>'''SEBoK v. 2.6, released 13 May 2022'''</center>")
m (Text replacement - "<center>'''SEBoK v. 2.7, released 31 October 2022'''</center>" to "<center>'''SEBoK v. 2.8, released 31 May 2023'''</center>")
(2 intermediate revisions by the same user not shown)
Line 58: Line 58:
[[Category: Part 5]][[Category:Knowledge Area]]
[[Category: Part 5]][[Category:Knowledge Area]]
<center>'''SEBoK v. 2.6, released 13 May 2022'''</center>
<center>'''SEBoK v. 2.8, released 31 May 2023'''</center>

Latest revision as of 17:40, 17 May 2023

Lead Author: Dick Fairley, Contributing Authors: Alice Squires, Art Pyster

This knowledge area focuses on enabling a teamteam to perform SE. Once that is done using the techniques described here, the knowledge found in Part 3, Systems Engineering and Management, about how to perform SE can be applied. Part 5, Enabling Systems Engineering, to which this knowledge area belongs, explores how systems engineeringsystems engineering (SE) is enabled at three levels of organization: the businessbusiness or enterpriseenterprise, the team, and the individual.

For the sake of brevity, the term “business” is used to mean “business or enterprise” throughout most of this knowledge area. For a nuanced explanation of what distinguishes a business from an enterprise, see Enabling Systems Engineering.


Each part of the SEBoK is composed of knowledge areas (KAs). Each KA groups topics together around a theme related to the overall subject of the part. This KA contains the following topics:


Products, enterprise systems, and services are developed, delivered, and sustained with the contributions of systems engineers, who also coordinate the technical aspects of the multiple projects that comprise a programprogram. These activities require certain individuals to work in a cooperative manner to achieve shared objectives based on a common vision—that is, as teams. Not every group of individuals working together is a team. To perform SE activities efficiently and effectively, the capabilities of and dynamics within the team must be specifically attuned to SE.

Although individuals sometimes perform SE activities, it is more usual to find project teams performing SE activities while providing specialty engineering capabilities (see Systems Engineering and Specialty Engineering). Not all who perform SE activities are labeled “systems engineers.” Thus, electrical, mechanical, and software engineers, service providers, or enterprise architects in IT organizations may lead or be members of teams that perform SE tasks. Those individuals are referred to as systems engineers in this knowledge area, regardless of their job titles within their organizations.

This knowledge area is concerned with methods, tools, and techniques for enabling project teams to perform SE activities. Its first topic, Team Capability, answers the questions:

  • How do businesses determine value added by SE activities performed by project teams?
  • How does an organization determine the efficiency and effectiveness of SE activities performed by project teams?

Its other topic, Team Dynamics, answers the question:

  • How are group dynamics crucial to enabling systems engineers to perform work and achieve goals?

Topics from elsewhere in the SEBoK that cover related questions include Relationships between Systems Engineering and Project Management and The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships, which answer the question:

  • What do managers need to know about managing systems engineers and project teams that perform SE activities?


Works Cited


Primary References

Brooks, F. 1995. The Mythical Man-Month, Anniversary Edition. Reading, MA, USA: Addison Wesley.

Curtis, B., W.E. Hefley, and S.A. Miller. 2001. People Capability Maturity Model (P-CMM), Version 2.0. Pittsburg, PA, USA: Software Engineering Institute (SEI). CMU/SEI-2001-MM-01. Accessed on June 8, 2012. Available at http://www.sei.cmu.edu/library/abstracts/reports/01mm001.cfm.

DeMarco, T. and T. Lister. 1999. Peopleware: Productive Projects and Teams, 2nd ed. New York, NY, USA: Dorset House.

Eisner, H. 2008.Essentials of Project and Systems Engineering Management, 3rd ed. Hoboken, NJ, USA: John Wiley and Sons.

Fairley, R.E. 2009. Managing and Leading Software Projects. Hoboken, NJ, USA: John Wiley & Sons.

Forsyth, D.R. 2010. Group Dynamics, 5th edition. Belmont, CA, USA: Wadsworth, Cengage Learning.

Hase, S. 2000. "Measuring Organisational Capability: Beyond Competence", Paper presented at Future Research, Research Futures: Australian Vocational Education and Training Research Association (AVETRA) Conference (2000). Accessed on June 8, 2012. Available at http://www.avetra.org.au/abstracts_and_papers_2000/shase_full.pdf.

INCOSE. 2010. Systems Engineering Competencies Framework 2010-0205. San Diego, CA, USA: International Council on Systems Engineering (INCOSE). INCOSE-TP-2010-003.

NASA. 2011. Academy of Program/Project and Engineering Leadership (APPEL), NASA APPEL Performance Enhancement. Accessed on September 15, 2011. Available at http://www.nasa.gov/offices/oce/appel/performance/index.html.

Additional References


< Previous Article | Parent Article | Next Article >
SEBoK v. 2.8, released 31 May 2023