CMGTCB/555 Competency 3 Assessment and RubricCourse Title: Systems Analysis and Development
Competency Assessment Title: Change Management Plan & Customer Success Story
Assignment Directions
Part 1 Change Management Plan
Building a new software application is just the start, as organizations invest in software to help solve business problems. For systems to be
effective and have a positive influence on organizational goals, they need to address user experience and focus on how best to gain new system
adoption. The ideas for a new strategy are compiled in a document titled a “change management plan.” This plan contains information about the
new user experience, how the new system will be supported, and the communication plans to inform the system users, which includes FAQs and
instructions on how to use the system.
Develop a 2- to 3-page change management plan for WeLoveVideo. Within the change management plan, incorporate the following:
• Justify ways in which the system was designed to support a positive user experience
• Determine how the system changes will be communicated to the users
• Propose ways in which you will shape the communications to ensure a positive outlook
• Propose collateral (e.g., FAQs and user guides) that will be developed in support of the new system
• Recommend what type of support will be available to the users after implementations
Note: Refer to Chapter 13 of Modern Systems Analysis and Design for information on creating change management plans.
Part 2 Customer Success Story
Your implementation was successful, and it is time to plan for future projects. As the project comes to a conclusion, it is important to reflect on
the project. One way to do this is to create customer success stories. These stories read as case studies and provide internal and external
personnel a glimpse into the decisions made throughout the project. It provides the opportunity to highlight the goals, results, and impacts of the
project. Customer success stories are also used to predict trends in future projects.
Copyright 2021 by University of Phoenix. All rights reserved.
CMGTCB/555 Competency 3 Rubric
Page 2 of 4
Develop a 12- to 14-slide, multimedia-rich presentation (appropriate charts, images, graphics, video, or audio where appropriate) featuring your
work with WeLoveVideo and a 1-page summary of the presentation to be published on the company website for potential clients to review. You
will use this presentation in your next client meeting. Include the following:
•
•
•
•
•
Explain the systems project and the SDLC recommended (Waterfall or Agile) with intended business goals of the systems project
Assess the results of the project, include scope, schedule, budget, and user adoption and the impact the systems project had on the
organization with storyboard example
Compare 2 customer success stories
Predict how the decisions made in this project will affect the business in the next 10 years
Compose detailed presentation speaker notes which include at least 2 references cited in APA format a 1-page summary of the
presentation to be published on the company website for potential clients to review
Note: Slides in a multimedia-rich presentation should only contain essential information. Do not design a slide presentation made up of long bullet
points. Speaker notes should convey the details you would give if you were presenting. Review the Create Speaker Notes video for more help.
Copyright 2021 by University of Phoenix. All rights reserved.
CMGTCB/555 Competency 3 Rubric
Page 3 of 4
Competency Assessment Rubric
Assignment/Performance
Criteria
Mastery
100%
Thoroughly justified ways in which
the system was designed to support
a positive user experience
Meets Expectations
85%
Not Met
0%
Adequately justified ways in which
the system was designed to
support a positive user experience
Vaguely justified ways in which the
system was designed to support a
positive user experience
2. Part 1 Change
Management Plan: System
Changes Communication
(weight 10%)
Clearly determined how the
system changes will be
communicated to the users
Somewhat determined how the
system changes will be
communicated to the users
Barely determined how the system
changes will be communicated to
the users or did not attempt to
determine how system
changes will be communicated
3. Part 1 Change
Management Plan: Positive
Communication
(weight 10%)
Thoroughly proposed ways to shape
the communications to ensure a
positive outlook
Adequately proposed ways to
shape the communications to
ensure a positive outlook
Vaguely proposed ways to shape
the communications to ensure a
positive outlook or did not attempt
to propose communication
4. Part 1 Change
Management Plan:
Collateral
(weight 10%)
Thoroughly proposed collateral
(e.g., FAQs and user guides) that
will be developed in support of the
new system
Adequately proposed collateral
(e.g., FAQs and user guides) that
will be developed in support of the
new system
Vaguely proposed collateral (e.g.,
FAQs and user guides) that will be
developed in support of the new
system
5. Part 1 Change
Management Plan: Support
(weight 10%)
Clearly recommended what type of
support will be available to the
users after implementations
Adequately recommended what
type of support will be available to
the users after implementations
Vaguely recommended what type of
support will be available to the
users after implementations
6. Part 2 Presentation:
Explanation
(weight 10%)
Thoroughly explained the systems
project and the SDLC
recommended (Waterfall or Agile)
with intended business goals of the
systems project
Adequately explained the systems
project and the SDLC
recommended (Waterfall or Agile)
with intended business goals of the
systems project
Vaguely explained the systems
project and the SDLC
recommended (Waterfall or Agile)
with intended business goals of the
systems project
7. Part 2 Presentation:
Results
(weight 10%)
Clearly assessed the results of the
project, scope, schedule, budget,
user adoption and the impact the
systems project had on the
Adequately assessed the results of
the project, scope, schedule,
budget, user adoption and the
impact the systems project had on
Vaguely assessed the results of the
project, scope, schedule, budget,
user adoption and the impact the
systems project had on the
1. Part 1 Change
Management Plan: User
Experience
(weight 10%)
Copyright 2021 by University of Phoenix. All rights reserved.
CMGTCB/555 Competency 3 Rubric
Page 4 of 4
Assignment/Performance
Criteria
Mastery
100%
organization with storyboard
example
Meets Expectations
85%
the organization with storyboard
example
Not Met
0%
organization with storyboard
example
8. Part 2 Presentation:
Customer Success Stories
(weight 10%)
Thoroughly compared 2 customer
success stories
Adequately compared 2 customer
success stories
Vaguely compared 2 customer
success stories
9.Part 2 Presentation:
Future of Business
(weight 10%)
Clearly predicted how the decisions
made in this project will affect the
business in the next 10 years
Adequately predicted how the
decisions made in this project will
affect the business in the next 10
years
Vaguely predicted how the
decisions made in this project will
affect the business in the next 10
years
10. Part 2 Presentation:
Speaker Notes & Summary
(weight 10%)
Thoroughly composed detailed
presentation speaker notes and a 1page summary of the presentation
to be published on the company
website
Partially composed detailed
presentation speaker notes and a
1-page summary of the
presentation to be published on the
company website
Vaguely composed detailed
presentation speaker notes and a 1page summary of the presentation
to be published on the company
website
Copyright 2021 by University of Phoenix. All rights reserved.