Project Management I assignment

The  proposed assignment is to prepare a Statement of Work. This is a Project Management I course. I can also send additional information if necessary.
The first assessment requires you to have an understanding of the importance of project selection and of the various approaches used by organizations to prioritize projects.

  • Think about what your personal project will be and post your idea in the form of a statement of work (SOW) in the Assignments folder.  SOW examples can be found in the PMBOK 5.3.3. Project Scope Statement.
  • Here are two documents that will help in developing an SOW for your Project

Statement of Work
What It Is/What It Does
The purpose of a Statement of Work (SOW) is to establish a written contract for work to be performed, i.e., when and how. Use it to start a project effort or start a subsequent phase of a project. A project can have one or more SOWs.
The amount of work agreed to in a SOW should be the amount of work you can clearly describe. If the customer’s request is broad, complex, multi-organizational, or very large, use one SOW to cover early requirements gathering and analysis. Subsequent SOWs can cover design, development and implementation. You can use multiple SOWs for requests that spawn multiple projects. In this case, use one SOW for project investigation, then one SOW for each project that follows.

Project Name:
The project name that will consistently be used for discussing this project.
Project Sponsor:
The name of the person(s) from the business organization who has ultimate responsibility for defining and accepting results of this project.
Project Manager(s):
The name of the individual(s) responsible for managing the project.
Date of First Draft:
The mm/dd/yy that the SOW document was first circulated for review. This date never changes!
Latest Version No.:
Each time a change to the SOW is agreed upon by the project team, this version number is incremented by 1. Record the latest version number here.
Date Agreement Reached:
Enter the sign-off date for the original SOW.
Latest Revision Date:
The mm/dd/yy of the last update (version) to this document.
Background Information:
A summary of the need or problem expressed in business terms. Include a description of the chronology of events leading up to the request for service. State the specific business benefits that this project will provide. Identify any current manual or automated procedures involved.
Project Goal:
Indicate what specific goal exists for the project in support of a strategic business directive.
Scope Statement:
Summarize the key product or service this project will result in, the project duration, and the overall project budget.  Be concise with your scope statement, leaving no room for ambiguity.
Basic Approach:
What is the strategy by which a technical solution can be found? How will the options of build, buy, or reuse be analyzed and weighed? Are there any special technical circumstances that need to be taken into account when managing the technical aspects of this project? Will there be specialized methodologies needed? If the SOW covers multiple releases of functionality, describe that approach here.
Deliverables / Milestones:
List key summary tasks and deliverables for this SOW. Summary tasks should appear as major tasks on the project plan. Milestones are zero-duration actions or events marking a significant change or stage in development.Distinquish between the two.
Project Priority:
Clarify the project priority with respect to product performance (features), development cost (cost), and time-to-market (time).


Assumptions are conditions that you expect to be in place that pertain to the effort covered by this SOW. A constraint is a limiting condition, circumstance or event, setting boundaries for the project process and expected results. Exceptions are those items that are clearly out of scope but need mentioning.
Other:  Include any other information you feel supports the project scope or background. (Otherwise, remove this section)
Acceptance Procedure:
Provide measures of success that will be used to assess success. Measures of success should be stated in measurable and quantifiable terms. Clearly state the goal, not activities, in business terms. Establish the acceptance criteria for the project completion and the procedure for achieving customer acceptance.


Submit a Comment