Difference between revisions of "Systems Engineering and Project Management"

Latest revision as of 22:21, 18 November 2023

Lead Author: Dick Fairley, Contributing Authors: Richard Turner, Alice Squires

The goal of project managementproject management is to plan and coordinate the work activities needed to deliver a satisfactory product, service, or enterprise endeavor within the constraints of schedule, budget, resources, infrastructure, and available staffing and technology. The purpose of this knowledge area (KA) is to acquaint systems engineers with the elements of project management and to explain the relationships between systems engineering (SE) and project management (PM).

Topics

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:

References

Works Cited

None.

Primary References

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

Forsberg, K., H. Mooz, and H. Cotterman. 2005. Visualizing Project Management, 3rd ed. New York, NY, USA: John Wiley & Sons.

PMI. 2013. A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 5th ed. Newtown Square, PA, USA: Project Management Institute (PMI).

Additional References

None.

< Previous Article | Parent Article | Next Article > SEBoK v. 2.9, released 20 November 2023

@@ Line 1: / Line 1: @@
-The goal of [[Project Management (glossary)|project management]] is to plan and coordinate the work activities needed to deliver a satisfactory product, service, or enterprise endeavor within the constraints of schedule, budget, resources, infrastructure, and available technology.  According to Section 1.3 of the PMBOK® Guide – Fourth Edition, project management is "accomplished through the appropriate application and integration of the 42 logically grouped project management processes comprising the 5 process groups" (PMI 2008). The 5 process groups are:
+----
+'''''Lead Author:''''' ''Dick Fairley'', '''''Contributing Authors:''''' ''Richard Turner, Alice Squires''
-*Initiating,
+----
-*Planning,
+The goal of {{Term|Project Management (glossary)|project management}} is to plan and coordinate the work activities needed to deliver a satisfactory product, service, or enterprise endeavor within the constraints of schedule, budget, resources, infrastructure, and available staffing and technology.   The purpose of this knowledge area (KA) is to acquaint systems engineers with the elements of project management and to explain the relationships between systems engineering (SE) and project management (PM).
-*Executing,
-*Monitoring and Controlling, and
-*Closing.
-Each of the 42 processes is specified by Inputs, Tools & Techniques, and Outputs.  Data flow diagrams are used to illustrate the relationships between each process and the other processes with which each process interacts.
 ==Topics==
-The Systems Engineering and Project Management knowledge area contains the following topics:
+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:
-*[[An Overview of Project Management]]
+*[[The Nature of Project Management]]
-*[[Systems Engineering and Project Management: Similarities and Differences]]
+*[[An Overview of the PMBOK® Guide]]
+*[[Relationships between Systems Engineering and Project Management]]
-==PMBOK Overview==
+*[[The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships]]
-The Initiating process group in PMBOK® includes developing a project charter and identifying stakeholders.  Planning includes 20 of the 42 project management processes; they range from develop project management plan, collect requirements, define scope, and create WBS to develop schedule, develop budget, plan quality, identify risks, plan risk responses, and plan procurements.  The Monitoring and Controlling process group is comprised of 10 processes that include control scope, control schedule, control cost, perform quality control, and monitor and control risks.  the Closing process group includes close project or phase, and close procurements.
+*[[Procurement and Acquisition]]
+*[[Portfolio Management]]
-The scope of project management thus encompasses the total set of management concerns that contribute to successful outcomes.  This knowledge area provides an overview of project management and describes the relationships between systems engineering, project management, and systems engineering project management.
-==Future Version 1.0 Additions==
-For the Version 1.0 of the SEBoK we will focus this section on what a systems engineer needs to know to manage the SE portions of the project. We will also discuss how to engage and collaborate with the project manager to ensure that SE has sufficient resources and priorities.
-Topics being considered are: TBD.
 ==References==
-===Citations===
+===Works Cited===
+None.
-PMI 2008. [[A Guide to the Project Management Body of Knowledge]]. 4th ed. Newtown Square, PA, USA: Project Management Institute (PMI).
 ===Primary References===
-Fairley, Richard E. 2009. [[Managing and Leading Software Projects]]. Hoboken New Jersey: John Wiley & Sons.
+Fairley, R.E. 2009. ''[[Managing and Leading Software Projects]]''. Hoboken, NJ, USA: John Wiley & Sons.
-NASA. 2007. [[NASA Systems Engineering Handbook|Systems Engineering Handbook]], Revision 1 (NASA/SP-2007-6105). Washington, D.C.: NASA.
+Forsberg, K., H. Mooz, and H. Cotterman. 2005. ''[[Visualizing Project Management]]'', 3rd ed. New York, NY, USA: John Wiley & Sons.
-PMI 2008. [[A Guide to the Project Management Body of Knowledge]]. 4th ed. Newtown Square, PA, USA: Project Management Institute (PMI).
+PMI. 2013. ''[[A Guide to the Project Management Body of Knowledge|A Guide to the Project Management Body of Knowledge (PMBOK® Guide)]]'', 5th ed. Newtown Square, PA, USA: Project Management Institute (PMI).
 ===Additional References===
+None.
-Blanchard, Benjamin.  2008. System Engineering Management.  Hoboken New Jersey: John Wiley & Sons.
-Martin, James. 1997. Systems Engineering Guidebook: A Process for Developing Systems and Products. London: Taylor and Francis Group CRC-Press, LLC.
 ----
-====Article Discussion====
+<center>[[Systems Engineering and Industrial Engineering|< Previous Article]] | [[Related Disciplines|Parent Article]] | [[The Nature of Project Management|Next Article >]]</center>
-[[{{TALKPAGENAME}}|[Go to discussion page]]]
-<center>[[Software Engineering and Systems Engineering: Similarities and Differences|<- Previous Article]] | [[Related Disciplines|Parent Article]] | [[An Overview of Project Management|Next Article ->]]</center>
-==Signatures==
---[[User:Bkcase|Bkcase]] 19:07, 22 August 2011 (UTC) (on behalf of Dick Fairley)
---[[User:Asquires|Asquires]] 16:28, 2 September 2011 (UTC)Incomplete article
+<center>'''SEBoK v. 2.9, released 20 November 2023'''</center>
---[[User:Rturner|Rturner]] 17:03, 8 September 2011 (UTC) tech edit
 [[Category: Part 6]][[Category:Knowledge Area]]