Software Project Management Pl Good Eats Inc
Software Project Management Plan
December 14, 2013 CMIS330
Table of Contents
6.0 References 14
Software Project Management Plan
1. Overview
1.1 Project Summary
1.1.1 Purpose, scope and objectives
1.1.1.1 Background
Good Eats Inc. required a system be developed that would be utilized by the local stores, regional warehouses, suppliers and the corporate headquarters of Good Eats Inc. Good Eats ERP provides an inventory control system at each store that is linked to both regional warehouses, and corporate headquarters. This will track the sale of every item in every store and online storefront, as well as all items in the regional warehouses. The system …show more content…
5.5.2.3 Management or marketing insists on technical decisions that lengthen the schedule
5.5.2.4 Budget cuts upset project plans
5.5.3 Development environment
5.5.3.1 Facilities are not available on time
5.5.3.2 Facilities are crowded, noisy, or disruptive
5.5.3.3 Development tools are not in place by the desired time
5.5.3.4 Development tools do not work as expected; developers need time to create workarounds or to switch to new tools
5.5.4 End-users
5.5.4.1 End-user insists on new requirements
5.5.4.2 End-user ultimately finds product to be unsatisfactory, requiring redesign and rework
5.5.4.3 End-user does not buy into the project and consequently does not provide needed support
5.5.4.4 End-user input is not solicited, so product ultimately fails to meet user expectations and must be reworked
5.5.5 Customer
5.5.5.1 Customer insists on new requirements
5.5.5.2 Customer review/decision cycles for plans, prototypes, and specifications are slower than expected
5.5.5.3 Customer will not participate in review cycles for plans, prototypes, and specifications or is incapable of doing so—resulting in unstable requirements and time-consuming changes
5.5.5.4 Customer communication time (e.g., time to answer requirements-clarification questions) is slower than
December 14, 2013 CMIS330
Table of Contents
6.0 References 14
Software Project Management Plan
1. Overview
1.1 Project Summary
1.1.1 Purpose, scope and objectives
1.1.1.1 Background
Good Eats Inc. required a system be developed that would be utilized by the local stores, regional warehouses, suppliers and the corporate headquarters of Good Eats Inc. Good Eats ERP provides an inventory control system at each store that is linked to both regional warehouses, and corporate headquarters. This will track the sale of every item in every store and online storefront, as well as all items in the regional warehouses. The system …show more content…
5.5.2.3 Management or marketing insists on technical decisions that lengthen the schedule
5.5.2.4 Budget cuts upset project plans
5.5.3 Development environment
5.5.3.1 Facilities are not available on time
5.5.3.2 Facilities are crowded, noisy, or disruptive
5.5.3.3 Development tools are not in place by the desired time
5.5.3.4 Development tools do not work as expected; developers need time to create workarounds or to switch to new tools
5.5.4 End-users
5.5.4.1 End-user insists on new requirements
5.5.4.2 End-user ultimately finds product to be unsatisfactory, requiring redesign and rework
5.5.4.3 End-user does not buy into the project and consequently does not provide needed support
5.5.4.4 End-user input is not solicited, so product ultimately fails to meet user expectations and must be reworked
5.5.5 Customer
5.5.5.1 Customer insists on new requirements
5.5.5.2 Customer review/decision cycles for plans, prototypes, and specifications are slower than expected
5.5.5.3 Customer will not participate in review cycles for plans, prototypes, and specifications or is incapable of doing so—resulting in unstable requirements and time-consuming changes
5.5.5.4 Customer communication time (e.g., time to answer requirements-clarification questions) is slower than