Cmgt 555 academic adviser ....tutorialrank.com

CMGT 555 Entire Course (June 2020)
For more course tutorials visit
www.tutorialrank.com
CMGT 555 Week 1 Individual SDLC Comparison
CMGT 555 Week 1 DQ 1
CMGT 555 Week 2 Individual Project Plans

CMGT 555 Week 3 Individual System Requirements
CMGT 555 Week 4 Individual CRM Design Proposal
CMGT 555 Week 5 Individual Change Management Plan

CMGT 555 Week 6 Individual Customer Success Story
.....................................................................................................................
.........................................
Projects are unique by nature, and organizations each have their own
specific needs when it comes to managing systems projects. In addition,
there is never a superior SDLC methodology, but rather SDLCs that will
fit certain projects better than others.

Compare and contrast Agile and waterfall SDLCs. Based on your
personal and work experiences, why might an organization opt to choose
one SDLC over another? Can an organization make use of both types of
SDLCs, and why? Reference a project you have personally worked on
(at home or at work) and integrate that experience into your response.
.....................................................................................................................
.........................................
Projects that adhere to an Agile SDLC allow for iterative development,
leading to quicker results for customers. However, many times the
requirements you have at the start of an Agile sprint differ from the
results you see at the end of the sprint.
How can stakeholders be flexible in terms of scope and requirements
when running an Agile project? What type of expectations would you set

with your customer (internal or external) when running a project based
on the Agile SDLC, and why?
.....................................................................................................................
.........................................
CMGT 555 Week 1 Individual SDLC Comparison
You’ve been hired to implement the CRM system for WeLoveVideo,
Inc. Part of your job is to propose and recommend a project approach
based on several models. A meeting is scheduled for next week with the
WeLoveVideo, Inc. CIO to discuss your recommendations on the project
approach.
Prepare for this meeting by developing a 6- to 8–slide multimedia-rich
presentation that explains the waterfall and Agile SDLCs, and how your
team will guide WeLoveVideo, Inc. Include the following in your
presentation:

An explanation of waterfall and Agile SDLCs, including:
The typical phases that comprise an entire systems project
The differences in documentation produced, with an explanation as to
why it would or would not be used
An explanation of stakeholder expectations that should be set based on
the chosen SDLC
The pros and cons associated with each waterfall and Agile SDLC
A graphic summary or chart comparing waterfall and Agile for the
WeLoveVideo, Inc. CRM project, including features, team, delivery,
and feedback
Attributes within WeLoveVideo, Inc. that would dictate your
recommendation on the type of SDLC you would lean toward
Two references formatted in APA style
Write an executive summary to accompany your presentation that
includes your SDLC recommendation and references to support your
recommendation. This summary for the executive team is typically 1- to
2-pages in length.
Submit your assignment.

.............................................................................................
.................................................................
Well-defined business requirements are essential building blocks to any
system project. If requirements are not written well, the input to design
and development phases will be poor. However, well-written
requirements will lead to a much better project outcome in relation to
stronger designs and system solutions.
What are 2 key attributes to well-written requirements? How do these
attributes impact the quality of requirements? How might you assess
system requirements based off these attributes?
.....................................................................................................................
.........................................

Agile systems development provides organizations with an iterative
model, allowing for quicker, more incremental results. However, an
Agile SDLC is also more flexible in terms of the comprehensive project
results, meaning stakeholders may have a set of requirements going in
that are reshaped throughout the life of the project.
When might an organization opt for an Agile SDLC, and why? How
would you describe the flexible nature of an Agile SDLC, to set
stakeholders expectations upfront?
.....................................................................................................................
.........................................
CMGT 555 Week 2 Individual Project Plans
After consideration of your proposal from Week 1, the WeLoveVideo,
Inc. CIO is having a hard time envisioning how the project would be
executed based on your recommendations. She has asked your company
to develop a project plan in both waterfall and Agile so she can better
understand the implications to her team.

