AI

shanta75
Home>Homework Answsers>English homework help
AI
  • 2 years ago
  • 20
Report issue
files (2)

Unit4Assignment_ScopeStatement2ai.pdf

Due: Sunday by 11:59pm

Total Points: 100

Overview:

Instructions: Based on lecture materials for course thus far and the template provided on the next pages, create a scope statement for your individual case study project. As with earlier deliverables, use a business writing style where applicable, and do not assume the audience of this scope statement has read previous project documentation. HINT: this scope statement incorporates requirements documentation, which means you will list the requirements (project, technical and any regulatory requirements) for your case study project in this document. As we saw in course unit 3, writing requirements is challenging and could take some time! My hint is to start sooner rather than later. As with your other written assignments, this assignment is to be completed individually.

Requirements:

 Use the “Scope Statement Template Outline” template to complete the assignment

and submit to Blackboard.

 Please follow APA guidelines (proper margins, double-spaced, Times New Roman font,

12-point font).

 Use APA citation format and include a reference/works cited page when necessary.

 Writing should be clear, concise, and well organized. Thoughts should be expressed in

a logical manner.

 The writing should be free of spelling, grammar errors with excellent sentence /

paragraph construction.

 The outline template should be 4 pages maximum in length including reference page/work cited page.

 Save your files using the following filename convention:

o ScopeStatement – FirstName_LastName

Be sure to read the criteria, by which your paper/project will be evaluated, before you write, and again after you write.

PMG501 – Scope Project Management

Unit 4 Assignment: Scope Statement

Evaluation Rubric Unit 4: Scope Statement Outline Template Assignment

CRITERIA Deficient

Needs

Improvement Proficient

Exemplary

0 – 11 Points 12 – 16 Points 17 – 19 Points 20 Points

Executive Summary

Executive summary is

inadequate or missing.

Executive summary

is unfocused and

does not give a

clear perspective.

Executive summary

presents a specific

position or

perspective but may

lack clarity or detail.

Executive summary gives a clear, well- written position or perspective.

Solution Requirements, Prioritization, and Verification

No prioritized list of regulatory requirements identified and/or and missing summary of collection process and key stakeholders. Includes the incorrect number of requirements. Little to no evidence of unit concepts applied.

Identifies prioritized list of regulatory requirements but missing summary of collection process and/or key stakeholders. Includes the incorrect number of requirements. Few unit concepts applied and evident.

Identifies a prioritized list of regulatory requirements and summary of collection process and key stakeholders. Includes correct number of requirements. Some unit concepts applied and evident.

Identifies a prioritized list of regulatory requirements and summary of collection process and key stakeholders. Includes the correct number of requirements. Several unit concepts applied and evident.

Key Project Features

Both project constraints and milestones are missing and/or is not identified clearly in either section. Little to no evidence of unit concepts applied.

Project constraints and milestones are identified but missing some detail in each section. Few unit concepts applied and evident.

Project constraints and milestones are identified but missing some detail in one section. Some unit concepts applied and evident.

Both project constraints and milestones are clearly identified with supporting detail in each section. Several unit concepts applied and evident.

0 Points 0 Points 0 Points 20 Points

Exclusions Incorrect number of exclusions identified and listed.

N/A N/A Correct number of exclusions identified and listed.

0 Points 0 Points 0 Points 10 Points

Business Requirements

Not the same requirements listed from Business Case in previous unit.

N/A N/A Same requirements listed from Business Case in previous unit.

0 – 5 Points 6 – 7 Points 8 – 9 Points 10 Points

Clear and Professional Writing

Writing assignment contains no sense of organization. Paragraphs lack clear ideas. Contains several errors in grammar, spelling and punctuation which detracts from content of the passage.

Writing assignment contains a sense of organization. Some paragraphs have clear ideas. Contains several minor errors in grammar, spelling and punctuation, but does not detract from content of the passage.

Writing assignment contains good overall organization. Most paragraphs have clear ideas and are supported with some examples. Mostly free of errors in grammar, spelling and punctuation.

Writing assignment is well-planned and well-thought out. All paragraphs have clear ideas, are supported with examples and have smooth transitions. Free of errors in grammar, spelling and punctuation.

Unit4Assignment_ScopeStatementOutlineTemplate2.docx

PMG501 – Scope Project Management

Scope Statement Outline Template

Scope Statement: [Your Proposed Project Name Here]

(Note: the text in RED is designed to help you write your Scope Statement. Please remove all red text before submitting your assignment.)

1. Executive Summary

· Have you noticed how useful it is to have an Executive Summary of your project already written? A well-written Executive Summary is one that can be used in multiple documents as needed. As with other Executive Summaries, this summary should briefly describe the background and purpose of the project, and it’s acceptable to reuse summary text from other deliverables.

· Because the Scope Statement is different from other scope documents in that it is a living document (it can be changed as project scope changes), it’s helpful to identify the project’s overall expected cost and delivery timeframe, to quickly provide readers a sense of the project’s scale.

1. Business Requirements

· In this section, identify the business requirements this project was undertaken to satisfy. It is acceptable to restate the business requirements you identified in your Business Case (in fact, if your business requirements have changed, then the purpose of the project has changed, which isn’t a good sign. Business requirements should remain fixed once a project has been approved for initiation.)

1. Solution Requirements, Prioritization, and Verification

1. This section will contain a prioritized list of the project, technical, and any regulatory requirements associated with your project. Begin this section by briefly summarizing the requirement collection process used for your case study project, to give the requirements themselves some context. For example, you may want to briefly identify the collection tools used, some of the key stakeholders involved, and how requirement priorities were determined.

1. Next, list the requirements for your case study (identify, at a minimum, 15 requirements.) For each requirement, include:

1. The requirement sentence itself

1. The type of requirement: project, technical, or regulatory

1. Whether the requirement is a “must have”, “should have”, or “nice to have” requirement

1. How you will determine the requirement has been fulfilled (what verification methods will be used)

1. You may find using a table (or simple columns) useful for organizing your requirements list, but you are not required to do so.

1. Exclusions

1. In this section, identify at least two items that are NOT included as part of this project.

1. Key Project Features

4. Project Constraints

1. In this section, identify any conditions that limit project planning, such as the availability of certain important personnel or pieces of equipment; the amount of money available for the project; contractual limits; and/or predefined timelines.

4. Important Milestones

1. In this section, identify any important delivery dates or interim delivery dates the project plan must include. For example, identify any required project reviews, inspections, testing milestones, or fiscal reporting dates (you are not limited to these examples.)

1. Project Assumptions and Risks (this section is not required for this assignment)

1. Most scope statements include a section that identifies any assumptions and risks associated with the project thus far. Since you already identified risks for your case study project in your business case assignment in course week 1, you are not required to generate a new list of risks for this scope statement assignment. This section has been included with this scope statement simply to show you it is normally a part of the scope statement, to give you a complete scope statement template for potential use outside this class.

1. Approvals

1. This final section provides space for actual signatures, to formally indicate approval of the requirements, priorities, acceptance criteria, and exclusions identified. Formal approval of the scope statement allows the project team to use this document to begin detailed project planning, so it’s important this document indicates agreement from any stakeholder responsible for overseeing any part of this project.

1. In this section, create an area for key stakeholders to sign this document. For your case study, who do you believe should sign this document? Be sure to also identify the signatory’s name, role, and the date the document was signed.

image1.png