1 To: ADD name, title Comment by Sharon Rose: NOTE: There is no need for a cover page. Remove comments provide by instructor before submitting assignment. Assignment with comments will be returned for resubmissionFrom: ADD your nameDate: ADD date Subject: Status Report Week 8 Enter a short paragraph stating objective of the status.Project Task for this week: Comment by Sharon Rose: List expectations toward project completion for the week. Explain the plans to meet these expectation Provide insight as to how expectations were set week-to-week. Include when expectations listed would be met. · Write task 1 · Write task 2 · … · … · If applicable add more or lessProject Task accomplished this week: Comment by Sharon Rose: List accomplishments for the week Describe what was not accomplished for the week List accomplishments for the week Explain why things were not accomplished · Write task 1 · Write task 2 · .. · .. If applicable add more or less Project Issues: Comment by Sharon Rose: Describe issues that arose during the week Determine what kind of help is needed to resolve outstanding issues Describe issues that arose and include how they were resolved. Present issues in order of priority, with ideas about how to solve each. · Write issue 1 · Write issue 2 Project tasks planned for next week: Comment by Sharon Rose: List expectations toward project completion for next week Described how outstanding issues would be resolved by the following week Prioritize list of expectations for next week Propose strategy for prioritizing and resolving outstanding issues · Write task 1 · Write task 2 · .. · .. If applicable add more 1 To: ADD name, title Comment by Sharon Rose: NOTE: There is no need for a cover page. Remove comments provide by instructor before submitting assignment. Assignment with comments will be returned for resubmissionFrom: ADD your nameDate: ADD date Subject: Status Report Week 9 Enter a short paragraph stating objective of the status.Project Task for this week: Comment by Sharon Rose: List expectations toward project completion for the week. Explain the plans to meet these expectation Provide insight as to how expectations were set week-to-week. Include when expectations listed would be met. · Task 1 · Task 2Project Task accomplished this week Comment by Sharon Rose: List accomplishments for the week Describe what was not accomplished for the week List accomplishments for the week Explain why things were not accomplished · Task 1 · Task 2Project Issues Comment by Sharon Rose: Describe issues that arose during the week Determine what kind of help is needed to resolve outstanding issues Describe issues that arose and include how they were resolved. Present issues in order of priority, with ideas about how to solve each. · Issue 1 · Issue 2 Project tasks planned for next week Comment by Sharon Rose: List expectations toward project completion for next week Described how outstanding issues would be resolve ...

1. 1
To: ADD name, titleComment by Sharon Rose: NOTE:
There is no need for a cover page.
Remove comments provide by instructor before submitting
assignment.
Assignment with comments will be returned for
resubmissionFrom: ADD your nameDate: ADD date Subject:
Status Report Week 8
Enter a short paragraph stating objective of the status.Project
Task for this week: Comment by Sharon Rose: List
expectations toward project completion for the week.
Explain the plans to meet these expectation
Provide insight as to how expectations were set week-to-week.
Include when expectations listed would be met.
· Write task 1
· Write task 2
· …
· …
· If applicable add more or lessProject Task accomplished this
week: Comment by Sharon Rose: List accomplishments for
the week
Describe what was not accomplished for the week
List accomplishments for the week
Explain why things were not accomplished
· Write task 1
· Write task 2
· ..
· .. If applicable add more or less
Project Issues: Comment by Sharon Rose: Describe issues that
arose during the week
Determine what kind of help is needed to resolve outstanding
issues
Describe issues that arose and include how they were resolved.

2. Present issues in order of priority, with ideas about how to
solve each.
· Write issue 1
· Write issue 2 Project tasks planned for next week:
Comment by Sharon Rose: List expectations toward project
completion for next week
Described how outstanding issues would be resolved by the
following week
Prioritize list of expectations for next week
Propose strategy for prioritizing and resolving outstanding
issues
· Write task 1
· Write task 2
· ..
· .. If applicable add more
1
To: ADD name, titleComment by Sharon Rose: NOTE:
There is no need for a cover page.
Remove comments provide by instructor before submitting
assignment.
Assignment with comments will be returned for
resubmissionFrom: ADD your nameDate: ADD date Subject:
Status Report Week 9
Enter a short paragraph stating objective of the status.Project
Task for this week: Comment by Sharon Rose: List
expectations toward project completion for the week.
Explain the plans to meet these expectation
Provide insight as to how expectations were set week-to-week.
Include when expectations listed would be met.
· Task 1

