MET 470 Lecture 7: MET 470 lecture notes (7)
22 May 2018
School
Department
Course
Professor
Planning Stages
1. Proposal State
2. Start up (-plan who will work on the project, how the project will be broken down into increments,
how resources will be allocated across your company.)
3. Throughout project - modify plan as needed
Plan Driven Development
1. Development Process is planned in detail
2. Plan that records the work to be done, who will do it, and the schedule and the products
3. Managers use the plan to support project decision making as a way of measuring progress
Project Plans
Typical sections of a plan:
1. Introduction
2. Project Organization
3. Risk Analysis (what can go wrong)
4. Hardware and software resource requirements
5. Work Breakdown
6. Project Schedule
7. Monitoring and reporting mechanisms
Configuration Management Plan
Describes the configuration management procedures and structures to be used.
Deployment Plan
Describes how the software and associated hardware (If required) will be deployed in the customer's
environment. This should include a plan for migrating data from existing systems.
Maintenance Plan
Predicts the maintenance requirements, costs, and effort
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Planning stages: proposal state, start up (-plan who will work on the project, how the project will be broken down into increments, how resources will be allocated across your company. , throughout project - modify plan as needed. Typical sections of a plan: introduction, project organization, risk analysis (what can go wrong, hardware and software resource requirements, work breakdown, project schedule, monitoring and reporting mechanisms. Describes the configuration management procedures and structures to be used. Describes how the software and associated hardware (if required) will be deployed in the customer"s environment. This should include a plan for migrating data from existing systems. Describes the quality procedures and standards that will be used in a project. Describes the approach, resources, and schedule used for system validation. An iterative process that starts when you create an initial project plan during the project start up phase.
