Difference between revisions of "Team Capability"
| Line 21: | Line 21: | ||
This article describes ways in which the systems engineering competencies needed by a team that to perform its systems engineering duties can be determined for projects and programs that are conducted to develop a new product, a new enterprise endeavor, or a new service; or to develop a significant enhancements to an existing product, enterprise endeavor, or service. The competencies needed and the competencies that are available influence the ways in which a systems engineering [[team (glossary)|team]], [[project (glossary)|project]], or [[program (glossary)|program]] is organized and enabled. | This article describes ways in which the systems engineering competencies needed by a team that to perform its systems engineering duties can be determined for projects and programs that are conducted to develop a new product, a new enterprise endeavor, or a new service; or to develop a significant enhancements to an existing product, enterprise endeavor, or service. The competencies needed and the competencies that are available influence the ways in which a systems engineering [[team (glossary)|team]], [[project (glossary)|project]], or [[program (glossary)|program]] is organized and enabled. | ||
| + | ===Individual competencies=== | ||
As noted in [[Enabling Individuals to Perform Systems Engineering]], competency of an individual is manifest in the knowledge, skills, abilities, and attitudes needed for the individual to perform a specific task efficiently and effectively. Different levels of competency may be needed in different situations. Competencies include occupational competence, social competence, and communication competence. Competent systems engineers, for example, have systems engineering knowledge, skills, and ability; engage in systems thinking; possess emotional intelligence; and have good communication and negotiation skills. In addition, competent systems engineers are typically competent within specific domains (e.g. aerospace, medicine, information technology) and within specific process areas of systems engineering (e.g., requirements, design, V&V). The article on [[Roles and Competencies]] includes a summary of systems engineering competency models. Based on the context, these competency models are tailored to match the needs of each project. The roles within the team are defined, and competencies are linked to the roles. The lists of competencies given in those models are most often distributed among the members of a team. It is not often that a single individual will fulfill the full list of competencies given in these models. | As noted in [[Enabling Individuals to Perform Systems Engineering]], competency of an individual is manifest in the knowledge, skills, abilities, and attitudes needed for the individual to perform a specific task efficiently and effectively. Different levels of competency may be needed in different situations. Competencies include occupational competence, social competence, and communication competence. Competent systems engineers, for example, have systems engineering knowledge, skills, and ability; engage in systems thinking; possess emotional intelligence; and have good communication and negotiation skills. In addition, competent systems engineers are typically competent within specific domains (e.g. aerospace, medicine, information technology) and within specific process areas of systems engineering (e.g., requirements, design, V&V). The article on [[Roles and Competencies]] includes a summary of systems engineering competency models. Based on the context, these competency models are tailored to match the needs of each project. The roles within the team are defined, and competencies are linked to the roles. The lists of competencies given in those models are most often distributed among the members of a team. It is not often that a single individual will fulfill the full list of competencies given in these models. | ||
| − | + | ===Collective competencies=== | |
In addition to individual competencies to perform systems engineering roles, the collective competencies needed by a systems engineering [[team (glossary)|team]] for a product, enterprise, or service depend on additional factors, including the domain, the stakeholders, the scope of the effort, criticality of outcome, new initiative versus enhancement, and the responsibilities and authority assigned to the SE team. For example, SE competencies needed to develop an IT enterprise architecture are quite different from those needed to support a mission-critical product at multiple sites. In the former case, the SE team might be organized to play the leadership role in working with senior managers, business process analysts, and other stakeholders at the organizational level, with participation of solution implementers (who may be internal or external to the organization), solution maintainers, and one or more vendors. In the latter case (supporting a mission-critical product at multiple sites), the SE team may consist of a centrally located lead systems engineer with a team of SE members, each deployed to one of the geographically dispersed sites. | In addition to individual competencies to perform systems engineering roles, the collective competencies needed by a systems engineering [[team (glossary)|team]] for a product, enterprise, or service depend on additional factors, including the domain, the stakeholders, the scope of the effort, criticality of outcome, new initiative versus enhancement, and the responsibilities and authority assigned to the SE team. For example, SE competencies needed to develop an IT enterprise architecture are quite different from those needed to support a mission-critical product at multiple sites. In the former case, the SE team might be organized to play the leadership role in working with senior managers, business process analysts, and other stakeholders at the organizational level, with participation of solution implementers (who may be internal or external to the organization), solution maintainers, and one or more vendors. In the latter case (supporting a mission-critical product at multiple sites), the SE team may consist of a centrally located lead systems engineer with a team of SE members, each deployed to one of the geographically dispersed sites. | ||
| Line 42: | Line 43: | ||
#Organize the systems engineering team in a manner that facilitates communication and coordination within the SE team and throughout the project or program; see [[Organizing Teams to Perform Systems Engineering]]. | #Organize the systems engineering team in a manner that facilitates communication and coordination within the SE team and throughout the project or program; see [[Organizing Teams to Perform Systems Engineering]]. | ||
| − | As indicated, the set of competencies needed to accomplish systems engineering for a product, enterprise, or service are established by first determining the scope of effort, the responsibilities and authority of the systems engineering team and the roles to be played by systems engineers. Competency models and skills inventories, such as the ''INCOSE SE Competencies Framework 2010-0205'' (INCOSE 2010) can be used as a checklist to assist in determining the needed competencies and competency levels for a product, enterprise, or service; see [[Roles and Competencies]]. | + | As indicated, the set of competencies needed to accomplish systems engineering for a product, enterprise, or service are established by first determining the scope of effort, the responsibilities and authority of the systems engineering team and the roles to be played by systems engineers. Competency models and skills inventories, such as the ''INCOSE SE Competencies Framework 2010-0205'' (INCOSE 2010) can be used as a checklist to assist in determining the needed competencies and competency levels for a product, enterprise, or service; see [[Roles and Competencies]]. |
==Accommodating team constraints== | ==Accommodating team constraints== | ||
Revision as of 18:22, 12 September 2011
The capability to perform systems engineering includes factors such as having competent personnel, adequate time, sufficient resources and equipment, and appropriate policies and procedures. Team capability requires both competency and capacity to perform the team's collective job functions. Team competency requires the collective aptitudes, intelligence, and skills among team members be used to perform their assigned duties. Capacity requires sufficient numbers of team members and sufficient time within their schedules to perform their duties. A team's capability to perform systems engineering is also dependent on morale and attitudes, at both the individual and team level.
Overview
According to Stephenson and Weil (Stephenson and Weil 1992), capable people are:
those who know how to learn; are creative; have a high degree of self-efficacy, can apply competencies in novel as well as familiar situations; and work well with others. In comparison to competency, which involves the acquisition of knowledge and skills, capability is a holistic attribute.
The results of a survey by Steward Hase (Hase 2000) concluded that the following factors are significant contributors to the human elements of capability:
- Competent People
- Working in Teams
- Visible Vision and Values
- Ensuring Learning Takes Place
- Managing the Complexity of Change
- Demonstrating the Human Aspects of Leadership
- Performing as Change Agents
- Involving People in Change
- Developing Management Talent
- Committing to Organizational Development
Determining needed team competencies
This article describes ways in which the systems engineering competencies needed by a team that to perform its systems engineering duties can be determined for projects and programs that are conducted to develop a new product, a new enterprise endeavor, or a new service; or to develop a significant enhancements to an existing product, enterprise endeavor, or service. The competencies needed and the competencies that are available influence the ways in which a systems engineering team, project, or program is organized and enabled.
Individual competencies
As noted in Enabling Individuals to Perform Systems Engineering, competency of an individual is manifest in the knowledge, skills, abilities, and attitudes needed for the individual to perform a specific task efficiently and effectively. Different levels of competency may be needed in different situations. Competencies include occupational competence, social competence, and communication competence. Competent systems engineers, for example, have systems engineering knowledge, skills, and ability; engage in systems thinking; possess emotional intelligence; and have good communication and negotiation skills. In addition, competent systems engineers are typically competent within specific domains (e.g. aerospace, medicine, information technology) and within specific process areas of systems engineering (e.g., requirements, design, V&V). The article on Roles and Competencies includes a summary of systems engineering competency models. Based on the context, these competency models are tailored to match the needs of each project. The roles within the team are defined, and competencies are linked to the roles. The lists of competencies given in those models are most often distributed among the members of a team. It is not often that a single individual will fulfill the full list of competencies given in these models.
Collective competencies
In addition to individual competencies to perform systems engineering roles, the collective competencies needed by a systems engineering team for a product, enterprise, or service depend on additional factors, including the domain, the stakeholders, the scope of the effort, criticality of outcome, new initiative versus enhancement, and the responsibilities and authority assigned to the SE team. For example, SE competencies needed to develop an IT enterprise architecture are quite different from those needed to support a mission-critical product at multiple sites. In the former case, the SE team might be organized to play the leadership role in working with senior managers, business process analysts, and other stakeholders at the organizational level, with participation of solution implementers (who may be internal or external to the organization), solution maintainers, and one or more vendors. In the latter case (supporting a mission-critical product at multiple sites), the SE team may consist of a centrally located lead systems engineer with a team of SE members, each deployed to one of the geographically dispersed sites.
The collective set of competencies needed by a systems engineering team to conduct a project or program can be determined as follows:
- Identify the context, to include:
- domain,
- stakeholders,
- organizational culture
- scope of effort,
- criticality of the product, enterprise endeavor, or service,
- new initiative or sustainment project
- Clarify the responsibilities, authority, and communication channels of the systems engineering team
- Establish the roles to be played by systems engineers, and other project personnel as determined by context, responsibilities, and authority
- Determine the required competencies and competency levels needed to fill each of the systems engineering roles
- Determine the number of systems engineers needed to provide the competencies and competency levels for each role
- Determine the availability of needed systems engineers
- Make adjustments based on unavailability of needed systems engineers
- Organize the systems engineering team in a manner that facilitates communication and coordination within the SE team and throughout the project or program; see Organizing Teams to Perform Systems Engineering.
As indicated, the set of competencies needed to accomplish systems engineering for a product, enterprise, or service are established by first determining the scope of effort, the responsibilities and authority of the systems engineering team and the roles to be played by systems engineers. Competency models and skills inventories, such as the INCOSE SE Competencies Framework 2010-0205 (INCOSE 2010) can be used as a checklist to assist in determining the needed competencies and competency levels for a product, enterprise, or service; see Roles and Competencies.
Accommodating team constraints
Having determined the needed competencies, competency levels, and capacities, one of two situations will arise: in the optimal case, the number of systems engineers who have the needed competencies and competency levels to fill the identified roles will be available and can be mapped into one of the organizational models presented in Organizing Teams to Perform Systems Engineering.
However, it is sometimes the case that some of the needed competencies, in sufficient quantities, are either unavailable or cannot be provided because of insufficient funding. For example, a new initiative may need a lead engineer, a requirements engineer, a systems architect and a systems integrator-tester to accomplish systems engineering tasks. Budgetary constraints may indicate that only two of the four roles can be supported. Some compromises must be made; perhaps the system architect will be the lead engineer and the requirements engineer will also be assigned the tasks of system integration and testing even though he or she does not have the desired skill and experience (i.e., competency level) in integration and testing.
References
This article relies heavily on limited sources. Reviewers are requested to identify additional sources.
Citations
Hase, Steward. 2000. Measuring Organizational Capability: Beyond Competence. Proceedings of Future research, research futures: Australian Vocational Education and Training Research Association (AVETRA) Conference (2000) http://www.avetra.org.au/abstracts_and_papers_2000/shase_full.pdf
Stephenson, J. & Weil, S. 1992. Quality in Learning: A Capability Approach in Higher Education. London, UK: Kogan Page.
Primary References
INCOSE 2010. Systems Engineering Competencies Framework, 2010-0205. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2010-003.
Additional References
No additional references have been identified for version 0.5. Please provide any recommendations on additional references in your review.
Article Discussion
Signatures
--Asquires 15:16, 15 August 2011 (UTC)