3. · Task 2Project Task accomplished this week Comment by
Sharon Rose: List accomplishments for the week
Describe what was not accomplished for the week
List accomplishments for the week
Explain why things were not accomplished
· Task 1
· Task 2Project Issues Comment by Sharon Rose: Describe
issues that arose during the week
Determine what kind of help is needed to resolve outstanding
issues
Describe issues that arose and include how they were resolved.
Present issues in order of priority, with ideas about how to
solve each.
· Issue 1
· Issue 2 Project tasks planned for next week Comment by
Sharon Rose: List expectations toward project completion for
next week
Described how outstanding issues would be resolved by the
following week
Prioritize list of expectations for next week
Propose strategy for prioritizing and resolving outstanding
issues
· Task 1
· Task 2…..
CIS 500 – Information Systems for Decision-Making
© 2017 Strayer University. All Rights Reserved. This document
contains Strayer University Confidential and Proprietary

4. 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 4
Week 8 Status Report
Due Week 8 and worth 50 points
In Week 10, you will provide a detailed project presentation for
your new information system project.
Because of its importance to the organization, your presentation
must be thoughtful and visually
appealing.
To help you stay on track for this three-week effort, the
executives have assigned you a project manager.
For each week leading up to the presentation, you are expected
to turn in a short (less than one page)
status report. It must address just 4 things:
1. What did you expect to accomplish on the project this week?
2. What did you actually accomplish on the project this week?
3. What issues have arisen, and what help do you need?
4. What do you expect to accomplish on the project next week?
Please write up your responses as a series of bullet points in
memo form. There is no need for a cover
page.

5. 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 4
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?

6. Please write up your responses as a series of bullet points in
memo form. There is no need for a cover
page.
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 3 of 4
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

7. 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

8. 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%

