Scope of Project Mr.

Atul Anil Aphale

The project scope is the description of the work to be performed and completed on a project. Project scope management process: 1. 2. 3. 4. 5. Project scope initiation Scope Planning Scope definition Scope verification Scope change control

1. Initiation: beginning a project or continuing to the next phase 2. Scope planning: developing documents to provide the basis for future project decisions 3. Scope definition: subdividing the major project deliverables into smaller, more manageable components. 4. Scope verification: formalizing acceptance of the project scope 5. Scope change control: controlling changes to project scope Project Planning: Project planning is part of project management, which relates to the use of schedules such as Gantt charts to plan and subsequently report progress within the project environment. Project planning is a discipline for stating how to complete a project within a certain timeframe, usually with defined stages, and with designated resources. Initially, the project scope is defined and the appropriate methods for completing the project are determined. Following this step, the durations for the various tasks necessary to complete the work are listed and grouped into a work breakdown structure.

1. Statement of Work: The statement of work is narrative description of the work to be accomplished. It includes the objectives of the project, a brief description of the project, the funding constraints if any, and the specifications and schedule. The complexity of the sow is determined by desires of the top management, the customer, and / or the user groups. For project internal to the company, the sow is prepared by the project office with input from user groups because the project office is usually composed of personnel with writing skills. For project external to the organization, as a competitive bidding, the contractor may have to prepare the sow and submit to customer. Areas that are typically addressed by a SOW are as follows:

Purpose: Why are we doing this project? This is the question that the purpose statement attempts to answer. Scope of Work: This describes roughly the work that must be done in detail and specifies the hardware and software involved and the exact nature of the work to be done. Location of Work: This describes where the work must be performed. This also specifies the location of hardware and software and where people will meet to perform the work. Period of Performance: This specifies the allowable time for projects, such as start and finish time, number of hours that can be billed per week or month, where work is to be performed and anything else that relates to scheduling. Deliverables Schedule: This part lists the specific deliverables, describing what is due and when. Applicable Standards: This describes any industry specific standards that need to be adhered to in fulfilling the contract. Acceptance Criteria: This specifies how the buyer or receiver of goods will determine if the product or service is acceptable, what objective criteria will be used to state the work is acceptable. Special Requirements: This specifies any special hardware or software, specialized workforce requirements, such as degrees or certifications for personnel, travel requirements, and anything else not covered in the contract specifics. Type of Contract/Payment Schedule: The project acceptance will depend on if the budget available will be enough to cover the work required. Therefore

payments breakdown whether up front or phased will be negotiated very early at this stage. Miscellaneous: There are many items that do not form part of the main negotiations but are nonetheless very important to the project. They seem minor but being overlooked or forgotten could pose problems for the project..

2. Project Specifications: A Project Specification (or spec) is a comprehensive description of objectives for a development of project. It contains all goals, functionality, equipment and material estimates required for a development team to fulfill the vision of the customer. Common Elements for Project Specifications: The following are often included in project specifications: a. Introduction - description of project b. Project Objectives c. Site User Roles - what types of roles will site users have (guest, editor, admin, etc) d. Functional Requirements Per User Role e. Design Specifications - how with things look visually f. Flow or Logic Diagrams - for non-trivial processes like checkout or applications g. Success Criteria h. Site Map i. Content Plan - where will content come from j. Marketing Plan - how will the site make money k. Site Maintenance - who will maintain the site l. Project Phases / Timeline m. Budget

3. Milestone Schedules: The milestone schedule provides an estimated timeline for the life of the project. The milestones include all project activities and interim steps needed to implement the project. The schedule should include milestones for the planning, development, construction, evaluation and reporting of the projects implementation. The milestone dates are only projected dates based on an anticipated grant award. Those dates may change depending on the timing of the grant award.

simplified milestone schedule for various phases of an AMD project:

Duration Quarters Task list Pre-construction sampling Surveying and engineering Permitting Construction Post-construction sampling

2012

2013

2014

2015

1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

4. Work breakdown structure: Purpose: To plan a project, the total scope of work must be: identified subdivided into manageable segments assigned to individuals responsible to do the work documented

Definition: The WBS is a deliverable-oriented hierarchy of decomposed project components that organises and defines the total scope of the project. The WBS is a representation of the detailed project scope statement that specifies the work to be accomplished by the project. WBS is a hierarchical decomposition of the project into phases, deliverables and work packages. It is a tree structure, which shows a subdivision of effort required to achieve an objective. Developing the WBS: Divide the total work of the project into major groups...

...then subdivide these groups into tasks... ...then divide these tasks into sub-tasks Subtasks should be small enough to permit adequate control and visibility ,But avoid excess bureaucracy Read Kerzner, p.n. 415 onwards.. In project management, a work package (WP) is a subset of a project that can be assigned to a specific part for execution. Because of the similarity, work packages are often misidentified as projects. WP is a Software Development term