|
|
| (40 intermediate revisions by 8 users not shown) |
| Line 1: |
Line 1: |
| − | The goal of [[Project Management (glossary)|project management (glossary)]] 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 and project management. | + | ---- |
| − | | + | '''''Lead Author:''''' ''Dick Fairley'', '''''Contributing Authors:''''' ''Richard Turner, Alice Squires'' |
| − | To download a PDF of all of Part 6 (including this knowledge area), please [http://www.sebokwiki.org/075/images/8/80/SEBoK075_Part6.pdf click here].
| + | ---- |
| | + | 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). |
| | | | |
| | ==Topics== | | ==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: | + | 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: |
| | *[[The Nature of Project Management]] | | *[[The Nature of Project Management]] |
| − | *[[An Overview of the PMI Guide to the Project Management Body of Knowledge (PMBOK(TM))]] | + | *[[An Overview of the PMBOK® Guide]] |
| | *[[Relationships between Systems Engineering and Project Management]] | | *[[Relationships between Systems Engineering and Project Management]] |
| | *[[The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships]] | | *[[The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships]] |
| − | | + | *[[Procurement and Acquisition]] |
| − | ==The Nature of Project Management==
| + | *[[Portfolio Management]] |
| − | Project managers and systems engineers are both concerned with management issues such as planning, measuring and controlling, leading, directing, and managing risk. In the case of project managers, the project attributes to be managed include project plans, estimates, schedule, budget, project structure, staffing, resources, infrastructure and risk factors. Product attributes managed by systems engineers include items such as requirements allocation and flow-down, system architecture, structure of and interactions among technical teams, [[Systems Engineering and Specialty Engineering|specialty engineering]], [[integration (glossary)]], [[System Verification|verification]] and [[System Validation|validation]]. The exact allocation of the [[Acronyms|SE]] and [[Acronyms|PM]], duties depend on many factors such as customer and [[Stakeholder Needs and Requirements|stakeholder]] interactions, organizational structure of the parent organization, and relationships with affiliate contractors and subcontractors. See the article on [[The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships]] in this KA.
| |
| − | | |
| − | The activities of project management include the following (Fairley 2009; Forsberg et al 2005):
| |
| − | *Planning and Estimating
| |
| − | *Measuring and Controlling | |
| − | *Leading and Directing
| |
| − | *Managing Risk
| |
| − | | |
| − | ==Planning and Estimating==
| |
| − | [[Planning]] a project involves providing answers to the who, what, where, when, and why questions: | |
| − | *'''Who:''' addresses staffing issues (competencies, numbers of staff, communication and coordination)
| |
| − | *'''What:''' addresses the scope of activities
| |
| − | *'''Where:''' addresses issues of locale (local, geographically distributed)
| |
| − | *'''When:''' addresses scheduling issues
| |
| − | *'''Why:''' addresses rationale for conducting a project
| |
| − | | |
| − | Guidance for developing project plans can be found in INCOSE (2012), NASA (2007), and ISO/IEC/IEEE Standard 16326:2009. It is often observed that communication and coordination among stakeholders during project planning are equally important and sometimes more important than the documented plan that is produced.
| |
| − | | |
| − | Estimation is an important element of planning. An estimate is a projection from past to future, adjusted to account for differences between past and future. Estimation techniques include analogy, rule of thumb, expert judgment, and use of parametric models such as [[Acronyms|COCOMO]] for software projects and [[Acronyms|COSYSMO]] for systems projects (Boehm et al 2000; Valerdi 2008).
| |
| − | | |
| − | Systems engineering contributes to project estimation by ensuring that
| |
| − | *the overall system life cycle is understood;
| |
| − | *dependencies on other systems and organizations are identified; | |
| − | *the logical dependencies during development are identified; and
| |
| − | *resources and key skills are identified and planned.
| |
| − | | |
| − | Additionally, the high-level system architecture and a risk assessment provide the basis for the work breakdown structure and the organizational breakdown structure.
| |
| − | | |
| − | ==Measuring and Controlling ==
| |
| − | Measuring and controlling are the key elements of executing a project. Measurement includes collecting measures for work products and work processes. For example, determining the level of coverage of requirements in a design specification can be assessed by reviews, analysis, prototyping, and traceability. Effort and schedule expended on the work processes can be measured and compared to estimates; earned value tracking can be used for this purpose. Controlling is concerned with analyzing measurement data and implementing corrective actions when actual status does not align with planned status. Additional information on measurement and control of technical factors can be found in the [[Measurement]] and [[Assessment and Control]] articles in Part 3 of this SEBoK.
| |
| − | | |
| − | ==Leading and Directing==
| |
| − | Leading and directing requires communication and coordination among all project stakeholders, both internal and external to a project. Systems engineers may be responsible for managing all technical aspects of project execution, or they may serve as staff support for the project manager or project management office. Organizational relationships between systems engineers and project managers are presented in [[Organizing Teams to Perform Systems Engineering]] in Part 5 of this SEBoK. Other organizational considerations for the relationships between systems engineering and project management are covered in Part 5, [[Enabling Systems Engineering]].
| |
| − | | |
| − | ==Managing Risk ==
| |
| − | [[Risk Management (glossary)|Risk management (glossary)]] is concerned with identifying and mitigating potential problems before they become real problems. Systems engineering projects are, by nature, high-risk endeavors because of the many unknowns and uncertainties that are inherent in projects. Because new risk factors typically emerge during a project, ongoing, continuous risk management is an important activity for both systems engineers and project managers.
| |
| − | | |
| − | Every aspect of a project may encounter potential and real problems; systems engineers are typically concerned with technical risk and project managers with programmatic risk. Sometimes, technical risk factors are identified and confronted by systems engineers and programmatic risk factors are identified and confronted by project managers, but without adequate communication between them. In these cases appropriate tradeoffs among requirements, schedule, budget, infrastructure, and technology may not be made, which creates additional risk for the successful outcome of a project.
| |
| − | | |
| − | Additional information on risk management for systems engineering projects can be found in the [[Risk Management]] article in Part 3 of this SEBoK.
| |
| | | | |
| | ==References== | | ==References== |
| | ===Works Cited=== | | ===Works Cited=== |
| − | | + | None. |
| − | Boehm, B., C. Abts., A.W. Brown, S. Chulani, B.K. Clark, E. Horowitz, R. Madachy, D. Reifer, and B. Steece. 2000. ''Software Cost Estimation with COCOMO II''. Upper Saddle River, NJ, USA: Prentice Hall.
| |
| − | | |
| − | 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.'' Hoboken, NJ, USA: John Wiley and Sons.
| |
| − | | |
| − | INCOSE. 2012. ''Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities,'' version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.2.
| |
| − | | |
| − | ISO/IEC/IEEE. 2009. ''Systems and Software Engineering - Life Cycle Processes - Project Management''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electronical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE), ISO/IEC/IEEE 16326:2009(E).
| |
| − | | |
| − | NASA. 2007. ''Systems Engineering Handbook." Washington, DC,USA: National Aeronautics and Space Administration.
| |
| − | | |
| − | Valerdi, R. 2008.''The Constructive Systems Engineering Cost Model (COSYSMO): Quantifying the Costs of Systems Engineering Effort.'' Saarbrucken, Germany: VDM Verlag.
| |
| | | | |
| | ===Primary References=== | | ===Primary References=== |
| | | | |
| − | Fairley, R.E. 2009. ''[[Managing and Leading Software Projects]].'' Hoboken, NJ, USA: John Wiley & Sons. | + | 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. | + | 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=== | | ===Additional References=== |
| − | Blanchard, B. 2008.'' System Engineering Management.'' Hoboken, NJ, USA: John Wiley & Sons.
| + | None. |
| − | | |
| − | Kerzner, Harold. 2003. ''Project Management: A Systems Approach to Planning, Scheduling, and Controlling''. 8th Ed. Hoboken, NJ, USA: John Wiley & Sons.
| |
| | | | |
| − | Martin, J. 1997. ''Systems Engineering Guidebook: A Process for Developing Systems and Products.'' London, UK: Taylor and Francis Group CRC-Press, LLC.
| |
| | ---- | | ---- |
| − | <center>[[Ten Things a Systems Engineer Needs to Know about Managing a Software Team|< Previous Article]] | [[Related Disciplines|Parent Article]] | [[The Nature of Project Management|Next Article >]]</center> | + | <center>[[Systems Engineering and Industrial Engineering|< Previous Article]] | [[Related Disciplines|Parent Article]] | [[The Nature of Project Management|Next Article >]]</center> |
| | | | |
| | + | <center>'''SEBoK v. 2.5, released 15 October 2021'''</center> |
| | | | |
| | [[Category: Part 6]][[Category:Knowledge Area]] | | [[Category: Part 6]][[Category:Knowledge Area]] |
| − | {{DISQUS}}
| |