subject: project management

Please help me make a scope for the project named Online Blogging

1.1: Purpose: The primary function of this blogging site is to allow people to write blogs and earn some money. This will create a platform for all users to write their own blogs of their interesting topics. The other purpose is to create an earning platform for everyone. An online platform where anyone can share their knowledge of interesting facts and earn money from them.

The instructions related to planning of scope are given below. Please review this and make scope accordingly.

Scope Planning

1. Project scope document

Notes:

Project Constraints**

Project Constraints are limitations placed upon theproject that the project manager and team mustwork within.If constraint changes,there is most likely impact on the other constraints

1. Resources e.g. unavailability of skilled & competent Human Resources

• You must work within the available resources

2. Budget Sponsor imposed funding limits

• The total cost must not exceed $500.000

3. Scope e.g. work as defined in Contract

• Delivery of a number of features/project deliverables has to be done
• Make sure no extra work is added during project planning

4. Schedule e.g. Customer imposed completion dates

• You must finish 25% of the project work within 30 days
• The project has to be finished in 4 month

2. Work breakdown structure

Define a Work Breakdown Structure (WBS) to specify the various work activities to be performed in the project, and to depict the relationships among these work activities.The WBS can be created as an indented numbered list or in chart form. Show at least 4 levels with level 0 as the project name. Do not produce the draft WBS in MS Project.

The WBS should be deconstructed to a level that identifies individual work packages for each specific deliverable listed in the project scope document.

Break up your project into logical, major components. Once you have the first level of the WBS complete, break down each top level components. Continue to breakdown each of the components of the WBS until the task can no longer be logically subdivided. The final component should be small enough to easily estimate the time, cost and resources the task will require.

Specify the necessary resources.

Refer to Chapter 4 p. 113 in the text book (Project Management: The Managerial Process, 8th Edition

Erik Larson & Clifford Gray ISBN: 9781260884869

)

Chose either graphic chart format or indentured list format WBS template.

Project Roles and ResponsibilitiesAs the project team begins to form, it is important for project team members to know their role and what is expected of them.

This information is documented in a Project Roles and Responsibilities document.

Refer to Chapter 4pg. 123 for a sample Responsibility Matrix.

PROJECT SCOPE STATEMENT
Project Name	[This section contains the project name that should appear consistently on all project documents. Organizations often have project naming conventions.]
Date Produced	[The date the Project Charter is produced.]
Project Justification:	[The business need that the project was undertaken to address. The project justification provides the basis for evaluating future trade-offs]
Product Description:	[A brief summary of the product description]
Statement of Work	[Define the major tasks what will need to bee performed to accomplish the work that needs to be done and produce all the project deliverables. If something is not included in the Statement of Work (SOW), then it should be assumed that it will not be done or provided (see page 108 of the textbook)]
Project Deliverables [A list of the summary-level sub products whose full and satisfactory delivery marks completion of the project]
Project Exclusions [Indicate anything that will not be included in the scope of the project.]
Project Acceptance Criteria [include performance requirements and essential conditions, which must be met before project deliverables are accepted (PMBOK Guide). They set out the specific circumstances under which the user will accept the final output of the project. They are criteria that we can measure, achieve, and prove to our clients that our work is complete. Ex.: All permissions / licences obtained. Sponsor approved the event itinerary one month before the event. All requirements have been formally approved.
Project Assumptions *
[A list of the overall assumptions that are known at this point in the project.] Assumptions (State all factors that are, for planning purposes, considered to be true, real, or certain but without including proof. These assumptions will be validated during the planning process. If any are inaccurate, inconsistent, or incomplete, they will result in project risks. Add rows as required)
Project Constraints **
[A list of the overall constraints that are known at this point in the project.] Constraints (Identify the specific constraints or restrictions that limit or place conditions on the project, especially those associated with the project scope (e.g. a deadline, a budget, a set milestone, contract provisions, and privacy or security considerations)