9. (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

10. 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
resolved
Described issues
that arose during
the week
Somewhat

11. described help
needed to resolve
outstanding issues
Described issues
that arose during
the week
Determined what
kind of help is
needed to resolve
outstanding issues
Described issues
that arose,
demonstrated how
they were resolved.
Presented issues in
order of priority,
with ideas about
how to solve each.
4. What do you expect to
accomplish on the project
next week?
Weight: 20%
(10 points)

12. 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

13. week
Presented
prioritized list of
expectations for
next week
Proposed strategy
for prioritizing and
resolving
outstanding issues
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 4 of 4
5. Clarity, persuasion,

14. 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

15. technical specs,
persuasive
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 4
Assignment 2: The Presentation
Due Week 10 and worth 200 points
Congratulations. Your project has been staffed and you are
about to meet with the team for the first time.
Initial impressions are important and you’ll need visuals for
your presentation. Create a slide show (in

16. PowerPoint or similar software) in which you address the
following, in this order:
1. Goals: What the project hopes to accomplish.
2. Critical Success Factors: Identify at least 4 different
stakeholders; for each, list at least 2 things
that the stakeholder requires in order to deem the project
successful.
3. Acquisition strategy: Should the system be built in-house,
created by a contractor, purchased off-
the-shelf and customized, or leased as a service? Explain your
rationale.
4. Resources: For in-house development, what people/skills are
required and what development
lifecycle do you recommend? Otherwise, identify 3 candidate
organizations that can deliver the
system.
5. System functions: In a table format, summarize the types of
users for the system; the business
reason(s) each would use the system; the ways that the system
supports each of these needs;
and how this support differs from the current system.
6. Connectivity: Provide a diagram that shows how the system
will connect to the other information

17. systems and what data flows among them.
7. Security: List the most serious cybersecurity threats and
vulnerabilities of the new system.
Suggest strategies to address them.
8. Mobility: Identify the system’s capabilities for mobile use.
Include a title and summary slide. Use one slide for each of the
8 points above. Include speaker notes or
audio narration that explains each slide more fully.
Grading for this assignment will be based on answer quality,
logic / organization of the paper, and
language and writing skills, using the following rubric.
Points: 200 Assignment 2: The Presentation
Criteria
Unacceptable
Below 70% F
Fair
70-79% C
Proficient
80-89% B
Exemplary
90-100% A

18. 1. Goals: What the
project hopes to
accomplish.
Weight: 10%
(20 points)
Did not
communicate what
the project hopes to
accomplish
Did not list project
goals
Communicated
what the project
hopes to
accomplish
Did not list project
goals
Communicated
what the project
hopes to
accomplish

19. Listed the project
goals
Communicated
importance of
project reaching its
goals
Connected project
goals to the
organizational
strategy
2. Critical Success Did not identify 4 Identified 4 Identified 4
Identified and
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 4
Factors: Identify at least

20. 4 different stakeholders;
for each, list at least 2
things that stakeholder
requires in order to deem
the project successful.
Weight: 10%
(20 points)
stakeholders
Listed things to
make project
successful, but did
not connect each
stakeholder
stakeholders
Listed less than 2
things each
stakeholder would
require to deem
project successful
stakeholders
Listed 2 things that
each stakeholder
would require to
deem the project

21. successful
justified the
selection of 4
stakeholders
Explained why each
stakeholder would
be most interested
in 2 things to deem
project successful
3. Acquisition strategy:
Should the system be
built in-house, created by
a contractor, purchased
off-the-shelf and
customized, or leased as
a service? Explain the
rationale for your choice.
Weight: 10%
(20 points)
Did not compare
acquisition
strategies
Did not determine
the best strategy for

22. the proposed
information system
Inadequately
explained the
rationale for
choosing the
acquisition strategy
Reasonable
comparison of
acquisition
strategies
Determined best
acquisition strategy
for the proposed
information system
Somewhat
explained the
rationale for
choosing the
acquisition strategy
Compared various
acquisition
strategies
Determined which

23. acquisition strategy
would be the best
for the proposed
system
Provided rationale
for choosing a
specific acquisition
strategy
Analyzed various
acquisition
strategies, or
presented an
acquisition strategy
that was not
previously
mentioned
Explained why
other acquisition
strategies would
potentially not work
Discussed cost
considerations
4. Resources: For in-
house development,
what people/skills are
required and what

24. development lifecycle do
you recommend?
Otherwise, identify 3
candidate organizations
that can deliver the
system.
Weight: 10%
(20 points)
Inadequately
determined
resources needed
for the acquisition
strategy
Limited
recommendation for
development
lifecycle for in-
house
development, or
three external
organizations that
can deliver the
system
Inadequate
justification
Determined

25. resources needed
for the acquisition
strategy, but did not
justify reasoning
Recommended a
project
development
lifecycle for in-
house
development, or
three external
organizations that
can deliver the
system, but did not
justify why they
were chosen
Determined and
justified resources
needed for chosen
acquisition strategy
Recommended a
project
development
lifecycle for in-
house
development, or
three external
organizations that
can deliver the

26. system.
Presented
resources not
previously
considered
Included risk
identification and
mitigation
procedures
Proposed a
combination of
resources and
strategy to organize
stakeholder efforts
toward project
completion
5. System functions: In a
table format, summarize
the types of users for the
system; the business
Failed to put in
table format
In table format:

27. Summarized some
In table format:
Summarized the
In table format:
Analyzed user
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 3 of 4
reason(s) each would
use the system; the ways
that the system supports
each of these needs; and
how this support differs
from the current system.

28. Weight: 10%
(20 points)
Inadequate
summary of users
for the system
Limited explanation
of why users would
use the system
Inadequate
description of how
system supports
users
Inadequate
comparison of the
proposed system to
the old system
of the types of
users for the
system
Somewhat
explained business
reasons for system
use

29. Somewhat
described how the
system supports
users
Reasonable
comparison of the
proposed system to
the old information
system
types of users for
the information
system
Explained business
reasons why each
user type would use
the system
Described how the
system supports the
needs of each user
type
Determined how
this support differs
from the current
information system

30. experience and
user design
considerations
Explained design
changes that took
place between the
old and new system
Provided rationale
for the user types
identified
Discussed how to
reach out to user
types to test the
system
6. Connectivity: Provide a
diagram that shows the
other information
systems this one will
connect to, and what
data flows among them.
Weight: 10%
(20 points)
Failed to put in
diagram format

31. Inadequate diagram
showing your
system, hard to
follow, incomplete
Inadequate or hard
to follow the data
that would flow
among systems,
incomplete
In a diagram:
Showed other
information systems
that your system
would connect to,
but hard to follow
Demonstrated what
data would flow
among systems, but
hard to follow
In a diagram:
Showed other
existing information
systems that your
proposed system

32. would connect to
Demonstrated what
data would flow
between your and
other information
systems.
In a diagram:
Showed how you
selected existing
systems that your
system would
connect to
Explained how
diagram would be
updated and
maintained based
on changes in the
marketplace
7. Security: List the most
serious cybersecurity
threats and vulnerabilities
of the new system.
Suggest strategies to
address them.

33. Weight: 10%
(20 points)
Inadequate list of
cybersecurity
threats
Inadequate
strategies to
address each threat
Reasonable list of
cybersecurity
threats, failed to
show why they are
most serious
Identified strategies
to address each
threat
Listed the most
serious
cybersecurity
threats to your new
system
Proposed strategies
to address each
threat

34. Proposed how your
new system would
integrate with
Shadow IT, if at all
Demonstrated
strategies for
current users to
avoid threats
8. Mobility: Identify the
system’s capabilities for
mobile use.
Weight: 10%
Failed to identify
your system’s
capabilities for
mobile use,
incomplete
Identified your
system’s
capabilities for
mobile use, but not
comprehensive
Identified your
system’s
capabilities for
mobile use

35. Proposed situations
in which mobile use
would happen and
situations where its
limitations
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 4 of 4
(20 points)
9. Speaker / Audio
Notes: Include speaker
notes or audio narration
that explains each slide
more fully.
Weight: 10%

36. (20 points)
Inadequate speaker
notes or audio
narration, too much
or too little
information on each
slide provided
Somewhat detailed
speaker notes or
audio narration
explaining each
slide more fully
Included speaker
notes or audio
narration explaining
each slide more
fully
Speaker notes or
audio narration
succinct and direct,
persuasive
presentation
Discussed cost
considerations, and
risk identification &
mitigation

37. 10. Clarity, persuasion,
proper communication,
writing mechanics, and
formatting requirements.
Weight: 10%
(20 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,

38. references business
needs, connects to
technical specs,
persuasive
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 4
Week 8 Status Report
Due Week 8 and worth 50 points
In Week 10, you will provide a detailed project presentation for
your new information system project.
Because of its importance to the organization, your presentation
must be thoughtful and visually
appealing.

39. To help you stay on track for this three-week effort, the
executives have assigned you a project manager.
For each week leading up to the presentation, you are expected
to turn in a short (less than one page)
status report. It must address just 4 things:
1. What did you expect to accomplish on the project this week?
2. What did you actually accomplish on the project this week?
3. What issues have arisen, and what help do you need?
4. What do you expect to accomplish on the project next week?
Please write up your responses as a series of bullet points in
memo form. There is no need for a cover
page.
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 4
Week 9 Status Report

40. 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.
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

41. disclosed in whole or in part, without the expressed written
permission of
Strayer University.
CIS 500 Page 3 of 4
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)

42. 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

43. 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

44. 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)

45. Inadequate
description of
issues that arose
during week
Did not describe or
identify issues to be
resolved
Described issues
that arose during
the week
Somewhat
described help
needed to resolve
outstanding issues
Described issues
that arose during
the week
Determined what
kind of help is
needed to resolve
outstanding issues
Described issues
that arose,
demonstrated how
they were resolved.

46. Presented issues in
order of priority,
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

47. 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

48. 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 4 of 4
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,

49. 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