Huntsville Case Study
Project Name | Huntsville Project | Project Number | 1 | Project Manager | Janet Clark | Prioritization | | Owner(s) | SEITZ Corporation | Start Date: | April 17, 2009 | Scheduled Completion Date: | June 30, 2010 |
Mission | To gain second position in market share in southeast region | | Scope | Construction of a new plant in Huntsville, Alabama in order to reduce the cost of transportation to the markets in the region | | Objectives | To build a new plant in Huntsville, Alabama for $2. 75 million and accomplish first shipment of the product by June 30, 2010. | | Assumptions | * Required technical staff for the new plant will be recruited from the internal and external sources * Funding for the project will be ready for immediate use * The new …show more content…
technology prototype will be ready to be used in the new plant * | | Constraints | * Technical staff needed for the new plant may not be willing to relocate from Milwaukee to Alabama * Required permits for construction might not be completed in time | | Time/Decision Points | Define key events which usually represent a significant deliverable.
They may be process indicators, decision gates, funding decision points or other significant phases. In this section, document key events, decision gates. Start and end dates are helpful. This section is also a good place to document important information pertaining to dates. For instance, if an end date is required by an FCC regulation, that fact should be documented here along with the end date. | | Cost/Financial Assumptions | Usually information from the feasibility analysis. Answers funding questions. Information for this section usually comes from the feasibility analysis. In this section outline life cycle costs and revenues. The purpose of this section is to help determine if pursuing this project makes corporate sense. It is NOT the Project Budget. The project budget will be created in the Project Plan. | | User Acceptance Criteria/Quality | Basis for quantifying quality. Use this section to communicate how the project team can insure that they will provide a product that not only meets the specifications, but also successfully addresses all quality criteria. |
| Major Risks | Define risk events which can affect the project’s success. In this section, define any event, which can affect the project’s success. These events can affect the project negatively OR positively. Defining positive risks can help teams focus on ways to optimize opportunities | |
KEY STAKEHOLDERS | | Name | Project Core Team: | | Subject Matter Experts (SME) (Include company & channel designations if applicable) | | APPROVALS | Type Name | Signature | Date | Project Manager Approval: | | | Owner/Sponsor Approval: | | |
Mission | To gain second position in market share in southeast region | | Scope | Construction of a new plant in Huntsville, Alabama in order to reduce the cost of transportation to the markets in the region | | Objectives | To build a new plant in Huntsville, Alabama for $2. 75 million and accomplish first shipment of the product by June 30, 2010. | | Assumptions | * Required technical staff for the new plant will be recruited from the internal and external sources * Funding for the project will be ready for immediate use * The new …show more content…
technology prototype will be ready to be used in the new plant * | | Constraints | * Technical staff needed for the new plant may not be willing to relocate from Milwaukee to Alabama * Required permits for construction might not be completed in time | | Time/Decision Points | Define key events which usually represent a significant deliverable.
They may be process indicators, decision gates, funding decision points or other significant phases. In this section, document key events, decision gates. Start and end dates are helpful. This section is also a good place to document important information pertaining to dates. For instance, if an end date is required by an FCC regulation, that fact should be documented here along with the end date. | | Cost/Financial Assumptions | Usually information from the feasibility analysis. Answers funding questions. Information for this section usually comes from the feasibility analysis. In this section outline life cycle costs and revenues. The purpose of this section is to help determine if pursuing this project makes corporate sense. It is NOT the Project Budget. The project budget will be created in the Project Plan. | | User Acceptance Criteria/Quality | Basis for quantifying quality. Use this section to communicate how the project team can insure that they will provide a product that not only meets the specifications, but also successfully addresses all quality criteria. |
| Major Risks | Define risk events which can affect the project’s success. In this section, define any event, which can affect the project’s success. These events can affect the project negatively OR positively. Defining positive risks can help teams focus on ways to optimize opportunities | |
KEY STAKEHOLDERS | | Name | Project Core Team: | | Subject Matter Experts (SME) (Include company & channel designations if applicable) | | APPROVALS | Type Name | Signature | Date | Project Manager Approval: | | | Owner/Sponsor Approval: | | |