PJM6005 Final Paper

Introduction to the Scope Management Plan Template

·

Scope management refers the process of collections that makes sure that a particular project

The plan of the scope management offers scope frameworks in support of this project. The plan documents the approaches of scope management, roles and responsibilities pertaining to project scopes, definitions, verifications and measures of control. It touches on scope control changes, as well as work breakdown structures in support of the project.

The project will be helpful in the designing, programming as well testing fresh software products that shall be employed in tracking organizational finances as well as enhancing different process of finance in the company. This would incorporate designing software, doing programming together with coding. The project will assist in validation as well as testing the software created. In this project, there is not a single external resources otherwise outsourcing of materials which shall take place.

Management scope for this project shall be the sole duty of project manager. The project scope in this area is described by scope statements, Work Breakdown Structures (WBS) alongside the dictionary for the WBS. The sponsors, stakeholders together with project managers shall determine alongside approving documentation in support of quantifying project scopes. These will incorporate checklists for the deliverable qualities and measurements of work performance. The changes on the proposed scope might be started by the project managers, stakeholders otherwise team members of the project. All the requested changes will then be submitted to project manager for evaluation. When approved, the project manager will be task with updating every project document as well as communicate various changes of the scope to every stakeholder. Depending on the acquired feedback together with inputs from stakeholders and project managers, the sponsors of the project will be able to accept the project scopes and deliverables of the final project.

The project scope here was described via comprehensive process for the collection requirements. Firstly, complete analysis was done on the organizational present software application anchored on the feedbacks from the users and employees. Using this information, project team created requirements on the project documentation, requirements on plan management as well as demands for the traceability matrix in support of whatever new application ought to achieve.

The project deliverables and descripts were made anchored on collection process needs a well as the inputs acquired from the experts of the subject matters during the software designs, technical supports, programming as well as applications which are used in business. The expert judgment offered feedbacks on the effective approaches of meeting original requirements of offering platform for new software. The developed software will assist the company in improving financial tracking as well as process of internal financial operations.

Example: WBS Dictionary

[Insert Project Name]

When the project would be in progresses, project manager shall do verifications of the project deliverables versus original scopes just as outlined within the WBS dictionary, project statements, and WBS. As long as the project manager gives an authentication that the scope of the project is meeting the defined requirements within the plan in the project, the sponsor and project manager shall have a meeting in support of formal acceptance of the outlined deliverables. In the meeting, the project manager shall do a presentation on the project deliverability to the project sponsors so to get the project accepted formally. The sponsors of the project shall accept that the project is deliverable through signing the acceptable document. Appending the signature ensures that the project works stay within the scope required in the project life cycle.

The project teams and manager shall be working jointly in controlling project scopes. The team shall leverage WBS dictionary through utilizing it like a work statement in support of the elements in the WBS. The team shall make sure that all the described duties are executed within the WBS dictionary alongside generating defined deliverables in support of WBS features. Also, project manager shall supervise progression as well as project teams in ensuring all the scopes within the projects are followed. In case there is need to change the project scope, the change recommendations shall be followed. A sponsor or team member might request for a change of project scopes. The request shall be provided to project manager in the form of a document for change requisition of the project scope. It is the duty of the project manager to either deny or consent for the changes after convening a meeting with sponsors and project teams. When the project scope gets approval, a change request shall be passed to control board of change. In the event he controls board of change consent to such changes of the project scope, the sponsors will be required to sign a document for changing the scope.