Difference between revisions of "Enabling Teams"
|Line 1:||Line 1:|
Part 5 on [[Enabling Systems Engineering]] explores how [[Systems Engineering (glossary)|systems engineering]] (SE) is enabled at three levels of
Part 5 on [[Enabling Systems Engineering]] explores how [[Systems Engineering (glossary)|systems engineering]] (SE) is enabled at three levels of organization: the [[Business (glossary)|business]] or [[Enterprise (glossary)|enterprise]], the [[Team (glossary)|team]], and . knowledge area focuses on enabling teams to perform SE. Part 3 [[Systems Engineering and Management]] how to perform SE .
Revision as of 12:39, 10 September 2012
Part 5 on Enabling Systems Engineering explores how systems engineering (SE) is enabled at three levels of organization: the business or enterprise, the team, and the individual. This knowledge area focuses on enabling teams to perform SE. Once a team is enabled using the techniques described here, the knowledge found in Part 3 Systems Engineering and Management about how to perform SE can be applied.
You can download all of Part 5, including this knowledge area, as a PDF.
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 a enterprise, see Enabling Systems Engineering.
Each part of the SEBoK is divided into knowledge areas (KAs), which are groupings of information with a related theme. The KAs in turn are divided into topics. This KA contains the following topics:
Systems engineers contribute to development and sustainment of products, enterprise systems, and the delivery of services. Systems engineers also coordinate the technical aspects of multiple projects that comprise a program. These activities require teams of individuals who share a common vision, and work in a cooperative manner to achieve shared objectives. Not all groups of individuals who work together perform as teams; thus, teams must be enabled to perform SE activities efficiently and effectively.
SE activities are sometimes accomplished by individuals but are more often accomplished by project teams that perform SE activities and provide 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, as well as enterprise architects in IT organizations and service providers 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. Three additional topics related to enabling the performance of project teams that perform SE are
- What do managers need to know about managing systems engineers and project teams that perform SE activities? Managers can gain insight into what they need to know about managing project teams that perform SE in the topics Relationships between Systems Engineering and Project Management and The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships.
- How do businesses determine value added by SE activities performed by project teams? This topic is addressed in Team Capability.
- How does an organization determine the efficiency and effectiveness of SE activities performed by project teams? This topic is addressed in Team Capability.
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/cmmi/solutions/pcmm/
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.
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.