all together

CIS 500 – Information Systems for Decision-Making

© 2017 Strayer University. All Rights Reserved. This document contains Strayer University Confidential and Proprietary information and may not be copied, further distributed, or otherwise disclosed in whole or in part, without the expressed written permission of Strayer University.

CIS 500 Page 1 of 2

Week 9 Status Report

Due Week 9 and worth 50 points

Your big presentation is due next week! Update your project manager with what has happened since your last report. Include these 4 things:

1. What did you expect to accomplish on the project this week? (Copy this from item 4 of last week’s report.)

2. What did you actually accomplish on the project this week? 3. What issues have arisen, and what help do you need? 4. What must you accomplish to be ready for the kickoff presentation next week?

Please write up your responses as a series of bullet points in memo form. There is no need for a cover page. Grading for both of the weekly status reports will be based on the following rubric.

Points: 50 Status Report

Criteria Unacceptable Below 70% F

Fair 70-79% C

Proficient 80-89% B

Exemplary 90-100% A

1. What did you expect to accomplish on the project this week?

Weight: 20%

(10 points)

Inadequate list of expectations toward project completion for the week

Inadequate explanation of plans to meet expectations

Listed expectations toward project completion for the week

Somewhat explained the plans to meet expectations

Listed expectations toward project completion for the week.

Explained the plans to meet these expectations

Provided insight as to how expectations were set week-to- week.

Demonstrated when and how expectations listed would be met.

2. What did you actually accomplish on the project this week?

Weight: 20%

(10 points)

Inadequate list of accomplishments toward project for the week

Limited description of what was not accomplished

Listed accomplishments for the week

Somewhat described what was not accomplished

Listed accomplishments for the week

Described what was not accomplished for the week

Listed accomplishments for the week.

Explained why things were not accomplished.

3. What issues have arisen, and what help would you like with them?

Weight: 20%

(10 points)

Inadequate description of issues that arose during week

Did not describe or identify issues to be

Described issues that arose during the week

Somewhat described help needed to resolve

Described issues that arose during the week

Determined what kind of help is needed to resolve

Described issues that arose, demonstrated how they were resolved.

Presented issues in order of priority,

CIS 500 – Information Systems for Decision-Making

© 2017 Strayer University. All Rights Reserved. This document contains Strayer University Confidential and Proprietary information and may not be copied, further distributed, or otherwise disclosed in whole or in part, without the expressed written permission of Strayer University.

CIS 500 Page 2 of 2

resolved

outstanding issues outstanding issues

with ideas about how to solve each.

4. What do you expect to accomplish on the project next week?

Weight: 20%

(10 points)

Inadequate list of expectations toward project completion

Did not describe how outstanding issues would be resolved

Listed expectations toward project completion for next week

Somewhat described how outstanding issues would be resolved

Listed expectations toward project completion for next week

Described how outstanding issues would be resolved by the following week

Presented prioritized list of expectations for next week

Proposed strategy for prioritizing and resolving outstanding issues

5. Clarity, persuasion, proper communication, writing mechanics, and formatting requirements

Weight: 20%

(10 points)

Unclear structure, not persuasive, major grammatical errors

Somewhat clear structure, limited persuasion, grammatical errors, language too simple or too wordy

Clear structure, persuasive writing, minor or no grammatical errors, length and format within requirements, plain language

No grammatical errors, plain language, organized by topic, references business needs, connects to technical specs, persuasive