Project Plans
After considering your previously completed proposal, 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 that is approved by your instructor, develop one milestone-level project plan using the waterfall SDLC and a second milestone-level project plan using Agile SDLC that does the following:
- Describes the inputs and outputs for each phase of a project within each milestone based upon the SDLC applied.
- Contains at least one clear milestone at the end of each project phase and milestones within phases where applicable.
- Incorporates comprehensive SDLC phases based on each SDLC type.
- The following scenario will be used for all assessments in this course:
- WeLoveVideo is a mid-sized entertainment corporation providing streaming video services to its customers globally. The company has become very successful, growing from 10 to 200 employees in the past 5 years and gaining significant traction in the market. In addition, their sales have grown from $100,000 to $40,000,000.The primary services provided are streaming videos, primarily focusing on major network shows along with current and past movie releases. They are seen as an alternative service provider to local cable and satellite TV.As the company has grown in size and revenue, they have found that the database they use to track customer data has become obsolete. The sales team has a hard time determining both its prospective customer demographics and its current customer preferences. Sales is in desperate need of a customer relationship management (CRM) system, but is currently well positioned to invest in improving the internal systems.The company has a functional organizational structure. The departments include Sales, Human Resources, Finance, Operations, and Product Development. Each of these departments is influenced by customer data and will be potential users of the new CRM. In addition to its internal users, it has partnered with all the major networks to license and make its shows available to customers.A CRM system will be no small undertaking. Currently, customer data is being managed through multiple spreadsheets that will need to be migrated. In addition, Finance uses a system called “Adaptive Insights for Finance,” which will need to interface with the CRM to ensure the integration of financial data.Beyond this, WeLoveVideo has focused on improving its employees’ overall worker experience in terms of applications, workflow, and user interface. This new CRM will need to account for this, ensuring that the user interface and design lead to strong adoption across its users.Speed of implementation will be critical, as the company senses it is losing money daily due to the lack of centralized customer information. WeLoveVideo is hoping that this CRM implementation will not only streamline Sales and Support, but will also provide valuable insights about its customers’ viewing and buying behaviors that will lead to increased market share.
CMGTCB/555 Competency 2 Assessment and Rubric
Course Title: Systems Analysis and Development
Competency Assessment Title: Project Plans
Assignment Directions
After considering your previously completed proposal, 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 that is approved by your instructor, develop one milestonelevel project plan using the waterfall SDLC and a second milestone-level project plan using Agile SDLC that does the following:
•
•
•
Describes the inputs and outputs for each phase of a project within each milestone based upon the SDLC applied.
Contains at least one clear milestone at the end of each project phase and milestones within phases where applicable.
Incorporates comprehensive SDLC phases based on each SDLC type.
Copyright 2021 by University of Phoenix. All rights reserved.
CMGTCB/555 Competency 2 Rubric
Page 2 of 2
Competency Assessment Rubric
Assignment/Performance
Criteria
Mastery
100%
The plans comprehensively
described the inputs and outputs
for each phase of a project within
each milestone based upon the
SDLC applied.
Meets Expectations
85%
The plans partially described the
inputs and outputs for each phase of
a project within each milestone
based upon the SDLC applied.
Not Met
0%
The plans narrowly described the
inputs and outputs for each phase of
a project within each milestone
based upon the SDLC applied.
2. Project Plans: Milestones
(weight 30%)
The project plans fully defined at
least one clear milestone at the
end of each project phase and
milestones within phases where
applicable.
The project plans adequately
defined at least one clear milestone
at the end of each project phase and
milestones within phases where
applicable.
The project plans inadequately
defined at least one clear milestone
at the end of each project phase and
milestones within phases where
applicable.
3. Project Plans: Phases
(weight 35%)
The project plans clearly related
comprehensive SDLC phases
based on each SDLC type.
The project plans sufficiently related
comprehensive SDLC phases based
on each SDLC type.
The project plans vaguely related
comprehensive SDLC phases based
on each SDLC type.
1. Project Plans: Inputs and
Outputs
(weight 35%)
Copyright 2021 by University of Phoenix. All rights reserved.
Executive Summary
Elizabeth Chase
University of Phoenix
08/05/2022
Executive Summary
Introduction
System Development Life Cycle entails software development lifeblood, including its
implementation process (Saleh, 2009). In most cases, it follows several phases based on
maintenance specifications. Due to this factor, most companies prefer working with the approach
because it effectively serves or addresses their issues with the available resources. This
presentation highlights the Agile and Waterfall SLDC models based on this concept. The
presentation will also recommend the type of approach that will be ideal for CRM system
implementation at WeLoveVideo, Inc.
Waterfall and Agile SDLCs
In this context, the Waterfall model could be classified as akin to a sequence based on different
phases, interconnected through activities and downstream like a waterfall. The difference is that
while documentation might be needed in the various steps as part of the waterfall model, it is
pretty different in agile methodology. The different product works in this approach tend to be
exhausted before the incorporation of the next phase (Saleh, 2009). Agile reflects on swift or
quick development, including the changing user requirement as part of the developmental
process (Nelson, Nelson, & Wierwille, 2012). Developers usually have their chance to progress
or cycle back once the process is initiated. In this case, documentation remains secondary to
code.
Stakeholder expectations
Examples of stakeholders in this context include the employees, the development team, which is
supposed to develop the system and the system sponsors. This means that each team has some
expectations regarding the system processes (Nelson, Nelson, & Wierwille, 2012). The
management expects to have an SDLC approach, which addresses the organisation’s demands
and needs but at a low cost. On the other hand, the employees expect to be part of the process
since they know the system processes (Saleh, 2009). The development team expects to have an
efficient model which can meet the customer needs and demands.
Pros and cons linked to Waterfall SDLC
Some of the pros linked to each waterfall/agile SDLC include ensuring that the requirements
tend to be understood and outlined before the commencement of system development processes.
Each step is usually exploited before shifting to a different step. This is critical in ensuring that
customer requirements tend to be considered (Saleh, 2009). The phases are less challenging,
especially during the implementation process. As part of the cons, it is justifiable to state that the
changes remain challenging to implement, especially during the later phases. The other limitation
is that it usually results in a poorly structured system (Saleh, 2009).
Agile Model
The two main advantages of this model are that the system tends to respond positively, especially
to some of the changes based on the system requirements. It is also justifiable to state that the
development team is always in a position to understand the client’s desires since the model
enhances face-to-face communication (Nelson, Nelson, & Wierwille, 2012). On the other hand,
two significant cons lined to this model are that the system is limited to senior programmers and
that as much as it is profitable for small projects, it is usually challenging to establish aspects
such as resources and efforts incorporated. ‘
Graphic summary
During the implementation of the project at WeLoveVideo, Inc, based on the waterfall
technology, it remains evident that the team starts by following an existing system. In most
cases, this calls for an extensive documentation process, especially where each phase ends. As
part of the process, meetings are necessary to ensure that the consumer’s different requirements
are met (Saleh, 2009). Agile, on the other hand, tend to use a continuous communication process
with the consumers. This is because the CRM project tends to be incorporated cumulatively.
Attributes
There are at least five attributes within WeLoveVideo, Inc., which would be critical in dictating
the recommendation based on the SDLC types. They include risk tolerance, stakeholder demands
and needs, and culture of software implementation (Nelson, Nelson, & Wierwille, 2012). The
other attributes include technology infrastructure and availability of resources that would assist
in completing the process. While incorporating these attributes, it is essential to note that the idea
behind the entire process is to operate or function within the projected boundaries.
References
Nelson, K. M., Nelson, H. J., & Wierwille, B. J. (2012). Agile Software Development
Documentation and Maintainability. MWAIS 2012 Proceedings. Retrieved from
htp://aisel.aisnet.org/mwais2012/24
Saleh, K. (2009). Software engineering. Ft. Lauderdale, FL: J. Ross Pub.