Deliverable #5

Deliverable #5 project manager: Lauren Vance

Worldwide Sports Online Site Scope Management Plan

The focus of this project taken on by LEMM Solutions is to find and implement a system to improve and increase customer relations for Worldwide Sports. Worldwide Sports is a company that serves its community with sports equipment for many of the local teams. They have been the best in town and there have been customers from other areas inquiring about the products. The improvements to the system will allow them to interact with more customers across further distances.

MOV

To implement a software system that is custom developed to help Worldwide Sports improve

·         Customer base

·         Sales

·         Inventory

·         Shrinkage

These improvements to the current site will give a 50% increase in sales in the first year.

Deliverable Structure Chart (DSC)

Definition Table

Deliverable	Structure	Standards	Approval Needed By	Resources Required
Project Charter	Document	Signed and agreed on by all team members	Project sponsor, project team	Business case team and Office 365
MOV/Alternative Analysis	Document	Reviewing all alternatives to make the best decision	Project sponsor	Project manager and sponsor and Office 365
Resource Analysis	Document	Determining what resources we have/need	Project manager and project sponsor	LEMM solutions and Office 365
Stakeholder Analysis	Document	Reviewing all impacts of stakeholers	Project manager	Systems analyst, potential users, and Office 365
DSC, DDT, and Use Case Diagram	Prototype	As defined in user interface guidelines	Project sponsor	System analyst, programming team, potential users, and Office 365
Physical and technical design	Prototype of the system	Basic functionality is met	Project manager and project sponsor	System analyst, programming team, and Office 365
Application system	Files on the server	As defined in project methodology	Project sponsor	Programming team, system analysts, network managers, programming development tools, and Visual Basic
Scope Change and Request	Document	As defined in project methodology	Project manager	System analysts and Office 365
WBS	Document	Use of the 100% rule	Project manager	Programming team, system analyst, and Office 365
Change management and implementation plan	Document	As defined in project methodology	Project manager	System analyst and Office 365
Risk Analysis/Plan	Document	As defined in implementation plan	Project manager and project sponsor	Trainers, trainees, secretary, and Office 365
Financial report and presentation	Document	As defined in project methodology	Project sponsor	Project sponsor, project manager, and Office 365
Project evaluations and lessons learned	Document	As defined in project methodology	Project manager and senior	Project team and knowing the whole system

 
Use Case Diagram (Visio)

Scope Definition

The Deliverable Definition Table (DDT) shows all of the planned deliverables in the different progressions of our project. The MOVers are responsible for making sure that each of our deliverables are completed on track of the schedule. Any deliverables that might be added at a later date by Worldwide Sports are not included in the original scope of the project. Any change in functionality requires a change to the scope of the project and effects the budget and schedule as well.

The Use Case Diagram describes what functionality will be developed into our custom software that is being created. The MOVers make sure that all of the functionality will be added correctly into the software and that it is completed on time.

Scope Verification

Of the functions mentioned in the Use Case Diagram, all are requirements of the MOV and will be satisfied in our project. The final software package with these listed functions will ensure its correctness.

Milestones

Once a deliverable from the DDT is completed and documented correctly, it will be then considered a milestone of the project. Worldwide Sports will make sure that it is functional and comprehensive of the scope before signing off on its completion. Once the deliverable is signed off on and is considered a completed milestone, our team will begin working on the next deliverable to be finished.

Scope Change Process

 During the course of the project, somewhere along its completion there will need to be changes for any number of reasons. It is important to be prepared for such changes and to document them correctly, in an organized fashion. The most common changes that need to be made deal with changes in scope and functionality.

As soon as a change is requested, Worldwide Sports will contact us to discuss and document all details. Worldwide Sports is well aware that any change in scope includes changing the budget and schedule as well. It will also be documented below whether the change is negative or positive.

Of all the changes to be requested, only high priority, positive changes will be considered. The change has to be positive and highly important to both Worldwide Sports, LEMM Solutions, and all MOVers. When addressing any change in scope, the changes, negative or positive, will be documented for the schedule and budget as well.

Scope Change Process

Also, once a request is documented by Worldwide Sports or LEMM Solutions, alternatives must be mentioned upon request. Worldwide Sports has the final say whether the change will be executed or not to the project. One party may not request, document, and execute a change in scope without all other party approval and consideration.

The following is the Scope Change Request Form and the Scope Change Request Log, both of which must be fully completed for a change to have consideration.     

Scope Change Request Form

Scope Change Request Form

Requestor Name:          ______________            Request Date: ­­_________

Request Title: _____________________                        Request Number:  _______

Request Description:

Justification:

Possible Alternatives:

Impacts	Alternative I	Alternative II	Alternative III	Worldwide Sports Online Site
Scope
Schedule
Budget
Resources

Recommendation:

Authorized by:

Date:

All changes requested should be logged for future reference and to monitor the quality of work being performed. Multiple change requests would indicate a problem with the original scope definition. The following is the format of the log to track scope changes.

 Scope Change Request Log

Notation:

LP - for low priority

MP - for medium priority

HP - for high priority

Request Number	Request Title	Date of Request	Requestor	Priority (LP, MP, HP)	Authority to approve request	Expected Response Time	Scope Change Approved? (Yes or No?)

Conclusion

With this document, we have defined the scope of the project. It includes the various deliverables and functions that the application has to have to be developed. This will serve as a guide to what the expectations of the website are and the various steps in the project needed to meet those expectations.