Using Microsoft® Excel®, Project, or another project management tool
of your choice―and approved by your instructor, develop two
milestone-level project plans: one using the waterfall and one using
Agile SDLC. The milestones should demonstrate a clear understanding
of the inputs and outputs for each phase of a project, based upon the
SDLC applied. At minimum, there should be a clear milestone at the end
of each project phase, and potentially milestones within phases where
applicable. Ensure that each project plan incorporates comprehensive
SDLC phases based on each SDLC type.
.....................................................................................................................
.........................................
When developing system requirements, it is very important that they be
written in a way that will allow for specific design and development

steps. Poorly written requirements may lead to ambiguity, resulting in
missing a stakeholder’s expectations.
Develop one complete system requirement for one of the following
activities:
Option A: Making a withdrawal at an ATM.
Option B: Using your charge card for a meal at a restaurant.
Option C: Buying a stock using an online brokerage account.
Option D: Searching for books (on a specific topic) using an online
bookstore.
In your response, consider attributes that comprise a solid system
requirement, as well as the result of requirements that do not meet
quality attributes.

.............................................................................................
.................................................................
Depending on the type of project and the SDLC applied, system
requirements may be developed differently. For example, many current
projects use the Agile SDLC, and build requirements based on user-story
format. A user story is essentially a use case that describes how a
specific user would interact with a system. An example of a user story
tied to a customer using an ATM might be, “As a customer of the bank, I
need to be able to access my account from an ATM to understand
balances across all of my accounts.”
What are the attributes that comprise a quality user story, and why are
these attributes necessary? Consider the result of poorly written user
stories. Provide an example of what you would consider to be a quality
user story. This example can be from experience, from a company you
know of, or one that you create.

Post your answers to the discussion forum.
.....................................................................................................................
.........................................
CMGT 555 Week 3 Individual System Requirements
As you learned in Week 2, requirements are a fundamental component
to any project. Depending on the SDLC applied, requirements can be
written in different forms. For example, some requirements will be very
technically focused (technical requirements) and are written in a manner
that dictates what a stakeholder expects the system to accomplish.
Another approach taken, often with Agile-run projects, is to create a user
story. A user story focuses on different types of system users and
outlines more of a workflow that organizations expect.
Review the Wk 2 Discussion 1 about what makes well-written
requirements.

The WeLoveVideo, Inc. project team met with the business owners last
week in a structured requirements-gathering meeting. In this meeting,
they discussed that the requirements should focus on certain users, such
as customer support representatives and inside-sales representatives, as
well as be geared towards the system supporting the job function.
Create 15 to 20 system requirements based on the scope of the project
discussed in the requirements meeting. Ensure the requirements meet
quality standards and are outlined in priority order. Provide a
justification behind the prioritization within the document. You may use
any Microsoft® program, such as Excel® or Word, to create the list of
requirements.
.....................................................................................................................
.........................................

Implementing a new system, or modifying an existing one, can create
organizational change. This change can impact how employees work,
how information technology teams support the business, and even how
customers interact with the organization.
Ensuring users adopt new systems or changes to existing systems is
critical, as implementing a system no one will use becomes a wasted
investment. User adoption should be considered by the business
stakeholders no later than during the design phase. Identify 2 to 4 steps
or activities a project team can take that will influence user adoption.
Explain how these steps or activities will influence user adoption.
.....................................................................................................................
.........................................

Resource: Pluralsight: UX-based Software Design in the Week 4 -
Required Learning Activities folder
Waterfall projects may dictate a different approach and rigor
surrounding design when compared to Agile.
Consider the phases associated with both waterfall and Agile. How you
would approach design for a new project, based off each of these SDLC
approaches? Consider User Experience Design and Bottom Up Design
approaches. Provide an example of a project (either from your
experience or one you read about) and explain what documents you
would produce, why, and how that would affect future phases of the
project.
.....................................................................................................................
.........................................
CMGT 555 Week 4 Individual CRM Design Proposal

