Development Projects / Analysis Projects / On-site Service Projects

Development Projects / Analysis Projects / On-site Service Projects
Planning Requirements Analysis Design Test Delivery << Start over

Overview Project Planning  2.1 Requirements Development 5.1 Risk Id, Analysis , & Prioritization Configuration Management  7.1 Supplier Management 8.1 Decision Analysis & Resolution Templates Training Development Planning Requirements Analysis Design Test Delivery << Start over

Overview Project Planning  2.1 Requirements Development 5.1 Risk Id, Analysis , & Prioritization Configuration Management  7.1 Supplier Management 8.1 Decision Analysis & Resolution Templates Training Development Planning Requirements Analysis Design Test Delivery 1.1 Project Planning 1.1.1 Project Estimating 1.1.2 Project Scheduling << Start over

Overview Project Planning  2.1 Requirements Development 5.1 Risk Id, Analysis , & Prioritization Configuration Management  7.1 Supplier Management 8.1 Decision Analysis & Resolution Templates Training Development Planning Requirements Analysis Design Test Delivery 6.1 CM Plan Definition 6.1.1 Identify Project Baselines 6.2 Create and Release Baselines << Start over

Overview 3.1 Preliminary Technical Design 3.2 Detailed Technical Design 2.1 Requirements Development 8.1 Decision Analysis & Resolution Templates Training Development Planning Requirements Analysis Design Test Delivery << Start over

Before beginning the Design Phase, the Project Planning Checklist and Requirements Checklist must be completed. OK Development Projects / Analysis Projects / On-site Service Projects Overview 3.1 Preliminary Technical Design 3.2 Detailed Technical Design 2.1 Requirements Development 8.1 Decision Analysis & Resolution Templates Training Development Planning Requirements Analysis Design Test Delivery << Start over

Project Planning Project planning is the critical first step in managing and controlling a successful project. Planning begins with requirements that define the product and project. The project plan provides the basis for performing and controlling the project’s activities that address the commitments with the project’s customer. The project plan will usually need to be revised as the project progresses to address changes in requirements and commitments, inaccurate estimates, corrective actions, and process changes. Successful project planning involves activities from 6 different process areas, as listed below. Click on the individual activities to see the procedures. You may also click here to see a list of templates that will be useful, or here to see the training materials available to guide you through the processes. Process Areas: 1.1 Project Planning 1.1.1 Project Estimating 1.1.2 Project Scheduling 2.1 Requirements Development 5.1 Risk Identification, Analysis, and Prioritization 6.1 Identify Project Baselines 6.1.1 Create and Release Baselines 7.1 Supplier Agreement Management 8.1 Decision Analysis and Resolution From: Chrissis, Mary Beth, Konrad, Mike, & Shrum, Sandy (2007). CMMI: Guidelines for Process Integration and Product Improvement (2nd ed.). Boston: Addison-Wesley. Project planning: involves developing the plan, interacting with stakeholders, getting commitment, and maintaining the plan. Begins with requirements that define the product and project, and includes: 1) estimating the attributes of the work products & tasks; 2) determining resources needed; 3) negotiating commitments; 4) producing a schedule; & identifying and analyzing project risks. (often an iterative process.) Project plan provides the basis for performing and controlling the project’s activities that address the comitments with the project’s customer. Usually revised as the project progresses. Once you have completed the Project Planning Phase, be sure to complete the Project Planning Checklist before continuing! < Back to Analysis Project screen << Start over

Requirements Analysis
Requirements are the basis for design. There are three types of requirements: customer requirements, product requirements, and product component requirements. Taken together, these requirements address the needs of relevant stakeholders, including those pertinent to various product lifecycle phases (e.g., acceptance testing criteria) and product attributes (e.g., safety, reliability, and maintainability). Requirements also address constraints caused by the selection of design solutions (e.g., integration of commercial off-the-shelf products). The analysis and management of requirements is specified in three procedural scripts. Click on the individual scripts below to see the procedures. You may also click here to see a list of templates that will be useful, or here to see the training materials available to guide you through the processes. Procedural Scripts: 2.1 Customer Requirements Development 2.2 Product Requirements Development 2.3 Requirements Management ? From: Chrissis, Mary Beth, Konrad, Mike, & Shrum, Sandy (2007). CMMI: Guidelines for Process Integration and Product Improvement (2nd ed.). Boston: Addison-Wesley. Project planning: involves developing the plan, interacting with stakeholders, getting commitment, and maintaining the plan. Begins with requirements that define the product and project, and includes: 1) estimating the attributes of the work products & tasks; 2) determining resources needed; 3) negotiating commitments; 4) producing a schedule; & identifying and analyzing project risks. (often an iterative process.) Project plan provides the basis for performing and controlling the project’s activities that address the comitments with the project’s customer. Usually revised as the project progresses. < Back to Analysis Project screen << Start over

