The purpose of a ConOps document is to describe the functional characteristics of the to-be delivered system from the user’s viewpoint. Washington, DC, USA: National Aeronautics and Space Administration (NASA). Conway’s law was avoided through the application of Agile and Lean approaches and many of the common challenges that ‘waterfall’ (sequential) project lifecycles incur at the end stages were also avoided by seeking early agreement on the client’s requirements and continuous review/feedback at the completion of each ‘sprint’. Conway’s law suggests that: “organizations which design systems … are constrained to produce designs which are copies of the communication structures of those organizations.” (Conway, 1968). In addition, some customers have technical management plans and expectations that the project’s SEMP integrate with customer plans and activities. This page was last edited on 13 October 2020, at 14:19. NASA. Care to join us in doing purposeful, sustainable work that helps shape communities and the future?…. Draft ConOps: The objective was to develop a concept for the ‘to-be’ system (or future state) jointly with users, stakeholders, and engineering staff, to identify and evaluate the gaps between the ‘as-is’ and ‘to-be’ states, and to brief decision-makers on the ConOps and gain acceptance of the principles and requirements captured within it. These sources describe the importance of understanding the scope of the work at hand, how to plan for critical activities, how to manage efforts while reducing risk, and how to successfully deliver value to a customer. Notably, the ConOps project team took the approach of delivering incremental versions of the ConOps document to the client at the end of each ‘sprint’ period (in accordance with the Agile product development methodology). Stay up to date with our latest global news, events, awards and more. This enabled the completed ConOps to be delivered, including sign-off approvals, within a timescales of 14 weeks; considerably shorter than typical ConOps production. The handbook is a recent detailed source for a frame-work to SEM and its applicati on for various types of systems. Agile and Lean methodologies contributed to keeping the stakeholders engaged in getting feedback early and often and incorporating it into the next ConOps increment. While there is no standard relationship, the project manager and the systems engineer encompass the technical and managerial leadership of a project between them, which requires the enterprise of each project manager and system engineer to work out the particular details for their own context. On other projects, there may be shared responsibilities for planning and managing activities. Forsberg, K., H. Mooz, and H. Cotterman. CMMI for Development: Guidelines for Process Integration and Product Improvement, 3rd ed. This often results in stovepipe (silo-engineered) designs that run into significant challenges during integration, verification and validation, transitioning into operation, and client acceptance. Managing and Leading Software Projects. Agile and Lean product development management principles (see Figure 1) were combined with standard project management processes and tools in order to develop the ConOps document. Project Management Institute (2012). The SEMP is the master planning document for the systems engineering technical elements. From developing and defending basis of estimates, planning and monitoring technical activities, identifying and mitigating technical risk, and identifying and including relevant stakeholders during the life of the project, the systems engineer becomes a key member of the project’s management and leadership team. 2009. PMI. The PCS monitors and controls the remote electrical plant located in traction power substations (TPSS) and circuit breaker houses (CBH) that supply traction power to the railway. 2007. The project combined and tailored elements of the following into an integrated project management approach: Project Management Institute’s PMBOK (Project Management Body of Knowledge) Guide, International Council on Systems Engineering (INCOSE) Systems Engineering Handbook (SEH), ‘Scrum’ as the Agile Product Development Framework, and the Lean Product Development Flow Method (Figure 1). A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 5th ed. It describes all activities, including technical activities, to be integrated and controlled during the life of the program. Pre-Final ConOps: The objective was to evaluate the gaps between the ‘as-is’ and ‘to-be’ systems, and develop a migration strategy for seamless deployment of the upgraded power control system, and to provide a complete set of system and process requirements for inclusion in the PCS specification. Best project management and systems engineering practices in the preacquisition phase for federal intelligence and defense agencies. 2005. Lead Author: Richard Turner, Contributing Author: Alice Squires. (2008). In some cases, particularly for smaller projects, the project manager may also be the lead technical member of the team performing both roles of project manager and systems engineer. With more than 500 offices throughout the…. A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 5th ed. 2013. In-Progress ConOps: The objective was to define the boundary of the PCS system-of-interest (SoI) and to understand and describe the ‘as-is’ system architecture, users, functions, and capability. The Project Management Plan (PMP) and the Systems Engineering Management Plan (SEMP) are key documents used to define the processes and methodologies the project will employ to build and deliver a product or service. The Third Edition of Essentials of Project and Systems Engineering Management enables readers to manage the design, development, and engineering of systems effectively and efficiently. Two major industry-recognized standards exist that outline the ConOps structure: ANSI/AIAA Guide to the Preparation of Operational Concept Documents (ANSI/AIAA-G-043) and the IEEE Guide for Information Technology-System Definition-Concept of Operations Document (IEEE-1362) (see Figure 3).