The stakeholders at WeLoveVideo, Inc. are interested in understanding
what the CRM will look like prior to development. There are a variety of
ways the project team can approach design, some being more effective
in terms of giving the stakeholders a view into what the final product
will look like. Some of the approaches include a storyboard and
presentation. The storyboard provides a visual display, while the
presentation provides the necessary information.
Develop a proposal presentation of how you will approach the design for
the WeLoveVideo, Inc. CRM project.
Create an 8- to 10-slide multimedia-rich presentation and include the
following:
Identify the recommended design approach (User Experience Design,
Bottom Up Design, or one of your choosing).

Explain why this approach was chosen over others.
Highlight the steps and processes that will be adhered to, along with the
output expected from the approach.
Include a storyboard that represents general screen layout and user flow
within the system.
Highlight the pros and cons of the chosen approach against other
options.
Appropriate charts, images, graphics, video, or audio where appropriate.
Cite at least 2 references using APA format.
.....................................................................................................................
.........................................
Something that is easy to overlook, but critical to the success of a
systems project, is the quality of the development work. Testing needs to
occur and is generally based on the approved requirements and design.

How would you best ensure quality when developing a new system?
Explain the inputs and outputs to testing. Use any relevant examples you
have from your experiences within your own organizations, or
organizations that you are familiar with.
.....................................................................................................................
.........................................
When developing new systems, teams tend to focus on understanding
the requirements of the system at the start of the project. Until
requirements are known, it’s hard to understand design and development
components. Beyond this, testing is an essential part of any systems
project, no matter what SDLC is applied.
When do you think a project team should plan for testing? Provide a
justification behind your position. Who do you think is the best
resource(s) to conduct testing activities, and why?

.....................................................................................................................
.........................................
CMGT 555 Week 5 Individual 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 change management plan for WeLoveVideo, Inc. Within the
change management plan, incorporate the following:
Ways in which the system was designed to support a positive user
experience

How the system changes will be communicated to the users
Ways in which you will shape the communications to ensure a positive
outlook
Collateral (Ex. FAQs and user guides) that will be developed in support
of the new system
Explain what type of support will be available to the users after
implementations.
Refer to Ch. 13 of Modern Systems Analysis and Design in the Week 5 -
Required Learning Materials folder for information on creating change
management plans.
.....................................................................................................................
.........................................

Technology advances rapidly in the current market and can become
dated and obsolete quickly. Organizations must keep pace with the
evolution of technology to compete and sustain a market advantage.
What are some emerging technology trends that have influenced your
personal choice of an SDLC, either in your experience or in something
you’ve read? Explain the trend and the influence and effect it had on
you. Were there any issues? Would you recommend the same SDLC if
you had to do it again?
.....................................................................................................................
.........................................
Throughout this course, you have evaluated two core SDLCs that are
most commonly applied within current organizations to manage systems
development projects. Consider the past 6 weeks, and list your
predictions on how current trends will influence software development
in the next 10 years. Cite readings, videos, or assignments from the past
6 weeks that support your prediction.

Post your answers to the discussion forum.
.....................................................................................................................
.........................................
CMGT 555 Week 6 Individual Customer Success Story
Your implementation was successful, and it’s time to plan ahead for
future projects. One important piece of project reflection and creating
future proposals is to use 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.

Develop a 12- to 14-slide, multimedia-rich presentation featuring your
work with WeLoveVideo, Inc. You will use this presentation in your
next client meeting.
Include the following:
A description of the systems project
Justification behind the SDLC recommended(waterfall or Agile)
Intended business goals of the systems project
Results of the project, to include scope,schedule, budget and user
adoption
Storyboard example
Impact the systems project had on theorganization
How the decisions made in this project willaffect the business in the next
10 years
Detailed speaker notes
Appropriate charts, images, graphics, video, or audio where appropriate
At least 2 references cited in APA format

In addition, write a brief, 1-page summary of the presentation to be
published on the company website for potential clients to review.

Cmgt 555 academic adviser ....tutorialrank.com

Recommended

Recommended

More Related Content

Similar to Cmgt 555 academic adviser ....tutorialrank.com

Similar to Cmgt 555 academic adviser ....tutorialrank.com (20)

More from ladworkspaces

More from ladworkspaces (20)

Recently uploaded

Recently uploaded (20)

Cmgt 555 academic adviser ....tutorialrank.com