Requirements Analysis
Requirements are the basis for design. There are three types of requirements: customer requirements, product requirements, and product component requirements. Taken together, these requirements address the needs of relevant stakeholders, including those pertinent to various product lifecycle phases (e.g., acceptance testing criteria) and product attributes (e.g., safety, reliability, and maintainability). Requirements also address constraints caused by the selection of design solutions (e.g., integration of commercial off-the-shelf products). The analysis and management of requirements is specified in three procedural scripts. Click on the individual scripts below to see the procedures. You may also click here to see a list of templates that will be useful, or here to see the training materials available to guide you through the processes. Procedural Scripts: 2.1 Customer Requirements Development 2.2 Product Requirements Development 2.3 Requirements Management ? Have all applicable checklists been completed before continuing to this phase? From: Chrissis, Mary Beth, Konrad, Mike, & Shrum, Sandy (2007). CMMI: Guidelines for Process Integration and Product Improvement (2nd ed.). Boston: Addison-Wesley. Project planning: involves developing the plan, interacting with stakeholders, getting commitment, and maintaining the plan. Begins with requirements that define the product and project, and includes: 1) estimating the attributes of the work products & tasks; 2) determining resources needed; 3) negotiating commitments; 4) producing a schedule; & identifying and analyzing project risks. (often an iterative process.) Project plan provides the basis for performing and controlling the project’s activities that address the comitments with the project’s customer. Usually revised as the project progresses. < Back to Analysis Project screen << Start over

< Back to Analysis Project screen << Start over

Overview 2.1 Customer Requirements Development 2.2 Product Requirements Development 2.3 Requirements Management Verification and Validation  Templates Training Development Planning Requirements Analysis Design Test Delivery << Start over

Overview 2.1 Customer Requirements Development 2.2 Product Requirements Development 2.3 Requirements Management Verification and Validation  Templates Training Development Planning Requirements Analysis Design Test Delivery 4.1.1 Verification Planning 4.2.1 Validation Planning 1.1.2 Project Scheduling << Start over

<< Start over

Templates* Project Plan (contains WBS, Stakeholder List, Project Resources, Project Processes and Standards, & Training Requirements) Requirements Specification Project Budget Plan Project Tracking File Configuration Management File From: Chrissis, Mary Beth, Konrad, Mike, & Shrum, Sandy (2007). CMMI: Guidelines for Process Integration and Product Improvement (2nd ed.). Boston: Addison-Wesley. All development projects have requirements (maintenance projects – any changes to product or components is based on changes to existing requirements, design or implementation. ) Activities include: 1) elicitation, analysis, validation, and communication of customer needs, expectations, and constraints to obtain cust reqts that constitute an understnading of what will satisfy stakeholders; 2) collection and coordination of stakeholder needs; 3) development of lifecycle reqts of the product; 4) establishment of customer reqts; 5) establishment of initial product and produt compnent reqts consistent with customer reqts. Customer needs can prescribe particular solutions in addition to describing the problem to be solved. As long as they continue to be maintained, reqts provide value to those supporting the product throughout its life. Stakeholder needs are rarely communicated in an official document – communicated in documentation, conversations, meetings, demonstrations, etc. Must be translated into reqts that the project and the customer can agree to. Rarely does a customer know exactly what he/she wants – plan for an iterative process. (Ask what the product must do and how it will behave. Also determine what is reqd to produce it, license, install, train end users, maintain, migrate to new versions, support, retire, and dispose of it.) < Back to Analysis Project screen << Start over * For testing purposes this is not an exhaustive list …

Your choice will open the Project Plan template.
< Back to Analysis Project screen << Start over

Planning Requirements Analysis Performance Delivery << Start over

Overview Project Planning  2.1 Requirements Development 5.1 Risk Id, Analysis , & Prioritization Configuration Management  7.1 Supplier Management 8.1 Decision Analysis & Resolution Templates Training Development Projects / Analysis Projects / On-site Service Projects Planning Requirements Analysis Performance Delivery < Back to Analysis Project screen << Start over

Overview Project Planning  2.1 Requirements Development 5.1 Risk Id, Analysis , & Prioritization Configuration Management  7.1 Supplier Management 8.1 Decision Analysis & Resolution Templates Training Development Projects / Analysis Projects / On-site Service Projects 1.1 Project Planning 1.1.1 Project Estimating 1.1.2 Project Scheduling Planning Requirements Analysis Performance Delivery < Back to Analysis Project screen << Start over

Overview Project Planning  2.1 Requirements Development 5.1 Risk Id, Analysis , & Prioritization Configuration Management  7.1 Supplier Management 8.1 Decision Analysis & Resolution Templates Training Development Projects / Analysis Projects / On-site Service Projects Planning Requirements Analysis Performance Delivery 6.1 CM Plan Definition 6.1.1 Identify Project Baselines 6.2 Create and Release Baselines < Back to Analysis Project screen << Start over

Planning Performance Contract Close-Out << Start over

Development Projects / Analysis Projects / On-site Service Projects

Similar presentations

Presentation on theme: "Development Projects / Analysis Projects / On-site Service Projects"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Development Projects / Analysis Projects / On-site Service Projects

Similar presentations

Presentation on theme: "Development Projects / Analysis Projects / On-site Service Projects"— Presentation transcript:

Similar presentations

About project

Feedback