Nyanya only

Project Scope Statement

New Soft development

Joseph Moore

8 November 2015

Introduction

This project is primarily designed to promote the significance of new software development to the companies. The purchasing business should possess’ long-term management preparation used for choosing, approving and upgrading software programs such as commercial off-the-shelf (COTS) and other software products that are reusable. If a mixture of these constituents is increased in the new systems, the demand continues to grow. The new software management plan and COTS usually help to facilitate the purchasing of new programs management of COTS and some of the reusable software. The project addresses how new COTS and reusable software will provide the strategy that outline data management about monitoring interdependency of software, tracking, choosing specific features and documenting those choices. The reusable software and COTS presented in this project functions as a guide for how to accomplish new software components and COTS in a complex system (Anderso, Smith, and Ward, 2007).

Project Purpose and Justification

The objective of this research is to help in identifying the techniques and collaborative processes in handling the new software components and to address the risks and other issues. The project also seeks to eliminate the baseless production of similar but different software components which are reusable across the organization and support the quantity discounts if possible. It describes the strategies for the program and approaches to managing and developing software components and COTS, which provide an origin for supporting roles and possesses. The project provides a summary of roles of the program that are affected by development plan and includes an overview of the operation that supports the software plan strategies. Furthermore, it ensures software development plan is implemented by describing the programs processes. Some of the activities that must be taken to address the risk and issues include identification of the components that can be shared across the software system and encourage their use (Anderso, Smith, and Ward, 2007).

Scope Description

This project seeks to justify the new development on the application of COTS solution. It also provides introductory information about COTS and new software programs and describes its relationship to other program plans (Anderso, Smith, and Ward, 2007). The anticipated deliverables include a new software program that needs to be written by exact deadline. It should be delivered in numbered phases. The first release will contain some new elements that will be present in final product. The training program, since the software program is new, there will be training design that tells the users how training on new software will be developed. After a task analysis, the training program is established and approved as the final deliverables. Finally, the accounting program processes are established to allow implementation of a program that is being created. The hardware is ordered and tested, the trainers are identified and implementation of new software according to due dates.

High Level Requirements

The work should be planned to utilize a project definition document. The time spent on the planning of the project will result in a reduction in cost and duration hence increases quality over the time of the project. Define the procedures of project management upfront. The procedure outlines all the resources that should be used in the management of the project. This include sections how the team will manage scope issues, risk, and communications. Finally manage the work plan and monitor the budget. Once the project has been properly planned the execution of the work begins (Kerzner, 2013).

Boundaries

This includes some of the techniques like tracking statement programs, checking software interdependency, selecting exact features and documenting those choices, assessing and alleviating the risks related to COTS and new software component in a system. The reusable software can be grouped into different categories of components; some of them include Shareware, Commercial off-the-shelf (COTS) and Government off-the-shelf (GOTS).

Strategy

The project team will use tradition approach. The strategy assumes that the scope of the project and goals will remain constant till the project ends. In this case, the project manager will plan and identify resources for the project based on this assumption. The tradition method lays down following stages:

1. Initiation of the project

2. Planning and designing the project

3. Monitoring and controlling of the project

4. Execution of the project

5. Completion of the project

Deliverables

1. A new software program that is written by the exact deadline, this should be delivered in numbered phases. The first release will contain some new elements that will be present in final product.

2. The training program, since the software program is new, there will be training design that tells the users how training on new software will be developed. After a task analysis, the training program is established and approved as the final deliverables.

3. Finally, the accounting program processes will be established to allow implementation of a program that is being created. The hardware is ordered and tested, the trainers are identified and implementation of new software according to due dates.

Acceptance Criteria

1. Improved information flow- this involves the flow information of from one step to another

2. Improved flow of the process- this involves systems improvement

3. Increased the quality of the product- this is the state of achieving desired output.

Constraints

1. Failure to manage projects with the unspecified schedule, the project management imposes deadline and budget on any project that creates major problems. When the project has to be finished in time and has schedule, its quality can be compromised.

2. Secondly dependence on the functional management, this is a major problem because project managers constantly work at the mercy of resources and functional managers.

3. Finally, an exclusive methodology, the project management forces the project manager to choose and follow methods be it tradition or agile.

Assumptions

1. Project schedule- this is a detailed description of the staffs action steps needed in project management.

2. Personnel recruitment and training is essential for personnel in the project team

3. Technical tasks- this is the availability of expertise and required technology to achieve the specific action steps.

4. Support from top management- the top management should be willing to provide necessary resources and authority of the power of the project success.

5. Communication- entails the provision of data and proper network to all key actors in the project management.

6. Troubleshooting- is the capacity to handle deviations from the plan and handle unexpected crises.

Risk Analysis and Mitigation Strategy

Types of risks

1. System or product complexity, this is how the project is complex and big

2. Team environment- the team makes an enormous difference to the success of the project. This risk needs careful consideration because it can break the project

3. Business project risk- if the project is moved to a new part that has not been not tried or verified. The risk is greater because it is about the aspect of the business not ending result.

Mitigation strategies

1. Restructure the project so as to minimize the impacts of early decisions on downstream conditions. Decisions that eliminate options and constrain future decisions should be reconsidered.

2. Stage the project so that it is always reviewed for no go decisions discrete and identifiable points. These plans must be constructed into front end plan.

3. Change the scope of the project, this should be either down or top, at some future decision points. In the high-uncertainty project, corrections may be necessary to improve the information.

Cost Estimate

Expense	Estimated Budget	Expended to Date	Estimate to Complete	Variance
Labor	$10000	7/11/2015	$11000
Internal	$7000	10/11/2015	$7500	$500
External	$3000	10/11/2015	$3500	$500
Software	$5000	22/11/2015	$5100	$100
Hardware	$6000	30/11/2015	$6200	$100
Other	$3000	12/12/2015	$3500	$500
Total	$24000		$$4200	$1800

References

Kerzner, H. R. (2013). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.

Anderso, W., Smith, D., & Ward, M. C. (2007, October). COTS and Reusable SoftwareManagement Planning: A Template forLife-Cycle Management. Retrieved October 2015, from software engineering institute: