HIS 200 Historical Analysis Essay Progress Check 1 Guidelines and Rubric
Overview: Throughout Modules Five and Six, you have been guided through beginning your Project 2: Historical Analysis Essay, which you will continue to work
on in Modules Seven and Eight and formally submit for completion at the end of Module Eight of the course. This progress check assignment provides you with
an important opportunity to get valuable instructor feedback on the progress you are making and to ensure you are on the right track for your later submission.
Prompt: Modules Five and Six have introduced you to how historians approach assessing historical evidence to refine their thesis statement and message. By
now you should have enough evidence compiled from your research to begin writing your historical analysis essay. You will begin working on the essay piece by
piece. In Module Five: Analyzing History, learning block 5-4 (page 2) in the webtext, you will work on drafting an introduction for your historical analysis essay.
This introduction will include the necessary parts of an introduction: an explanation of the topic and argument, an overview of evidence, and your revised thesis
statement.
Specifically, in this assignment, you will submit parts of the following elements of your Project 2: Historical Analysis Essay for review by your instructor:
In Module Five: Analyzing History, Learning Block 5-4 (page 5) in the webtext, you worked toward the following element:
I. Introduction: In this section of your essay, you will introduce your readers to the historical event you selected. Specifically, you should:
A. Provide a brief overview of your historical event. For instance, what background information or context does the reader of your essay need?
In Module Five: Analyzing History, Learning Block 5-4 (page 1) in the webtext, you worked toward the following element:
B. Based on your research question, develop a thesis statement that states your claim about the historical event you selected. Your thesis statement
should be clear, specific, and arguable, as it will give direction to the rest of your essay.
Please note that the numbering included above directly aligns with the numbering of these elements as they are presented in the Project 2 Guidelines and
Rubric. For your final historical analysis essay, you will also include body paragraphs, a conclusion, a reference list, and your essays overall message, but you do
not need to include them in this submission. You will be prompted to build upon this progress check submission to prepare your final historical analysis essay for
submission in Module Eight.
Rubric
Guidelines for Submission: The Historical Analysis Essay Progress Check 1 must be submitted as a 1-page Microsoft Word document with double spacing, 12-
point Times New Roman font, and one-inch margins. Follow the formatting of the example included in Module Five: Analyzing History, learning block 5-4 (page
5) in the webtext, and include identifying information (name, course code and title, name of university, and date) as well as section headings (revised thesis and
introduction) as appropriate.
Critical Elements Proficient (100%) Needs Improvement (75%) Not Evident (0%) Value
Introduction: Overview Provides brief overview of
historical event
Provides brief overview of
historical event, but with gaps in
detail or clarity
Does not provide brief overview
of historical event
50
Revised Thesis Statement Develops clear, specific, and
arguable thesis statement that
states claim about historical
event, based on research
question
Develops thesis statement that
states claim about historical
event, but thesis statement is
not based on research question
or lacks clarity or specificity or is
not arguable
Does not develop thesis
statement that states claim
about historical event
30
Articulation of Response Submission has no major errors
related to citations, grammar,
spelling, syntax, or organization
Submission has major errors
related to citations, grammar,
spelling, syntax, or organization
that negatively impact
readability and articulation of
main ideas
Submission has critical errors
related to citations, grammar,
spelling, syntax, or organization
that prevent understanding of
ideas
20
Total 100%
HIS 200 Historical Analysis Essay Progress Check 1 Guidelines and Rubric
Rubric
Accessibility Report
Filename:
HIS 200 Historical Analysis Essay Progress Check 1 Guidelines and Rubric.pdf
Report created by:
Organization:
[Enter personal and organization information through the Preferences > Identity dialog.]
Summary
The checker found no problems in this document.
Needs manual check: 2
Passed manually: 0
Failed manually: 0
Skipped: 1
Passed: 29
Failed: 0
Detailed Report
Document
Rule Name
Status
Description
Accessibility permission flag
Passed
Accessibility permission flag must be set
Image-only PDF
Passed
Document is not image-only PDF
Tagged PDF
Passed
Document is tagged PDF
Logical Reading Order
Needs manual check
Document structure provides a logical reading order
Primary language
Passed
Text language is specified
Title
Passed
Document title is showing in title bar
Bookmarks
Passed
Bookmarks are present in large documents
Color contrast
Needs manual check
Document has appropriate color contrast
Page Content
Rule Name
Status
Description
Tagged content
Passed
All page content is tagged
Tagged annotations
Passed
All annotations are tagged
Tab order
Passed
Tab order is consistent with structure order
Character encoding
Passed
Reliable character encoding is provided
Tagged multimedia
Passed
All multimedia objects are tagged
Screen flicker
Passed
Page will not cause screen flicker
Scripts
Passed
No inaccessible scripts
Timed responses
Passed
Page does not require timed responses
Navigation links
Passed
Navigation links are not repetitive
Forms
Rule Name
Status
Description
Tagged form fields
Passed
All form fields are tagged
Field descriptions
Passed
All form fields have description
Alternate Text
Rule Name
Status
Description
Figures alternate text
Passed
Figures require alternate text
Nested alternate text
Passed
Alternate text that will never be read
Associated with content
Passed
Alternate text must be associated with some content
Hides annotation
Passed
Alternate text should not hide annotation
Other elements alternate text
Passed
Other elements that require alternate text
Tables
Rule Name
Status
Description
Rows
Passed
TR must be a child of Table, THead, TBody, or TFoot
TH and TD
Passed
TH and TD must be children of TR
Headers
Passed
Tables should have headers
Regularity
Passed
Tables must contain the same number of columns in each row and rows in each column
Summary
Skipped
Tables must have a summary
Lists
Rule Name
Status
Description
List items
Passed
LI must be a child of L
Lbl and LBody
Passed
Lbl and LBody must be children of LI
Headings
Rule Name
Status
Description
Appropriate nesting
Passed
Appropriate nesting
Back to Top
SHOW MORE…
Project Management
Identify a personal project of your choosing. This could be a family vacation, plans to clean or organize a part of your living space, etc.
Provide a brief summary of your project that includes the scope of the project and at least three goals or objectives of the project.
Identify a personal project of your choosing. This could be a familyvacation, plans to clean or organize a part of your living space, etc.
For the discussion, you will use the tools provided in Chapter 4 of your textbook to provide a brief summary of your project that includes the scope of the project and at least three goals or objectives of the project. Chapter Four
Defining the Project
2021 McGraw Hill. All rights reserved. Authorized only for instructor use in the classroom.
No reproduction or further distribution permitted without the prior written consent of McGraw Hill.
Because learning changes everything.
Where We Are Now
McGraw Hill
#
2
Learning Objectives
4-1 Identify key elements of a project scope statement and understand why a complete scope statement is critical to project success.
4-2 Describe the causes of scope creep and ways to manage it.
4-3 Understand why it is important to establish project priorities in terms of cost, time, and performance.
4-4 Demonstrate the importance of a work breakdown structure (WBS) to the management of projects and how it serves as a database for planning and control.
4-5 Demonstrate how the organization breakdown structure (OBS) establishes accountability to organization units.
4-6 Describe a process breakdown structure (PBS) and when to use it.
4-7 Create responsibility matrices for small projects.
4-8 Create a communication plan for a project.
McGraw Hill
#
Chapter Outline
4.1 Step 1: Defining the Project Scope
4.2 Step 2: Establishing Project Priorities
4.3 Step 3: Creating the Work Breakdown Structure
4.4 Step 4: Integrating the WBS with the Organization
4.5 Step 5: Coding the WBS for the Information System
4.6 Process Breakdown Structure
4.7 Responsibility Matrices
4.8 Project Communication Plan
McGraw Hill
#
Five General Steps for Collecting Project Information
Step 1: Defining the Project Scope
Step 2: Establishing Project Priorities
Step 3: Creating the Work Breakdown Structure
Step 4: Integrating the WBS with the Organization
Step 5: Coding the WBS for the Information System
McGraw Hill
#
4.1 Step 1: Defining the Project Scope
Project Scope Defined
Is a definition of the end result or mission of your projecta product or service for your client/customer.
Defines the results to be achieved in specific, tangible, and measurable terms.
Purposes of the Project Scope Statement
To clearly define the deliverable(s) for the end user.
To direct focus on the project purpose throughout the life of the project for the customer and project participants.
To be published and used by the project owner and project participants for planning and measuring project success.
McGraw Hill
#
6
Project Scope Checklist
Project objective
Product scope description
Justification
Deliverables
Milestones
Technical requirements
Limits and exclusions
Acceptance criteria
McGraw Hill
#
7
Project Scope: Terms and Definitions
Scope Statements
Is a short, one- to two-page summary of key elements of the scope, followed by extended documentation of each element.
Is also referred to as statements of work (SOWs).
Project Charter
Is a documentation that authorizes the project manager to initiate and lead the project.
Often includes a brief scope description as well as such items as risk limits, business case, spending limits, and even team composition.
Scope Creep
Is the tendency for the project scope to expand over timeusually by changing requirements, specifications, and priorities.
McGraw Hill
#
8
Five of the Most Common Causes of Scope Creep
Poor requirement analysis
Not involving users early enough
Underestimating project complexity
Lack of change control
Gold plating
McGraw Hill
#
9
4.2 Step 2: Establishing Project Priorities
Three major criteria (trade-offs) that a project manager has to manage are:
Cost (budget)
Time (schedule)
Performance (scope)
A project manager can manage the project trade-offs by completing a priority matrix for the project and identifying which criterion is:
Constrainoriginal parameter is fixed.
Enhancea criterion should be optimized.
Accepta criterion is tolerable not to meet the original parameter.
McGraw Hill
#
10
Project Management Trade-offs
FIGURE 4.1
McGraw Hill
#
Project Priority Matrix for the Development of a New Wireless Router
FIGURE 4.2
Access the text alternative for slide images.
McGraw Hill
#
4.3 Step 3: Creating the Work Breakdown Structure
Work Breakdown Structure (WBS)
Is a hierarchical outline of the project with different levels of detail.
Identifies the products and work elements involved in a project.
Defines the relationship of the final deliverable (the project) to its sub-deliverables, and, in turn, their relationships to work packages.
Serves as a framework for tracking cost and work performance.
Is best suited for design and build projects that have tangible outcomes rather than process-oriented projects.
McGraw Hill
#
Hierarchical Breakdown of the WBS
* This breakdown groups work packages by type of work within a deliverable and allows assignment of responsibility to an organizational unit. This extra step facilitates a system for monitoring project progress (discussed in Chapter 13).
FIGURE 4.3
Access the text alternative for slide images.
McGraw Hill
#
How WBS Helps the Project Manager
Assures project managers that all products and work elements are identified, to integrate the project with the current organization, and to establish a basis for control.
Facilitates the evaluation of cost, time, and technical performance at all levels in the organization over the life of the project.
Provides management with information appropriate to each organizational level.
Helps project managers to plan, schedule, and budget the project.
Helps in the development of the organization breakdown structure (OBS), which assigns project responsibilities to organization units and individuals.
Provides the opportunity to roll up (sum) the budget and actual costs of the smaller work packages into larger work elements.
Defines communication channels and assists in understanding and coordinating many parts of the project.
McGraw Hill
#
Work Breakdown Structure
FIGURE 4.4
Access the text alternative for slide images.
McGraw Hill
#
A Work Package
Is the lowest level of the WBS.
Is a short-duration task that has a definite start and stop point, consumes resources, and represents cost.
Should not exceed 10 workdays or one reporting period.
Should be as independent of other work packages of the project as possible.
Is the basic unit used for planning, scheduling, and controlling the project.
McGraw Hill
#
Each Work Package in the WBS
Defines work (what).
Identifies time to complete a work package (how long).
Identifies a time-phased budget to complete a work package (cost).
Identifies resources needed to complete a work package (how much).
Identifies a single person responsible for units of work (who).
Identifies monitoring points for measuring progress (how well).
McGraw Hill
#
4.4 Step 4: Integrating the WBS with the Organization
Organization Breakdown Structure (OBS)
Depicts how the firm has organized to discharge work responsibility.
Provides a framework to summarize organization unit work performance.
Identifies the organization units responsible for work packages.
Ties the organizational unit to cost control accounts.
The intersection of work packages and the organization unit creates a project cost point or cost account that integrates work and responsibility.
McGraw Hill
#
Integration of WBS and OBS
FIGURE 4.5
Access the text alternative for slide images.
McGraw Hill
#
4.5 Step 5: Coding the WBS for the Information System
WBS Coding System
Defines
Levels and elements in the WBS
Organization elements
Work packages
Budget and cost information
Allows reports to be consolidated at any level in the structure.
WBS Dictionary
Provides detailed information about each element in the WBS.
McGraw Hill
#
Coding the WBS
EXHIBIT 4.1
Access the text alternative for slide images.
McGraw Hill
#
4.6 Process Breakdown Structure
Process Breakdown Structure (PBS)
Is used for process-oriented projects.
Is often referred to as the waterfall method in the software industry.
Process-oriented project
Is a project that the final outcome is a product of a series of steps and phases.
Is a project that evolves over time with each phase affecting the next phase.
Is a project that is driven by performance requirements, not by plans/blueprints.
McGraw Hill
#
PBS for Software Development Project
FIGURE 4.6
Access the text alternative for slide images.
McGraw Hill
#
4.7 Responsibility Matrices
Responsibility Matrix (RM)
Is also called a linear responsibility chart.
Summarizes the tasks to be accomplished and who is responsible for what on the project.
Lists all the project activities and the participants responsible for each activity.
Clarifies interfaces between units and individuals that require coordination.
Provides a mean for all participants in a project to view their responsibilities and agree on their assignments.
Clarifies the extent or type of authority exercised by each participant.
McGraw Hill
#
Responsibility Matrix for a Market Research Project
FIGURE 4.7
Access the text alternative for slide images.
McGraw Hill
#
Responsibility Matrix for the Conveyor Belt Project
FIGURE 4.8
Access the text alternative for slide images.
McGraw Hill
#
4.8 Project Communication Plan
Project communication plans address the following questions:
What information needs to be collected and when?
Who will receive the information?
What methods will be used to gather and store information?
What are the limits, if any, on who has access to certain kinds of information?
When will the information be communicated?
How will it be communicated?
McGraw Hill
#
Steps for Developing a Communication Plan
Stakeholder analysisidentify the target groups.
Information needsproject status reports, deliverable issues, changes in scope, team status meetings, gating decisions, accepted request changes, action items, milestone reports, etc.
Sources of informationwhere does the information reside?
Dissemination modeshardcopy, e-mail, teleconferencing, SharePoint, and a variety of database sharing programs.
Responsibility and timingdetermine who will send out the formation and when.
McGraw Hill
#
Stakeholder Communications
FIGURE 4.9
Access the text alternative for slide images.
McGraw Hill
#
Shale Oil Research Project Communication Plan
What Information
Target Audience
When?
Method of Communication
Provider
Milestone report
Senior management and project manager
Bimonthly
E-mail and hardcopy
Project office
Project status reports & agendas
Staff and customer
Weekly
E-mail and hardcopy
Project manager
Team status reports
Project manager and project office
Weekly
E-mail
Team recorder
Issues report
Staff and customer
Weekly
E-mail
Team recorder
Escalation reports
Staff and customer
When needed
Meeting and hardcopy
Project manager
Outsourcing performance
Staff and customer
Bimonthly
Meeting
Project manager
Accepted change requests
Project office, senior management, customer, staff, and project manager
Anytime
E-mail and hardcopy
Design department
Oversight gate decisions
Senior management and project manager
As required
E-mail meeting report
Oversight group or
project office
FIGURE 4.10
McGraw Hill
#
Key Terms
Acceptance criteria
Cost account
Gold plating
Milestone
Organization breakdown structure (OBS)
Priority matrix
Process breakdown structure (PBS)
Product scope description
Project charter
Responsibility matrix
Scope creep
Scope statement
WBS dictionary
Work breakdown structure (WBS)
Work package
McGraw Hill
#
End of Main Content
2021 McGraw Hill. All rights reserved. Authorized only for instructor use in the classroom.
No reproduction or further distribution permitted without the prior written consent of McGraw Hill.
Because learning changes everything.
www.mheducation.com
Accessibility Content: Text Alternatives for Images
McGraw Hill
#
Project Priority Matrix for the Development of a New Wireless Router – Text Alternative
Return to parent-slide containing images.
Time
Performance
Cost
Constrain
X
Enhance
X
Accept
X
Return to parent-slide containing images.
McGraw Hill
#
Hierarchical Breakdown of the WBS – Text Alternative
Return to parent-slide containing images.
Level
Hierarchical breakdown
Description
1
[double-headed arrow]
Project
[downward arrow]
Complete project
2
[double-headed arrow]
Deliverable
[downward arrow]
Major deliverables
3
[double-headed arrow]
Subdeliverable
[downward arrow]
Supporting deliverables
4
[double-headed arrow]
Lowest subdeliverable
[downward arrow]
Lowest management responsibility level
5
[double-headed arrow]
Cost account*
[downward arrow]
Work package
Grouping of work packages for monitoring progress and responsibility
Identifiable work activities
* This breakdown groups work packages by type of work within a deliverable and allows assignment of responsibility to an organizational unit. This extra step facilitates a system for monitoring project progress (discussed in Chapter 13).
Return to parent-slide containing images.
McGraw Hill
#
Work Breakdown Structure – Text Alternative
Return to parent-slide containing images.
Level 1 consists of the E-Slim Tablet x-13 Prototype.
Level 2 consists of Hardware, CPU, and More Items.
Level 3 consists of the Power Supply, Flash ROM, and I/O Controller, all flowing from the CPU in Level 2.
Level 4 consists of the Battery and Charger (flowing from the Power Supply in Level 3) and the USB Slots, Internet, and Touch Screen (flowing from the I/O Controller in Level 3).
Level 5 consists of the following components. Lowest Manageable Subdeliverables are identified with an (*); Work Packages are identified with a (#).
From Hardware (in Level 2)
Frame*
o WP-F1#
Cameras*
o WP-C1#
o WP-C2#
o WP-C3#
o WP-C4#
Speakers*
o WP-S1#
Antenna*
o WP-A1#
o WP-A2#
o WP-A3#
From Touch Screen (in Level 4)
Keyboard*
o WP-K1#
Touch Sensors*
o WP-TS1#
o WP-TS2#
o WP-TS3#
Back Light*
o WP-BL1#
o WP-BL2#
o WP-BL3#
Resolution*
o WP-R1#
o WP-R2#
o WP-R3#
Return to parent-slide containing images.
McGraw Hill
#
Integration of WBS and OBS – Text Alternative
Return to parent-slide containing images.
Level 1 consists of the E-Slim Tablet x-13 Prototype [1.0].
Level 2 consists of Hardware [1.1], CPU [1.2], and More Items.
Level 3 consists of the Power Supply [1.2.1], Flash ROM [1.2.2], and I/O Controller [1.2.3], all flowing from the CPU in Level 2.
Level 4 consists of the Battery [1.2.1.1] and Charger [1.2.1.2] (flowing from the Power Supply in Level 3) and the USB Slots [1.2.3.1], Internet [1.2.3.2], and Touch Screen [1.2.3.3] (flowing from the I/O Controller in Level 3).
Level 5 consists of the following components, which are the Lowest Manageable Subdeliverables.
From Hardware (in Level 2)
Frame [1.1.1]
Cameras [1.1.2]
Speakers [1.1.3]
Antenna [1.1.4]
From Touch Screen (in Level 4)
Keyboard [1.2.3.3.1]
Touch Sensors [1.2.3.3.2]
Back Light [1.2.3.3.3]
Resolution [1.2.3.3.4]
The Level 5 components are integrated
into the OBS as shown in the following table:
Frame
Cameras
Speakers
Antenna
Keyboard
Touch Sensors
Back Light
Resolution
Design
Cost Account
1.1.4.1*
Cost Account
Cost Account
Cost Account
QC Test
Cost Account
Cost Account
Cost Account
Cost Account
Cost Account
Production
Cost Account
1.2.3.3.2.3
Cost Account
Outsourcing
Cost Account
Cost Account
Cost Account
Cost Account
Cost Account
Cost Account
* Cost Account Number
Return to parent-slide containing images.
McGraw Hill
#
Coding the WBS – Text Alternative
Return to parent-slide containing images.
[Info icon]
Task Mode
Task Name
1
[right-pointing arrow icon]
1 E-Slim Tablet x-13 Prototype
2
[right-pointing arrow icon]
1.1 Hardware
3
[push-pin icon and question mark]
1.1.1 Cameras
4
[push-pin icon and question mark]
1.1.2 Speakers
5
[push-pin icon and question mark]
1.1.3 Antenna
6
[right-pointing arrow icon]
1.2 CPU
7
[right-pointing arrow icon]
1.2.1 Power supply
8
[push-pin icon and question mark]
1.2.1.1 Battery (more items)
9
[push-pin icon and question mark]
1.2.1.2 Charger (more items)
10
[right-pointing arrow icon]
1.2.2 Flash Rom (more items)
11
[push-pin icon and question mark]
1.2.2.1 I/O controller
12
[push-pin icon and question mark]
1.2.2.2 USB slots (more items)
13
[push-pin icon and question mark]
1.2.2.3 Internet (more items)
14
[right-pointing arrow icon]
1.2.3 Touch screen
15
[right-pointing arrow icon]
1.2.3.1 Keyboard
16
[push-pin icon and question mark]
1.2.3.1.1 Work package
17
[right-pointing arrow icon]
1.2.3.2 Touch sensors
18
[push-pin icon and question mark]
1.2.3.2.1 Work package
19
[push-pin icon and question mark]
1.2.3.2.2 Work package
20
[push-pin icon and question mark]
1.2.3.2.3. Work package
21
[push-pin icon and question mark]
1.2.3.3 Back light (more items)
22
[push-pin icon and question mark]
1.2.3.4 Resolution (more items)
Return to parent-slide containing images.
McGraw Hill
#
PBS for Software Development Project – Text Alternative
Return to parent-slide containing images.
Software development project
Analysis (1)
Design (1)
o Define user interface (2)
o Develop technical design (2)
Define application architecture (3)
Define processing flow (3)
Design logical database structure (3)
Design system interfaces (3)
o Establish quality requirements (2)
o Develop detailed design (2)
Construct (1)
Test (1)
Rollout (1)
Outputs:
Design phase deliverables
Design document
o Application architecture
o Application flow
o Database design
o End user interface design
o Workflow diagram
User documentation outline
==============
Note: Numbers in parentheses indicate the following levels:
(1) Level: Major phases
(2) Level: Activities
(3) Level: Activities
Return to parent-slide containing images.
McGraw Hill
#
Responsibility Matrix for a Market Research Project – Text Alternative
Return to parent-slide containing images.
Task
Project Team
Richard
Dan
Dave
Linda
Elizabeth
Identify target customers
R
S
S
Develop draft questionnaire
R
S
S
Pilot-test questionnaire
R
S
Finalize questionnaire
R
S
S
S
Print questionnaire
R
Prepare mailing labels
R
Mail questionnaires
R
Receive and monitor returned questionnaires
R
S
Input response data
R
Analyze results
R
S
S
Prepare draft of report
S
R
S
S
Prepare final report
R
S
R = Responsible
S = Supports/assists
Return to parent-slide containing images.
McGraw Hill
#
Responsibility Matrix for the Conveyor Belt Project – Text Alternative
Return to parent-slide containing images.
Deliverables
Organization
Design
Development
Documentation
Assembly
Testing
Purchasing
Quality Assurance
Manufacturing
Architectural designs
1
2
2
3
3
Hardware specifications
2
1
2
3
Kernel specifications
1
3
3
Utilities specifications
2
1
3
Hardware design
1
3
3
3
Disk drivers
3
1
2
Memory management
1
3
3
Operating system documentation
2
2
1
3
Prototypes
5
4
1
3
3
3
4
Integrated acceptance test
5
2
2
1
5
5
1 Responsible
2 Support
3 Consult
4 Notification
5 Approval
Return to parent-slide containing images.
McGraw Hill
#
Stakeholder Communications – Text Alternative
Return to parent-slide containing images.
High Power, Low Interest: Keep Satisfied (clients D and A)
Low Power, Low Interest: Provide General Information (clients G and B)
High Power, High Interest: Manage Closely (clients F, H, and C)
Low Power, High Interest: Keep Informed (clients D and E)
Return to parent-slide containing images.
McGraw Hill
#
image3.PNG
image4.PNG
image5.png
image6.png
image7.png
image8.png
image9.png
image10.png
image11.png
image12.png
image13.png
image14.png
image2.png
image1.png